chore(release): the published crate predates its sixth backend - #4491
Merged
Merged
Conversation
t27c on crates.io is 0.2.0. The compiler gained gen-js in #4472, so the version a user installs from the registry cannot emit JavaScript while the compiler on master can. Minor rather than patch: a new backend is added functionality, and additive -- the five existing targets are untouched. Both files the release pipeline's VERSION TRUTH gate reads for a t27c-v* tag are bumped together, because the gate refuses a tag whose manifests do not already say what the tag says, and a half-bumped pair fails the tag rather than the PR. ZENODO_DEPOSITION_T27C stays unset on purpose, so zenodo-publish.yml skips and mints no DOI. A DOI cannot be withdrawn; enabling it is its own decision, not a side effect of cutting a crate release. Closes #4490 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
Contributor
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.
The published crate predates its sixth backend
crates.io serves
t27c 0.2.0— one version, 13 downloads, nothing yanked.gen-jslanded on master in #4472. So the compiler a reader installs withcargo install t27ccannot emit JavaScript while the compiler on master can,and for anyone who has not cloned this repository the registry copy is the only
t27c that exists.
Minor rather than patch, because a sixth backend is added functionality: the
five existing targets — Zig, Verilog, Verilog (HIR), C, Rust — are untouched.
What moves, and why exactly these files
bootstrap/Cargo.tomlt27c-v*tag.zenodo.jsonCargo.lockdocs/now/2026-09-21-…mdcheck-now-freshnessVERSION TRUTH checks both manifests against the tag. A half-bumped pair fails the
tag, not the pull request — which is the expensive place to discover it.
Rehearsed here, not left to CI
reaches
Uploading t27c v0.3.0and stops itself, exit 0. An earlier attemptrefused outright over one uncommitted manifest — the gate working, not failing.
No DOI is minted, deliberately
zenodo-publish.ymllooks upZENODO_DEPOSITION_T27C;gh variable list --repo gHashTag/t27returns nothing, so that job skips. A DOI cannot be withdrawnonce minted, so enabling it is its own decision and not a side effect of cutting
a crate.
What this does NOT establish
The dry run proves the crate packages and that the manifests agree with the tag.
It runs no generated JavaScript and compiles none — that
t27c gen-jsis correctis what #4471 and #4472 argued, and nothing here re-argues it.
Unlike a branch, a published version is permanent:
0.3.0can be yanked,never replaced and never reused.
Closes #4490