Repository navigation
Release 0.2.0 - #27
Merged
Merged
Conversation
…er 3.9.10) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Te3BRpRpxNhZAYnrQL6Gdt
The package README's property table left it out; the control restarts the app on a change of ownsHash like on one of app, endpoint or params, as the changelog already says. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Te3BRpRpxNhZAYnrQL6Gdt
The entries under "Unreleased" become the section of 0.2.0: restart(), ownsHash, the component under the bundle's componentName, the size applied without a rendering, no start for an invisible control, and the fixes of the endpoint and params handling. A minor version: the control gains API and keeps all of 0.1.1's. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Te3BRpRpxNhZAYnrQL6Gdt
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
2 participants
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.
Merge after #26 and abap2UI5/samples-embed-control#13; then create GitHub release v0.2.0.
packages/embed-control/package.json0.1.1 -> 0.2.0 (lockfile bynpm version).CHANGELOG.md: the entries under "Unreleased" become## 0.2.0; an empty## Unreleasedstays on top, as in the 0.1.1 release (Release 0.1.1 #14). Headings carry no date in this file, so## 0.2.0follows its style (release-check.mjsaccepts both).restart(),ownsHash, thecomponentNameof the bundle) and keeps all of 0.1.1's.npm install @abap2ui5/embed-control); nothing else to change. "The abap2UI5 release after 1.146.0" stays as written - no abap2UI5 after 1.146.0 is published yet.Based on #26 (the tooling update), so it carries its commits; merging #26 first leaves only the release commit.
Why the order:
publish.yamlruns the whole CI first, including thesamplesjob, which runs samples-embed-control'smainwith this control - red until samples-embed-control#13 is merged.After the release:
npm install @abap2ui5/embed-control@0.2.0 --workspaces, commit - its e2e turns green.npm run bsp, commitsrc/02(AGENTS.md: and the floors in README andci.yaml).Checked:
node scripts/release-check.mjs v0.2.0(tag, version and changelog agree),npm run pack:check(abap2ui5-embed-control-0.2.0.tgz),npm run format:check.🤖 Generated with Claude Code
https://claude.ai/code/session_01Te3BRpRpxNhZAYnrQL6Gdt
Generated by Claude Code