Skip to content

Bump the toolchain group with 6 updates - #6

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/toolchain-f9c24f63a2
Open

Bump the toolchain group with 6 updates#6
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/toolchain-f9c24f63a2

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 20, 2026 •
edited
Loading

Copy link
Copy Markdown

Bumps the toolchain group with 6 updates:

Package From To
@abaplint/database-sqlite 2.11.78 2.13.40
@abaplint/runtime 2.13.22 2.13.59
@abaplint/transpiler-cli 2.13.22 2.13.59
@types/node 22.19.18 26.2.0
npm-check-updates 17.1.18 23.0.2
@abap2ui5/render-runtime 0.1.1 0.2.1

Updates @abaplint/database-sqlite from 2.11.78 to 2.13.40

Commits

Updates @abaplint/runtime from 2.13.22 to 2.13.59

Commits

Updates @abaplint/transpiler-cli from 2.13.22 to 2.13.59

Commits

Updates @types/node from 22.19.18 to 26.2.0

Commits

Updates npm-check-updates from 17.1.18 to 23.0.2

Release notes

Sourced from npm-check-updates's releases.

v23.0.2

What's Changed

Full Changelog: raineorshine/npm-check-updates@v23.0.1...v23.0.2

v23.0.1

What's Changed

Full Changelog: raineorshine/npm-check-updates@v23.0.0...v23.0.1

v23.0.0

⚠️ Breaking changes & migration

1. Node.js 22+ required (#1844) The minimum supported Node.js is now 22. Supported versions: ^22.22.2 || ^24.15.0 || >=26.0.0 (and npm >=10).

  • Migration: Upgrade Node before installing. On older Node, stay on v22.x.

... (truncated)

Changelog

Sourced from npm-check-updates's changelog.

[23.0.2] - 2026-08-07

What's Changed

Full Changelog: raineorshine/npm-check-updates@v23.0.1...v23.0.2

[23.0.1] - 2026-08-02

What's Changed

Full Changelog: raineorshine/npm-check-updates@v23.0.0...v23.0.1

[23.0.0] - 2026-07-26

⚠️ Breaking changes & migration

1. Node.js 22+ required (#1844)

... (truncated)

Commits
Install script changes

This version modifies prepare script that runs during installation. Review the package contents before updating.


Updates @abap2ui5/render-runtime from 0.1.1 to 0.2.1

Release notes

Sourced from @​abap2ui5/render-runtime's releases.

v0.2.1

The theme of this release is the lifecycle rules seeing the code that is there. 0.2.0 was about findings that were not true; these three are about code the rules could not read at all — a handle with another name, a branch that does not exist, and an expression mistaken for a statement.

  • COND's ELSE is not the IF's ELSE. ifBranchEnd scanned for the WORD ELSE to find where a lifecycle branch stops, and

    status = COND #( WHEN i MOD 2 = 0 THEN `open` ELSE `closed` ).

    puts one at IF-depth 0, so the branch ended there — four statements before the view_display( ) it actually contains, which was then reported as a branch that never re-displays. Found on a real documentation page, not by reading. A false positive on idiomatic modern ABAP is the worst kind: it costs more than a suppression, it pushes people away from COND to satisfy a rule about something else. The scanner tracks parenthesis depth now, so inside an unclosed ( nothing is a statement keyword. Two tests, both directions — the second (a COND must not HIDE a branch that genuinely never displays) is the one that matters, because a fix that blinds the scanner passes the first alone.

  • The lifecycle rules find a client handle that is not called client. missing-on-navigated-branch, missing-view-display-on-navigated and separate-lifecycle-ifs all matched the receiver literally as client->. A class that names the handle differently was not judged leniently, it was invisible: abap2UI5/samples-stack's app 319 calls it m_client, has no check_on_navigated( ) branch, and no rule said a word. mo_client and me->client are in the corpora too. The handle is matched by shape now, and three assertions pin it.

  • New rule missing-on-navigated-branch (warning). The complement of missing-view-display-on-navigated, which has always judged a check_on_navigated( ) branch that never re-displays. The far more common shape in the wild has no branch at all, and nothing could see it.

    check_on_init( ) means "this app INSTANCE never ran", not "the app starts" — abap2UI5 flips mv_check_initialized in db_save( ) after the very first roundtrip. It is therefore false on three roundtrips that put the app back on screen: a called app leaving through nav_app_leave( ), one of the built-in z2ui5_cl_pop_* value helps returning (those run over nav_app_call too), and a bookmarked draft being restored. All three raise check_on_navigated( ) alone; with no branch for it main( ) does nothing, the response carries no display, and the model is pushed into a MAIN slot still holding the other app's view. The screen stays wrong with no error anywhere — which is why an app written this way works perfectly until the day something navigates into it, and why the defect is usually reported as "it broke when I put it behind a navigation" long after the app was written.

... (truncated)

Changelog

Sourced from @​abap2ui5/render-runtime's changelog.

0.2.1

The theme of this release is the lifecycle rules seeing the code that is there. 0.2.0 was about findings that were not true; these three are about code the rules could not read at all — a handle with another name, a branch that does not exist, and an expression mistaken for a statement.

  • COND's ELSE is not the IF's ELSE. ifBranchEnd scanned for the WORD ELSE to find where a lifecycle branch stops, and

    status = COND #( WHEN i MOD 2 = 0 THEN `open` ELSE `closed` ).

    puts one at IF-depth 0, so the branch ended there — four statements before the view_display( ) it actually contains, which was then reported as a branch that never re-displays. Found on a real documentation page, not by reading. A false positive on idiomatic modern ABAP is the worst kind: it costs more than a suppression, it pushes people away from COND to satisfy a rule about something else. The scanner tracks parenthesis depth now, so inside an unclosed ( nothing is a statement keyword. Two tests, both directions — the second (a COND must not HIDE a branch that genuinely never displays) is the one that matters, because a fix that blinds the scanner passes the first alone.

  • The lifecycle rules find a client handle that is not called client. missing-on-navigated-branch, missing-view-display-on-navigated and separate-lifecycle-ifs all matched the receiver literally as client->. A class that names the handle differently was not judged leniently, it was invisible: abap2UI5/samples-stack's app 319 calls it m_client, has no check_on_navigated( ) branch, and no rule said a word. mo_client and me->client are in the corpora too. The handle is matched by shape now, and three assertions pin it.

  • New rule missing-on-navigated-branch (warning). The complement of missing-view-display-on-navigated, which has always judged a check_on_navigated( ) branch that never re-displays. The far more common shape in the wild has no branch at all, and nothing could see it.

    check_on_init( ) means "this app INSTANCE never ran", not "the app starts" — abap2UI5 flips mv_check_initialized in db_save( ) after the very first roundtrip. It is therefore false on three roundtrips that put the app back on screen: a called app leaving through nav_app_leave( ), one of the built-in z2ui5_cl_pop_* value helps returning (those run over nav_app_call too), and a bookmarked draft being restored. All three raise check_on_navigated( ) alone; with no branch for it main( ) does nothing, the response carries no display, and the model is pushed into a MAIN slot still holding the other app's view. The screen stays wrong with no error anywhere — which is why an app written this way works perfectly until the day something navigates into it, and why the defect is usually reported as "it broke when I put it behind a navigation" long after the app was written.

... (truncated)

Commits

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

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

@dependabot
Bump the toolchain group with 6 updates
5490a7a 
Bumps the toolchain group with 6 updates:

| Package | From | To |
| --- | --- | --- |
| [@abaplint/database-sqlite](https://github.com/abaplint/transpiler) | `2.11.78` | `2.13.40` |
| [@abaplint/runtime](https://github.com/abaplint/transpiler) | `2.13.22` | `2.13.59` |
| [@abaplint/transpiler-cli](https://github.com/abaplint/transpiler) | `2.13.22` | `2.13.59` |
| [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) | `22.19.18` | `26.2.0` |
| [npm-check-updates](https://github.com/raineorshine/npm-check-updates) | `17.1.18` | `23.0.2` |
| [@abap2ui5/render-runtime](https://github.com/abap2UI5/linter/tree/HEAD/render-runtime) | `0.1.1` | `0.2.1` |


Updates `@abaplint/database-sqlite` from 2.11.78 to 2.13.40
- [Commits](https://github.com/abaplint/transpiler/commits)

Updates `@abaplint/runtime` from 2.13.22 to 2.13.59
- [Commits](https://github.com/abaplint/transpiler/commits)

Updates `@abaplint/transpiler-cli` from 2.13.22 to 2.13.59
- [Commits](https://github.com/abaplint/transpiler/commits)

Updates `@types/node` from 22.19.18 to 26.2.0
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node)

Updates `npm-check-updates` from 17.1.18 to 23.0.2
- [Release notes](https://github.com/raineorshine/npm-check-updates/releases)
- [Changelog](https://github.com/raineorshine/npm-check-updates/blob/main/CHANGELOG.md)
- [Commits](raineorshine/npm-check-updates@v17.1.18...v23.0.2)

Updates `@abap2ui5/render-runtime` from 0.1.1 to 0.2.1
- [Release notes](https://github.com/abap2UI5/linter/releases)
- [Changelog](https://github.com/abap2UI5/linter/blob/main/CHANGELOG.md)
- [Commits](https://github.com/abap2UI5/linter/commits/v0.2.1/render-runtime)

---
updated-dependencies:
- dependency-name: "@abaplint/database-sqlite"
  dependency-version: 2.13.40
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: toolchain
- dependency-name: "@abaplint/runtime"
  dependency-version: 2.13.59
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: toolchain
- dependency-name: "@abaplint/transpiler-cli"
  dependency-version: 2.13.59
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: toolchain
- dependency-name: "@types/node"
  dependency-version: 26.2.0
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: toolchain
- dependency-name: npm-check-updates
  dependency-version: 23.0.2
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: toolchain
- dependency-name: "@abap2ui5/render-runtime"
  dependency-version: 0.2.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: toolchain
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Aug 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants