Repository navigation
chore(release): t27c 0.5.1 -- device DNA is named on every die (Closes #7762) - #7763
Merged
Merged
Conversation
Refs #7669, #7758, #7761 t27c 0.5.0 refuses the DNA of every die whose FUSE_DNA tail is not die A's `0x4F`. On die B, `t27c silicon` passed but wrote `device_dna: null` (#7759). The fix is #7761. R3-3 operators build from the tag, so the fix only reaches their receipts through a new tag. This PR bumps the three files that release.yml's VERSION TRUTH gate reads for a `t27c-v*` tag, all in one commit, as #7603 did for 0.5.0: - `bootstrap/Cargo.toml` 0.5.0 → 0.5.1 - `.zenodo.json` 0.5.0 → 0.5.1 - `Cargo.lock` t27c entry; `cargo metadata --locked` is consistent No code change. Patch, not minor: it relaxes a rule in the verified specs, adds no subcommand, and leaves the backends untouched. `ZENODO_DEPOSITION_T27C` stays unset, so no DOI is minted. Order: #7761 and this PR merge, then the tag `t27c-v0.5.1` goes on that master commit. After it, the ternary_link seal is re-saved by the tag build (as #7681 did) and die B is rerun for #7759. 🤖 Generated with [Claude Code](https://claude.com/claude-code) EOF2 chore(release): t27c 0.5.1 -- device DNA is named on every die (Closes #7762) t27c 0.5.0 refuses the DNA of any die whose FUSE_DNA tail is not die A's 0x4F (#7758, fixed by #7761). R3-3 receipts come from the tag build, so the fix needs a tag. Both manifests the release VERSION TRUTH gate reads for t27c-v* (bootstrap/Cargo.toml, .zenodo.json) and the t27c entry in Cargo.lock move together (cargo metadata --locked: consistent). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
Collaborator
Author
|
t27b-native-ratchet is red here exactly as on master, so it is not caused by this PR. The ratchet line on this run (37768930215): |
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
1 participant
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.
Closes #7762
Refs #7669, #7758, #7761
t27c 0.5.0 refuses the DNA of every die whose FUSE_DNA tail is not die A's
0x4F. On die B,t27c siliconpassed but wrotedevice_dna: null(#7759). The fix is #7761. R3-3 operators build from the tag, so the fix only reaches their receipts through a new tag.This PR bumps the three files that release.yml's VERSION TRUTH gate reads for a
t27c-v*tag, all in one commit, as #7603 did for 0.5.0:bootstrap/Cargo.toml0.5.0 → 0.5.1.zenodo.json0.5.0 → 0.5.1Cargo.lockt27c entry;cargo metadata --lockedis consistentNo code change. Patch, not minor: it relaxes a rule in the verified specs, adds no subcommand, and leaves the backends untouched.
ZENODO_DEPOSITION_T27Cstays unset, so no DOI is minted.Order: #7761 and this PR merge, then the tag
t27c-v0.5.1goes on that master commit. After it, the ternary_link seal is re-saved by the tag build (as #7681 did) and die B is rerun for #7759.🤖 Generated with Claude Code