Repository navigation
ci: FULLNODE_TAG v0.8.7 (merge only after the fullnode v0.8.7 tag exists) - #15
Merged
Merged
Conversation
The real-node job tests the wallet against the v0.8.7 release (constraint set 11, chain 22) instead of building rand-node and rand-prover from the vendored fullnode. Merge only after fullnode v0.8.7 is tagged and its release published: until then `gh release download v0.8.7` fails and the job is red. No wallet version bump: a v0.8.x tag on this repository is a fleet snapshot tag, not a wallet release (README, CLI-751), and v0.8.6 bumped nothing here. Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01YGaYNLS2uLR7w6m2JtejVo
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
dendisuhubdy
marked this pull request as ready for review
November 21, 2026 04:46
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.
Do not merge until fullnode
v0.8.7is tagged and its GitHub release is published. Before that,gh release download v0.8.7in the real-node job fails and the job goes red. Draft until then.What
.github/workflows/node-integration.yml:FULLNODE_TAG: ""→FULLNODE_TAG: v0.8.7. The real-node job then downloadsrand-node/rand-proverfrom the v0.8.7 release (constraint set 11, chain 22), checks them againstSHA256SUMS, and runsscripts/e2e-node.sh. It no longer builds them fromcore/vendor/fullnode. The header comment is updated to match. Emptying the variable again restores the vendored-build path.Not bumped
There is no wallet version change. v0.8.6 bumped nothing in this repository. Per the README (CLI-751), a
v0.8.xtag here is a fleet snapshot tag, not a wallet release; the newest wallet is still 0.8.3.Check after the tag
RAND_MSAUTH_VKto the vendoredmsauth-vk-test.bin, so the release binary needs no key beside it.feat/cs11-revendor60a7d03, not at the v0.8.7 tag. If the real-node run against the release is green, nothing more is needed. A re-vendor to the tag is optional.Fullnode release PR: randprotocol/fullnode
release/v0.8.7.🤖 Generated with Claude Code
https://claude.ai/code/session_01YGaYNLS2uLR7w6m2JtejVo