Repository navigation
Prepare release 0.2.0: name abap2UI5 1.147.0 and the embed app that replaced frontend-new - #28
Merged
Merged
Conversation
abap2UI5/frontend-new is gone: its app is abap2UI5's frontend/embed, delivered as the standard_new and cloud_new branches of abap2UI5/frontend. The 0.2.0 changelog, the control's comments, the test and AGENTS.md named the old repository. And "the abap2UI5 release after 1.146.0" has a number now: 1.147.0 is cut on abap2UI5's main, with componentName, ownsHash, the mobile setup left to the host and the prefixed custom-control roots in its changelog section. The README and the 0.2.0 section name it, so the package page on npm does not send readers looking for "the release after". Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Te3BRpRpxNhZAYnrQL6Gdt
Member
Author
|
The first run of It is the same intermittent failure that turns the nightly run on
🤖 Generated with Claude Code Generated by Claude Code |
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.
Text-only changes before the 0.2.0 tag. The code is unchanged.
frontend/embed, which ships as thestandard_newandcloud_newbranches of abap2UI5/frontend. These places still named the old repository: the 0.2.0 changelog section, the comment aboveCOMPONENTinContainer.js, a test comment and AGENTS.md.main. Its changelog section hascomponentName,ownsHash, the mobile setup left to the host, and the prefixed custom-control roots. The package README, the 0.2.0 section, theownsHashproperty comment and AGENTS.md now say 1.147.0. Without this, the npm page of 0.2.0 would describe that release only as "the release after 1.146.0". Sections that are already released (0.1.1, 0.1.0) are unchanged.Best merged right after abap2UI5 1.147.0 is tagged and before the GitHub release v0.2.0.
Checked locally:
npm run lint,format:check,npm test(21/21),pack:check,consumer:check(UI5 CLI 3.11.14 and 4.0.71), andnode scripts/release-check.mjs v0.2.0, also run withGITHUB_REPOSITORY=abap2UI5/embed-control. Result: "tag, version, changelog and repository agree".🤖 Generated with Claude Code
https://claude.ai/code/session_01Te3BRpRpxNhZAYnrQL6Gdt
Generated by Claude Code