Repository navigation
chore: bump the pinned abap2UI5 framework commit - #280
Merged
Merged
Conversation
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.
Weekly re-resolve of
A2UI5_PINagainst abap2UI5 main (d4b17595d3a858e558e94a96e655f73645f9becd) —what node-setup, the Pages build and the e2e smoke run against.
The abaplint configs resolve main directly (unpinned), and the
nightly e2e keeps testing main tip as the canary.
The verdict at the new pin
The full backend build and the strict e2e smoke over all ports ran green at the new pin. This is a routine bump.
Run: https://github.com/abap2UI5/samples-controls/actions/runs/40488922892
Every FAIL line is a port whose live wire broke against the new
framework commit — or a harness effect, see
.claude/skills/e2e-debugging.