Repository navigation
feat: sync Cargo version automatically in ci release - #115
Merged
Merged
Conversation
greenroom-gremlin Bot
added a commit
that referenced
this pull request
Oct 15, 2026
## [8.30.0](https://github.com/greenroom-robotics/mise/compare/mise@8.29.8...mise@8.30.0) (2026-10-15) ### Features * sync Cargo version automatically in ci release ([#115](#115)) ([b504fde](b504fde))
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.
mise ci releaseonly bumpedpixi.toml, so crate packages had to wire--extra-prepare-cmd "mise ci sync-cargo ..."and--extra-git-assetthemselves. That wiring breaks in multi-package mode, where semantic-release runs from each package dir rather than the repo root.Now, for every released package whose dir has a
Cargo.tomlwith a[package]table:[package].versionis set to the release version.Cargo.lock(walking up from the package dir, stopping at the git root) gets this crate's local entry bumped; registry entries with the same name are left alone.commit_releasein multi mode.version.workspace = truefails the release instead of bumping a version shared with other crates.bump-pixidoes the Cargo sync for the package dir of eachpixi.tomlit bumps. Non-crate packages and virtual workspace manifests are untouched.mise ci sync-cargokeeps its flags, so repos still using the workaround keep working (the second bump is a no-op) and can drop it once this is released. mise's own release workflow keeps the workaround until then, since CI installs the released binary.