ROU-12860: Update Wijmo to 2026v1-Hotfix - Build 5.20261.52

[OS-giulianasilva]

What was happening

The Data Grid was on Wijmo 2026v1 (Build 5.20261.50). ROU-12860 adopts 2026v1-Hotfix (Build 5.20261.52) and asks for a repeatable command so future upgrades stop being hand work.

Two things were quietly wrong before this change:

• package-lock.json is gitignored, so CI resolved dependencies fresh on every install. Under the ^5.20261.50 caret it was already installing .52 against vendored .50 types — the declared dependency and the vendored definitions had drifted apart with nothing to detect it.
• Constants.ts had OSDataGridVersion = '2.23.1' while package.json and gulp/DefaultSpecs.js said 2.24.0. gulp gtaSetVersion builds its search string from DefaultSpecs and calls String.replace with no match assertion.

What was done

Dependency and vendored assets

• package.json pins wijmo at 5.20261.52 exactly. The pin is the fix for the drift above, not a style preference.
• src/@types/wijmo-5.20261.50/ → src/@types/wijmo-5.20261.52/ — 47 root .d.ts + 50 cultures, copied from the distribution archive. Worth knowing for next time: that set comes from three sources, not one — Dist/controls (45), Dist/interop/meta for wijmo.meta.d.ts, and npm for wijmo.interop.grid.d.ts, which the archive ships in no global-flavour copy anywhere.
• styles/wijmo.css refreshed. styles/Grid.css is unchanged.

Source

• Both Constants.ts version strings corrected.
• preventCut: true on the FlexGrid provider config, opting out of the release's new Ctrl+X handling (WJM-37524). The grid has no cut hook, so cut-cleared cells would bypass validation marks, OnCellValueChange and undo/redo. Verified in the browser, since the option bag is untyped at the provider boundary and no build can check it.

Build fix (commit 966b102)

cleanOldFiles in gulpfile.js piped its delete stream without returning it and called cb() immediately. The TypeScript compile that follows is synchronous and blocks the event loop, starving the glob's readdir; when it finally ran it listed dist/ after the compile had written the bundle and deleted exactly those files. npm run build was exiting 0 with an empty dist/. Returning the stream fixes it. This is pre-existing and affects everyone, not just this ticket — it is in scope here only because the upgrade cannot produce GridFramework.js without it.

Not verified: whether CI loses the same race. azure-pipelines.yml publishes dist/GridFramework.js as an artifact, so it may have been publishing an empty directory. Worth opening a past build's artifact.

Upgrade automation

.claude/commands/upgrade-wijmo-version.md plus .claude/skills/upgrade-wijmo-version/ — the phase sequence, the guardrails, and four reference files (module inventory, changeset recipe, workaround inventory, Confluence/Jira targets). The shape is recorded in ADR-0008; the vocabulary in CONTEXT.md.

Documentation

• ADR-0007 — the upgrade decision, the breaking-change assessment, the workaround review and the first run's execution record.
• Confluence: Check the ticket in Jira for the links.

Test Steps

Against OutSystemsDataGridSample_ROU12860, on the module merged onto the protected one and published:

1. In the console, confirm the runtime gate — the second line is the only reliable proof the Wijmo runtime is on the new build rather than just our wrapper:

wijmo.grid.FlexGrid.prototype.hasOwnProperty('preventCut')            // true
OutSystems.GridAPI.GridManager.GetActiveGrid().provider.preventCut    // true  
OSFramework.DataGrid.Constants.WijmoFlexGridVersion                   // '2026v1-Hotfix Wijmo - Build 5.20261.52'  

2. Select several cells, press Ctrl+X — no value clears, no OnCellValueChange fires.
3. Ctrl+C then Ctrl+V into another range — pastes, and still raises validation marks and OnCellValueChange.
4. Export to Excel and open File → Properties — Company is empty where 5.20261.50 wrote GrapeCity, Inc. (WJM-37633). Provable statically too: the .50 wijmo.xlsx carries that fallback once, the .52 zero times.
5. Type 1.2345 and paste 1.2345 into a 2-decimal column — both render 1.23.
6. Regression: render, sort, filter, group, edit; grouped CSV export contains no <b> or </b>; tooltips display.

All of the above passed. The pre-upgrade baseline was the live public sample, which stays on the released build for the length of the upgrade.

Screenshots

N/A — no intended visual change. The filter panel was compared against the public sample and matches.

Checklist

• npm run build passes with no errors or warnings
• Requires changes in OutSystems — the module was refreshed and published for validation; the release publish is a follow-up
• Automated regression suite (outsystems-datagrid-tests) — not run, and its outcome gates taking this PR out of draft
• Release notes draft
• RPM board and the Third-Party Tools registry
• The child page's operator sections: Fixed Issues, New issues found, RPMs, automated-test runs
• The Jira ticket's What I Did block — a comment carries the content; the description template is still to be filled with /enrich-jira-task

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud