Repository navigation
🦋 New version release - #15
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/audit@0.4.1
Patch Changes
4e17d0e: Gate each registry's publish on that registry, not on a parsed stdout flag
Every non-npm publish step was gated on
steps.changesets.outputs.published, which changesets/action derives by parsing publish stdout. That fails open two ways, both seen for real on 2026-08-20: if npm published in an earlier run, a retry finds nothing new so the flag is false and all four remaining registries skip — a green run that ships nothing; and@changesets/cli3.x renamed the very line the action parses, which silently switched every non-npm publish off in a sibling repo while its releases stayed green.Each step now gates on whether its own registry already carries
package.json's version, so a retry publishes exactly what is missing, and a final step fails the run if npm shipped a version the others didn't. NuGet is reported but not asserted — its index lags an accepted push by minutes to tens of minutes, and a guard that reddens successful releases gets deleted.