fix(ci): keep the release train on GitHub-hosted runners - #181
Merged
Conversation
The Blacksmith migration (#178) blanket-moved every ubuntu-latest job, including the four publishing workflows. npm rejects sigstore provenance minted anywhere but GitHub-hosted runners, so the truffle-v0.7.10 release died at both npm publish steps ("Unsupported GitHub Actions runner environment: self-hosted") after all binaries had built, and release-please then stopped at its build gate — nothing reached npm or crates.io, and the release is still a draft. Revert the six release-path workflows (release-please, release-preflight, release-sidecar, release-cli's siblings napi-build, release-npm, publish-crates) to ubuntu-latest and pin the constraint in comments on each publish job so the next runner migration can't silently reintroduce it. CI/test workflows keep their Blacksmith runners — the speed matters there and nothing in them mints provenance. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
What happened to truffle-v0.7.10
The Blacksmith migration (#178) blanket-moved every
ubuntu-latestjob — including the publishing workflows. npm refuses to mint sigstore provenance from self-hosted-class runners:Sequence: all five sidecar binaries and all five NAPI targets built and uploaded fine (checksums pinned in
f9f2c89), then both npm publish jobs died on the first platform package, and release-please stopped at its "require successful builds" gate — so crates.io and npm main publishes were never dispatched, the release was never un-drafted, and nov0.7.10SemVer tag was minted.Blast radius: zero. Verified:
truffle-v0.7.10is still a draft, npm shows nothing past 0.7.9 for any package, crates.io max version is 0.7.9. Nothing partial escaped to any registry.The fix
Revert the six release-path workflows to
ubuntu-latest(release-please,release-preflight,release-sidecar,napi-build,release-npm,publish-crates—release-cliescaped the migration, which is why CLI binaries succeeded) and pin the constraint in comments on each publish job so the next runner migration can't silently reintroduce it. CI/test/analysis workflows keep Blacksmith — the speed matters there and nothing in them mints provenance or uses trusted publishing.Recovery path for the release
Recovering 0.7.10 in place isn't viable: the publish jobs are tag-gated, and a
workflow_dispatchattruffle-v0.7.10executes the tag's (broken) workflow definitions; rebuilding at a recovery ref would also produce sidecar bytes that no longer match the pinned checksums. Since nothing was published, the clean path is:fix(ci)commit.truffle-v0.7.10as a dead draft and its tag in place — deleting the tag would make release-please try to re-cut 0.7.10; drafts are invisible to consumers.🤖 Generated with Claude Code
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.