GeezerVison

Sourced from @​abap2ui5/linter's releases.

v0.9.0

Read before upgrading

• This release is 0.9.0, not 0.8.6. In 0.x the minor is the number that says "a consumer has to act" (npm version minor, RELEASING.md), and several things below need action rather than a lockfile bump: the baseline key format (a baseline written here is misread by 0.8.5 and older), the refused numeric ui5, the baselines a downstream repo has to refresh, the baseline judged on an empty walk and read from its default file, and the refused flag pairs. Nothing removed or renamed an export or a rule id - a renamed id is the one change that would have been a breaking change on its own - and the --json shape only grew. @abap2ui5/linter-render moves to 0.9.0 with it (one tag, both packages) and npm run sync-peer-range writes the peer range; its FLOOR stays 0.8.0, since nothing here needs a newer runtime.

• Refresh every downstream baseline with this release - and move every tool that reads it at the same time. Fixed false positives leave their baseline entries behind, and a stale entry fails a run (exit 1) just as a new finding does. abap2UI5-addons/popups carries one now: src/99/z2ui5_cl_pop_search_help.clas.abap|missing-view-display-on-navigated, the negated guard IF client->check_on_navigated( ) = abap_false. RETURN. that 9c630cc (#134) stopped misreading - measured, popups' configured run exits 1 on that entry alone. abap2ui5lint --update-baseline drops it. The rewritten file uses this release's keys (the baseline-key bullet below), which 0.8.5 and older do not read: bump the Action pin, any npx pin and the VS Code extension's linter pin in the same change.

• abap2UI5/samples needs one waiver. A void helper's parameter now resolves from the call being replayed (Reconstruction), so app 507's three render_list( … items = client->_bind( … ) ) calls reconstruct their items bindings - and omit-initial-drops-false sees the omit_initial = abap_true list whose enabled column the sample drops on purpose ("Archived is enabled now, its abap_false was initial too"). A true positive on a sample that demonstrates the defect: waive it there (" abap2ui5lint-disable-next-line omit-initial-drops-false -- the sample shows exactly this). Nothing else changes on the seven corpora.

• Baseline keys carry no source position any more - and an older linter cannot read the new ones. Ten rules kept two occurrences in one class apart by writing a position into a key field: the source offset into value (default-key-table, abapdoc-html-tag, event-arg-default-index, display-after-nav-app-call, double-display-in-branch, empty-catch-block, boolc-instead-of-xsdbool, delete-index-in-loop) or the line number into member (source-line-too-long, trailing-whitespace). Both fields are part of the baseline key, so a line inserted above a baselined finding made it a stale entry AND a new finding. The position now travels as dedupe, which only the per-class collapse reads and which is dropped

... (truncated)

Sourced from @​abap2ui5/linter's changelog.

0.9.0 - 2026-10-14

Read before upgrading

• This release is 0.9.0, not 0.8.6. In 0.x the minor is the number that says "a consumer has to act" (npm version minor, RELEASING.md), and several things below need action rather than a lockfile bump: the baseline key format (a baseline written here is misread by 0.8.5 and older), the refused numeric ui5, the baselines a downstream repo has to refresh, the baseline judged on an empty walk and read from its default file, and the refused flag pairs. Nothing removed or renamed an export or a rule id - a renamed id is the one change that would have been a breaking change on its own - and the --json shape only grew. @abap2ui5/linter-render moves to 0.9.0 with it (one tag, both packages) and npm run sync-peer-range writes the peer range; its FLOOR stays 0.8.0, since nothing here needs a newer runtime.

• Refresh every downstream baseline with this release - and move every tool that reads it at the same time. Fixed false positives leave their baseline entries behind, and a stale entry fails a run (exit 1) just as a new finding does. abap2UI5-addons/popups carries one now: src/99/z2ui5_cl_pop_search_help.clas.abap|missing-view-display-on-navigated, the negated guard IF client->check_on_navigated( ) = abap_false. RETURN. that 9c630cc (#134) stopped misreading - measured, popups' configured run exits 1 on that entry alone. abap2ui5lint --update-baseline drops it. The rewritten file uses this release's keys (the baseline-key bullet below), which 0.8.5 and older do not read: bump the Action pin, any npx pin and the VS Code extension's linter pin in the same change.

• abap2UI5/samples needs one waiver. A void helper's parameter now resolves from the call being replayed (Reconstruction), so app 507's three render_list( … items = client->_bind( … ) ) calls reconstruct their items bindings - and omit-initial-drops-false sees the omit_initial = abap_true list whose enabled column the sample drops on purpose ("Archived is enabled now, its abap_false was initial too"). A true positive on a sample that demonstrates the defect: waive it there (" abap2ui5lint-disable-next-line omit-initial-drops-false -- the sample shows exactly this). Nothing else changes on the seven corpora.

• Baseline keys carry no source position any more - and an older linter cannot read the new ones. Ten rules kept two occurrences in one class apart by writing a position into a key field: the source offset into value (default-key-table, abapdoc-html-tag, event-arg-default-index, display-after-nav-app-call, double-display-in-branch, empty-catch-block, boolc-instead-of-xsdbool, delete-index-in-loop) or the line number into member (source-line-too-long, trailing-whitespace). Both fields are part of the baseline key, so a line inserted above a baselined finding made it a stale entry AND a new finding. The position now travels as

... (truncated)

• 369f4af Size test: read npm pack --dry-run --json in npm 12's shape as well (#160)
• bc584f5 Release 0.9.0: fold the unreleased rule in and date the section the day it is...
• 9134d30 Add the opt-in rule bound-aggregation-over-size-limit (#158)
• 1e2cb13 Prepare release 0.9.0: fold the Unreleased entries into 0.9.0 (#157)
• 3448bc2 Do not write the default baseline through a link out of its directory (#156)
• a466e0a Review round 2026-10-12: reconstructor, rules, --fix, CLI flags, docs (#155)
• 5660a89 Keep the files a config writes inside its own tree; no cache write through a ...
• 15e4939 release v0.9.0 (#152)
• d782c3c Bump the actions group with 3 updates (#153)
• 3026d80 Move the UI5 snapshot to OpenUI5 1.153.0 and the render runtime to playwright...
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions