Repository navigation
chore: register image 0.5, musl 0.28 and runtime 0.19 - #717
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.
Register the published image 0.5.0, musl 0.28.0 and LLVM runtime 0.19.0 source group. The image archive supplies openkal-ld, openkal-run, openkal-tools and openkal-bind; all six recipes select the same publicly released ABI dependency group. Existing version entries and the index client floor remain unchanged.
Each new canonical archive has been downloaded, its declared package version checked against the merged source, and its GitCode mirror downloaded and compared byte for byte. The image source passed all five native checks; musl and runtime each passed all ten final source checks. These source results are distinct from this PR's candidate consumers and subsequent ordinary public installation verification.
Validation: 22 updater integration tests and four wrapper tag-selection tests passed with the pinned updater. The complete descriptor audit preserves every existing version. All 141 distinct GitCode URLs referenced by the six changed recipes were downloaded and matched their declared SHA256 values, including historical releases. Candidate and workspace CI remain required before merge. After admission, GLOBAL and CN consumers use the published index artifact without path overrides.
Upstream source verification: image, musl, runtime.