Skip to content

chore(release): the published crate predates its seventh backend - #4504

Merged
gHashTag merged 1 commit into
masterfrom
chore/t27c-0-4-0
Sep 21, 2026
Merged

gHashTag merged 1 commit into
masterfrom
chore/t27c-0-4-0

Conversation

@gHashTag

Copy link
Copy Markdown
Owner

t27c on crates.io is 0.3.0. The compiler gained gen-ts in #4502, so the
version a user installs from the registry cannot emit TypeScript while the
compiler on master can.

Minor rather than patch: a new backend is added functionality, and additive —
the six existing targets are untouched.

The three files, and why they move together

file from to
bootstrap/Cargo.toml 0.3.0 0.4.0
.zenodo.json 0.3.0 0.4.0
Cargo.lock 0.3.0 0.4.0

The first two are what release.yml's VERSION TRUTH gate reads for a t27c-v*
tag. It refuses a tag whose manifests do not already say what the tag says, so a
half-bumped pair fails the tag, not this PR — and a tag that fails after one
registry leg has written is the failure mode the pipeline's header documents at
length. The lockfile is the mechanical consequence of the first (cargo update -p t27c).

No DOI

ZENODO_DEPOSITION_T27C stays unset, so zenodo-publish.yml skips. A DOI cannot
be withdrawn; enabling it is its own decision, not a side effect of cutting a
crate release.

The reds to expect

coverage, Corpus ratchet and test-ratchet are red on master itself — see
the measurement table on #4502. Nothing in a three-line version bump moves them.

Closes #4503

t27c on crates.io is 0.3.0. The compiler gained gen-ts in #4502, so the version
a user installs from the registry cannot emit TypeScript while the compiler on
master can. Minor rather than patch: a new backend is added functionality, and
additive -- the six 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 #4503

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

📓 NotebookLM Notebook linked to this PR

This notebook contains session context, decisions, and artifacts for this work.

@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-09-21 07:48:16 UTC

Summary

Status Count
Total Open PRs 21
PRs with Failing Checks 18
PRs with All Checks Green 3
READY 2
FAILING 18
PENDING 0
NO CHECKS YET 0

These columns do not partition: 2 + 18 + 0 + 0 = 20, and there are 21 open PRs. A PR is being counted twice or not at all.

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=403499176a5d != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

@gHashTag
gHashTag merged commit aca5700 into master Sep 21, 2026
36 of 40 checks passed
@gHashTag
gHashTag deleted the chore/t27c-0-4-0 branch September 21, 2026 08:00
@gHashTag
gHashTag restored the chore/t27c-0-4-0 branch September 28, 2026 10:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

t27c 0.4.0: the registry crate predates its seventh backend

1 participant