chore(release): v1.1.14 — restore release binaries + build-health#218
Closed
avrabe wants to merge 2 commits into
Closed
chore(release): v1.1.14 — restore release binaries + build-health#218avrabe wants to merge 2 commits into
avrabe wants to merge 2 commits into
Conversation
Release-engineering + build-health release; no optimizer behavior change (falcon behavioral gate unchanged from v1.1.13). - #142/#216: release-binary uploads restored + unified artifact standard (decoupled the release job from the fragile wasm32 build; verified by retroactively shipping v1.1.13's binaries via workflow_dispatch). - #202: un-redded main after wasmtime-45 + criterion floated-dep breaks. - #201: removed vestigial Sphinx scaffold (superseded by rivet). Refs #142
The WASM Build job used `dtolnay/rust-toolchain@1.93.1`, which pins the action's git tag — not Rust. That old action revision derives the "stable" version from the calendar; the estimate has now drifted to a not-yet-released 1.100.0, so rustup fails and the job went red on main (orthogonal to the v1.1.14 release, which builds native binaries only). Fix: `@stable` (current action code, like every other job) + explicit `toolchain: "1.93.1"` so the intended pin actually installs Rust 1.93.1.
This was referenced Jun 14, 2026
Contributor
Author
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.
v1.1.14 release bump (supersedes #217, whose branch stopped re-triggering CI after pushes/reopen — a GitHub quirk).
Contents (all already on main since v1.1.13):
workflow_dispatch..context, criterionblack_box).Plus a CI fix folded in: the WASM Build job pinned
dtolnay/rust-toolchain@1.93.1, which pins the action tag, not Rust — that stale action computes "stable" from the calendar, now overshooting to a non-existent Rust 1.100.0, breaking the job onmain. Switched to@stable+ explicittoolchain: "1.93.1".No optimizer behavior change — falcon behavioral gate unchanged from v1.1.13.
After merge: tag
v1.1.14→ release workflow ships per-OS binaries + SBOM + signed checksums on the normal tag path.🤖 Generated with Claude Code