chore: sync Registry Stack identifiers to the v0.33.0 release source - #8
Merged
Merged
Conversation
Signed-off-by: Jeremi Joslin <jeremi@joslin.fr>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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.
Rebind the publisher bundle to the exact Registry Stack v0.33.0 release source commit.
The release publication dispatch fails closed unless
src/upstream/source.jsonnames the exact released source commit and identifier catalog digest. The
previous sync pinned
60b0c2b0, which is the release-preparation commit; mainhas since advanced through two release-control fixes, and the candidate is bound
to
125f67b37b424ae7a43d8760c33fb73d4be8b8a1.Regenerated with:
What changed
Only the source-commit binding. The identifier catalog is byte-identical:
catalog_sha256stays800de6c787568677a26e2ccf4b0bc0fb5aaada4ac51e044a1b956b27fa3a1748artifact, schema, or route content moved
Verification
npm test(21 tests,check,check:problem-routes) passesnpm run checkreportspublic/ matches generated output