Repository navigation
🦋 New version release - #9
Merged
Merged
Conversation
brentrager
force-pushed
the
changeset-release/main
branch
from
August 20, 2026 18:03
da92d8d to
4ae7253
Compare
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@smooai/audit@0.2.1
Patch Changes
60bc0dc: Fix version sync so released artifacts carry the version they were released as.
version:syncran afterchangeset publish, mutating the manifests in the CIworkspace where nothing ever committed them. Every git tag therefore shipped
0.0.0inpython/pyproject.toml,rust/audit/Cargo.toml,go/version.go(
audit.Version), andSmooAI.Audit.csprojwhile npm, PyPI, crates.io, andNuGet all showed 0.2.0 — and
cargo publish --allow-dirtyexisted only totolerate the resulting dirty tree.
The sync now runs in the changesets
versionlifecycle, so the bumped manifestsare committed with the release. A new
pnpm version:checkfails CI on any drift,including a
go.modmodule path whose/vNsuffix disagrees with the major.cargo publishis now--locked.