chore(release): prepare v0.20.0 beta-30 - #723
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 8d1e76bdab
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
8d1e76b to
d957ff8
Compare
f4a02a1 to
83c0f8c
Compare
|
@codex review |
|
Codex Review: Didn't find any major issues. Breezy! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Signed-off-by: Jeremi Joslin <jeremi@joslin.fr>
Signed-off-by: Jeremi Joslin <jeremi@joslin.fr>
Signed-off-by: Jeremi Joslin <jeremi@joslin.fr>
Signed-off-by: Jeremi Joslin <jeremi@joslin.fr>
Signed-off-by: Jeremi Joslin <jeremi@joslin.fr>
83c0f8c to
c7a9a7a
Compare
|
@codex review |
Signed-off-by: Jeremi Joslin <jeremi@joslin.fr>
|
@codex review |
|
Codex Review: Didn't find any major issues. More of your lovely PRs please. Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
1 participant
Summary
Train-independent prerequisites #722, #724, #725, and #727 landed before this branch. Protected pre-tag CI can now validate the current manifest, verify the exact future evidence tag without creating it early, remain self-contained, and bootstrap the exact unpublished candidate archive.
Breaking changes
registry_relayvocabulary prefixholderBoundBatchMaxSizeVerification
release/scripts/registry-release validate-currentrelease/scripts/registry-release prepare --version 0.20.0 --release-id beta-30python3 -m unittest discover -s release/scripts -p test_*.py(261 passed)python3 release/scripts/check-gates-inventory.py(114 gates)products/evidence/scripts/check-contracts.shcargo fmt --all --checkcargo metadata --locked --no-deps --format-version 1cargo check --locked --manifest-path products/manifest/fuzz/Cargo.tomlcargo check --locked --manifest-path products/platform/fuzz/Cargo.tomlnpm test(323 passed on protected main)npm run checknpm run check:archive-lock -- --base-ref origin/mainDOCS_DOCSET=v0.20.0 npm run build:archivenpm run archive:snapshot -- v0.20.0 --verify-locknpm run check:archivesfrom a missing local v0.20 bundle (1 candidate bootstrapped; 125,750 internal links and assets checked)The immutable v0.20.0 tag remains absent. Candidate construction will start only after this PR merges and protected-main CI passes for the exact merge SHA.