Repository navigation
Release 0.3.0: ownsPage, and 1.147.0 is the release that carries it - #31
Merged
Merged
Conversation
abap2UI5 1.147.0 was tagged on 2026-10-14 with ownsPage (#2905), the page left to the host and the sap.m.NavContainer root (#2913) in it, so what 0.2.0's notes, the README, the control's comments and AGENTS.md called "the release after 1.147.0" or "newer than 1.147.0" is 1.147.0. The wording follows; nothing in the control changes. The Unreleased entries move under 0.3.0: ownsPage is a new property, a minor in 0.x. release-check v0.3.0 agrees; lint, format, the 22 tests and pack:check are green. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TrfF51pia7m6tLZQF2G2ua
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The release cut for 0.3.0, per README "Publish": the version in
packages/embed-control/package.jsonmoves to 0.3.0 and theUnreleasedentries (ownsPage, the NavContainer note) move under## 0.3.0.ownsPageis a new property, so a minor in 0.x.One correction travels with it. abap2UI5 1.147.0 was tagged today (2026-10-14) with
ownsPage(abap2UI5/abap2UI5#2905), the page left to the host and thesap.m.NavContainerroot (abap2UI5/abap2UI5#2913) in it - its release commit was written on 10-11 but the tag only went out today, after those merged. So what 0.2.0's notes, the package README, the control's comments and AGENTS.md called "the release after 1.147.0" / "an abap2UI5 newer than 1.147.0" is 1.147.0, and "up to 1.147.0" is up to 1.146.0. The wording follows everywhere it occurs; nothing in the control changes.Checked locally:
node scripts/release-check.mjs v0.3.0(tag, version and changelog agree),npm run lint,npm run format:check,npm test(22 pass),npm run pack:check(abap2ui5-embed-control-0.3.0.tgz).After the merge: create the GitHub release
v0.3.0on the merge commit -publish.yamlruns CI and publishes by trusted publishing. Then abap2UI5/abap2UI5'sfrontend/embed/package.json(^0.1.1) and root devDependency can move to^0.3.0, and samples-embed-control takes it with its lockfile bump.🤖 Generated with Claude Code
https://claude.ai/code/session_01TrfF51pia7m6tLZQF2G2ua
Generated by Claude Code