Repository navigation
v0.8.7: version, changelog and release notes (chain 22, constraint set 11) - #198
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
…t 11) - Workspace version 0.8.7: Cargo.toml, the seven workspace crates in Cargo.lock (cargo update -w on the build droplet; offline failed on the rand-zkvm-cuda git dependency), the rand_getVersion test. - CHANGELOG: Unreleased becomes v0.8.7 (tag date a PLACEHOLDER), with a row for #197's cutover-fleet-chain22.sh and the asset list. - docs/releases/v0.8.7.md: the set-11 gas change as a governance record (bundle 20 479 -> 22 527, auth 1 279 -> 1 407, msauth 436 159 -> 355 775; the per-row weights), the chain-22 cut, the operator upgrade steps and the rollback. The chain-22 genesis hash and the CHAIN_CONSTRAINT_SETS row are PLACEHOLDER-... until the cut. - README release table: v0.8.7. AGENTS.md: #194 is merged. Not tagged, not signed, not published. Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01YGaYNLS2uLR7w6m2JtejVo
dendisuhubdy
force-pushed
the
release/v0.8.7
branch
from
November 20, 2026 01:15
5de90d2 to
481b17f
Compare
Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01YGaYNLS2uLR7w6m2JtejVo
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.
The v0.8.7 bump: the chain-22 release on zkVM constraint set 11. Nothing is tagged, signed or published. The owner tags and signs on a real TTY (sequence below). Do not merge until the owner is ready to tag; merge with a squash, then tag the merge commit.
Changes
Cargo.tomlCargo.lockcargo update -won the build droplet, because--offlinefailed on therand-zkvm-cudagit dependency. The diff is exactly those 7 lines.crates/randprotocol-node/src/rpc.rsrand_getVersiontest expects 0.8.7CHANGELOG.mdUnreleasedbecomesv0.8.7 — PLACEHOLDER-TAG-DATE; new rows for #197 (cutover-fleet-chain22.sh) and the version; the asset listdocs/releases/v0.8.7.md(new)README.mdAGENTS.mdSame shape as v0.8.6's bump (
6eeed699), plus the release notes. v0.8.6 had no notes file; a chain cut needs one, as chain 21 haddocs/chain21-cut-runbook.md.Placeholders, filled at the tag or the cut:
PLACEHOLDER-TAG-DATE,-TAG-COMMIT,-CI-RUN,-SHA256SUMS,-CHAIN22-GENESIS-HASH, theCHAIN_CONSTRAINT_SETSrow(22, "PLACEHOLDER-CHAIN22-GENESIS-HASH", 11),,-LAUNCH-UTCand-OWNER-SIGNOFF(for the gas governance record).grep -rn PLACEHOLDER- CHANGELOG.md docs/releasesfinds them all.One doc conflict for the owner.
docs/deploy.mdsays "A release for chain 22 is tagged only from a tree on whichcheck-limitspasses". That cannot hold for v0.8.7:stageandbeacon-initneed the release before the cut, and the genesis hash, and so the row, exist only after it. v0.8.0 and chain 21 worked the same way (genesis-chain21.jsonlanded after the tag, in58c7afd2). The notes read the sentence as applying to the first release after the cut.Test
On the build droplet (the Mac built nothing):
cargo test --release --locked -p randprotocol-node --lib version_reports_build_and_chainpassed (1 test). The two v0.9.0-gated defaults (RPC-201, PRIV-601) key on0.8.and are unaffected.Tag-and-sign sequence (the owner)
0. Preconditions:
ciis green on the merge commitM;1. Tag fullnode (annotated, naming the green run;
release.ymlrefuses otherwise):release.ymlthen does the following:rand-node;rand-node,rand,rand-prover,msauth-vk-production.bin,perp-vk-production-t18-pg14-in16-pub{7,8,9,10}-p2h20.binandSHA256SUMS.2. Check
SHA256SUMSbefore signing. It must have eight lines. The seven chain-22 fleet files must be listed at these values:3. Sign. Run this in a separate, real Terminal; the key is passphrase-protected. Use a checkout at the tag:
A second holder, when there is one, uses
deploy/sign-release.sh --appendand uploadsSHA256SUMS.sig2.4. Verify the published set. Run the library under
bash; sourced into zsh it resolves paths wrongly:The cutover's
preflightre-checks all seven fleet files against the signed sums (RELEASE_SUMS=$REL/SHA256SUMS).5. Snapshot tags on the other repositories. These follow v0.8.6's convention: an annotated
v0.8.7tag naming the monorepo commit. Per CLI-751, outside fullnode such a tag marks the snapshot, not a release of that repository. Tag only after the monorepo pin commit for v0.8.7 lands, each at the commit that commit pins:randprotocol/zkp-circuits, at the pin41d64acd. The v0.8.6 circuits tag was 20 commits past the node's pin (CLI-751);6. After the roll. Move the monorepo's
configuration/release/pin to the signed v0.8.7 pair:SHA256SUMS,.sigand the set-11 msauth blob. The fullnode'sdeploy/lib/verify-release.shhas changed since v0.8.6, so the monorepo's pinned copy anddeploy-scripts/lib/verify-release.upstreamalso need refreshing. Without that,respawn-host.shrefuses.🤖 Generated with Claude Code
https://claude.ai/code/session_01YGaYNLS2uLR7w6m2JtejVo