🦋 New version release - #193
Merged
Merged
Conversation
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/logger@4.5.3
Patch Changes
be2b735: Commit the repo's formatting and stop the release pipeline from dirtying its own working tree.
Dropping
cargo publish --allow-dirtysurfaced what the flag had been hiding:release.yml'sown
Formatstep ranpnpm format, which rewrites files and never commits them, socargo publisha few steps later saw a dirty tree. Every crate published from this repo silentlycarried uncommitted reformatting.
mainwas format-drifted across seven files with nothing checking — PR checks ranoxlintbutnever a formatter, and
pnpm format:checkdid not exist.pnpm formatis now a no-op onmain.format:check(oxfmt + ruff +cargo fmt+gofmt) runs in PR checks.release.yml'sFormatbecomesFormat check— check, never rewrite.versionlifecycle now ends withoxfmt --write CHANGELOG.md package.json,because
changeset versionemits both in a shape oxfmt disagrees with; without it the nextrelease PR would land unformatted and break
cargo publish --lockedagain.This release also re-publishes to crates.io, NuGet, and the Go module tag, which stalled at
4.5.0while npm and PyPI went to4.5.2.