chore(release): sync versions to 0.9.417 [skip release] - #6494
Merged
Conversation
github-actions
Bot
added
the
no-issue
Contributor
Reviewer's guide (collapsed on small PRs)Reviewer's GuideThis automated release write-back synchronizes version metadata across the Rust workspace and lockfile, updates the Homebrew source tag and version, and records the Unreleased changelog entries under release 0.9.417. File-Level Changes
Possibly linked issues
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
This was referenced Sep 11, 2026
macanderson
added a commit
that referenced
this pull request
Sep 11, 2026
## What & why `main` is red on `lockfile-sync` and every `--locked` build (the canary's report is #6495). The `stella-time` crate landed in #6488 with its `Cargo.lock` entry at `0.9.416`, while the release sync in #6494 had already moved every workspace crate to `0.9.417`. Neither tree was wrong on its own; the composition is. This regenerates the lock, which changes exactly that one line. Refs #6495 ## The witness - [x] No witness needed (lockfile only) — because: `cargo metadata --format-version 1 --locked` fails on `main`'s tip and passes with this lock. That command is the `lockfile-sync` gate step. ## The gate - [x] `make guards-fast` (lockfile-sync included) passes locally - [ ] the rest is CI's ## Fix over file - [x] Extra fixes in this PR: none - [x] Nothing was deferred ## Anything reviewers should know? Carries `unblocks-main` so the red-main hold does not block its own repair, and `no-issue` because the canary's own run marks that issue resolved once `main` recovers; nothing here closes it.
4 tasks
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
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.
Automated write-back from auto-tag.yml: v0.9.417 was just released, and this PR records that version everywhere the sources carry one —
[workspace.package].versioninCargo.toml(inherited by every crate)Cargo.lockpackaging/homebrew/stella.rb(build-from-source formula)CHANGELOG.md— whatever was under[Unreleased]now sits under[0.9.417]The workflow approves this PR's parked workflow runs, waits for the required checks, and merges once they are green (#5589). No action is needed unless a check fails.
Summary by Sourcery
Chores: