chore(release): publish v0.42.0 from main, including everything merged since the release PR - #2371
Merged
Merged
Conversation
…d since the release PR v0.42.0 was never published: the release-PR merge commit's publish failed on an empty `CARGO_REGISTRY_TOKEN`, and with `release_always = false` release-plz never retries from a later commit. Flip it to `true` (the release-plz default) so the next push publishes the version main already declares — from HEAD, so #2367, #2361 and #2369 ship in 0.42.0 — and fold their changelog entries out of `[Unreleased]` into the 0.42.0 sections whose text becomes the GitHub release body; the section date moves to the day it actually publishes.
pull Bot
pushed a commit
to TM312/rig
that referenced
this pull request
Aug 18, 2026
`true` was a one-push recovery for v0.42.0 (0xPlaygrounds#2371), not the steady state: it makes every merge that lands after a release PR part of that release, unreviewed and unchangelogged. The comment records how to recover next time.
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.
Merging this PR publishes v0.42.0 to crates.io from
mainas of the merge commit — with #2367, #2361, #2369 and anything else merged before it. Read that sentence twice before pressing the button.Why this exists
The release-PR merge commit for v0.42.0 (
2da030332, #2221) ranrelease-plz releaseat 01:47 UTC and failed on the very firstcargo publish(rig-derive): "please provide a non-empty token" —CARGO_REGISTRY_TOKENwas empty. Nothing was published (crates.io is still at 0.41.0 for every crate) and nov0.42.0tag exists. The secret has since been set (12:39 UTC), butrelease-plz.tomlhadrelease_always = false, so every push since logs "skipping release: current commit is not from a release PR" — a stranded release that nothing will ever retry.Meanwhile the cd run queued behind the release (for
57b4ad2bb) ran its release-plz step at 01:32 on a checkout that predates the merge, found no open release PR, and opened #2360 — a stale "0.41.0 → 0.42.0" duplicate that conflicts withmainon every manifest becausemainalready contains those bumps. #2360 should be closed, not refreshed.What this changes
release-plz.toml:release_always = true(release-plz's default). Publish whenever a crate's manifest version is ahead of crates.io, on any push tomain. That both recovers v0.42.0 now and makes a future token/network failure self-heal on the next push; once every crate for a version is on crates.io it's a no-op.[Unreleased]entries from feat(agent): restore raw provider response access at the agent level, on both surfaces (#2366) #2367 (raw provider responses on every completion) and chore(deps): lower dependency floors to what rig needs and stop raising them (#2195) #2369 (dependency floors) are folded into the0.42.0sections of the root,rig-core, andrig-agentchangelogs — that text is the GitHub release body — and the section date becomes 2026-08-17.No manifest version changes:
mainalready says 0.42.0 everywhere.What happens on merge
cd.yamlruns the gates (~40 min), thenrelease-plz releasepublishes the 22 crates in dependency order, creates thev0.42.0tag and the GitHub release forrig. The next push after that makes release-plz open the "chore: release v0.43.0" PR for whatever comes next (#2367 is breaking, so a minor bump pre-1.0).Verify afterwards:
curl -s https://index.crates.io/ri/g-/rig-core | tail -1→0.42.0;git ls-remote --tags origin v0.42.0.