Skip to content

Update @abaplint/cli to 2.120.73 and playwright to 1.64.0 - #877

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

oblomov-dev merged 1 commit into
mainfrom
claude/beautiful-turing-wxr303

Conversation

@oblomov-dev

Copy link
Copy Markdown
Member
  • @abaplint/cli ^2.120.60 -> ^2.120.73 (the organisation-wide version, CONVENTIONS §4)
  • playwright ^1.63.0 -> ^1.64.0 (the e2e smoke's browser driver)
  • package-lock.json regenerated by npm install

Kept on purpose: the eight @openui5/* packages stay at exactly 1.152.0. They are the UI5 the e2e harness serves, and @abap2ui5/linter-render 0.8.5 (the render gate) ships and judges against 1.152.0 too; samples-controls' check_pins gate holds its runtime to "pinned exactly and to the version @abap2ui5/linter judges against". Moving them to 1.153.0 should wait for a linter release built on 1.153.0. @abap2ui5/linter / linter-render are already on the latest release (0.8.5).

No new abaplint findings. npm run check passes locally in full (pin, abaplint, cloud, abap2UI5 linter with the render gate, agents, orphans, keywords, markers, titles, launchpad, catalogue, derived, prose, docs links, app rules, ATC, patterns, selftest, rename). The e2e smoke runs in CI (it triggers on package.json).

🤖 Generated with Claude Code

https://claude.ai/code/session_01Te3BRpRpxNhZAYnrQL6Gdt


Generated by Claude Code

@oblomov-dev
oblomov-dev merged commit cf78961 into main Oct 11, 2026
22 checks passed
@oblomov-dev
oblomov-dev deleted the claude/beautiful-turing-wxr303 branch October 11, 2026 09:41
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