Skip to content

Update the examples' tooling (abaplint 2.120.73, Playwright 1.64.0, UI5 CLI 4.0.71) - #12

Merged
oblomov-dev merged 3 commits into
mainfrom
claude/beautiful-turing-wxr303
Oct 11, 2026
Merged

oblomov-dev merged 3 commits into
mainfrom
claude/beautiful-turing-wxr303

Conversation

@oblomov-dev

@oblomov-dev oblomov-dev commented Oct 10, 2026 •

Copy link
Copy Markdown
Member

What changes

Every npm dependency of the workspace and its four examples on its latest version; the lockfile is regenerated by npm install.

Package Old New Where
@abaplint/cli ^2.120.68 ^2.120.73 root
@playwright/test ^1.63.0 ^1.64.0 root
@ui5/cli ^4.0.70 ^4.0.71 root, all four examples
prettier ^3.9.9 ^3.9.10 root
@sap-ux/ui5-middleware-fe-mockserver ^2.4.17 ^2.4.18 fiori-elements, fiori-elements-v2
@abap2ui5/embed-control ^0.1.0 ^0.1.1 all four examples (the same range everywhere)

@abap2ui5/embed-control 0.1.1 is the newest published version (npm view @abap2ui5/embed-control versions: 0.1.0, 0.1.1) and already the one the lockfile installed; only the ranges follow it.

Further commit:

  • card/webapp/Component.js: a destination the host resolves to no URL threw inside the promise callback (new URL( )) - an unhandled rejection and an empty card without a word. The card now says "The destination resolves to no URL", like it names one on another origin. New e2e test in test/e2e/card.spec.mjs.

Why

Keep the tooling current ahead of the release.

npm audit still reports advisories in transitive dependencies of the UI5 CLI / fe-mockserver tree that npm audit fix cannot resolve without --force (breaking); left as they are.

Checked

npm run lint, npm run format:check, npm run abaplint (0 issues), npm run build (the control in every dist/thirdparty/), npm run bsp against abap2UI5 main's tools. The e2e tests run in CI - red as on main until the control is released after 0.1.1 (see the comment below).

🤖 Generated with Claude Code

https://claude.ai/code/session_01Te3BRpRpxNhZAYnrQL6Gdt

…I5 CLI 4.0.71)

Also prettier 3.9.10 and @sap-ux/ui5-middleware-fe-mockserver 2.4.18, and
the examples' range of @abap2ui5/embed-control to ^0.1.1, the version the
lockfile already installs - the same range in every example, so the
workspace keeps its one copy at the root.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Te3BRpRpxNhZAYnrQL6Gdt

Copy link
Copy Markdown
Member Author

Both e2e jobs fail here exactly as on main (scheduled ci runs since 2026-10-07, deliver run 38070505511): the freestyle tests for restart(), the invisible control, endpoint spellings, a query/fragment on the endpoint, the failed-load fallback and the params handover need the unreleased control (embed-control's "Unreleased" section) and fail with the published @abap2ui5/embed-control 0.1.1 (control.restart is not a function, ...). Not caused by this update; check and bsp are green. They turn green once the control is released and the lockfile here takes the new version (npm install @abap2ui5/embed-control@<version> --workspaces).


Generated by Claude Code

The card parsed what the host resolved its destination to with new URL( )
inside the promise callback. A value that is no URL threw there - an
unhandled rejection, and a card without app and without a word. It says
now that the destination resolves to no URL, the way it names one on
another origin. New e2e test in card.spec.mjs.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Te3BRpRpxNhZAYnrQL6Gdt
The two READMEs linked abap2UI5-addons/fiori-elements-integration, which
answers 404. The name stays as the predecessor, marked as no longer
published, as abap2UI5/docs does on its Fiori elements page.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Te3BRpRpxNhZAYnrQL6Gdt
@oblomov-dev
oblomov-dev merged commit 2483c3c into main Oct 11, 2026
2 of 4 checks passed
@oblomov-dev
oblomov-dev deleted the claude/beautiful-turing-wxr303 branch October 11, 2026 09:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants