Version Packages (alpha)#16
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/next
branch
4 times, most recently
from
392401a to
db15255
Compare
github-actions
Bot
force-pushed
the
changeset-release/next
branch
from
db15255 to
176e154
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
1 participant
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 publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to next, this PR will be updated.
nextis currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitonnext.Releases
react-class-variants@2.0.0-alpha.8
Patch Changes
3c3fcc0: Harden release automation so npm dist-tag validation happens before publish and GitHub Actions can synchronize dist-tags with npm's OIDC exchange flow instead of relying on a long-lived repository token.
The release workflow now also validates GitHub release/changelog readiness before publish, recovers safely on reruns after partial publish success, and catches malformed
.changeset/*.mdfiles during normal changeset coverage checks instead of at release time.It also waits through short npm registry propagation delays before deciding that a freshly published version or dist-tag update is still missing.
The post-publish reconciliation path is now simpler too: the workflow runs npm dist-tag sync and GitHub Release sync as separate steps and applies the final failure gate afterward.
Release tooling is also covered by ESLint now, which caught and prevents a latent dist-tag update bug in the non-no-op npm mutation path.
7c72ce5: Fix package packing and publishing from a clean checkout so the tarball always includes the built
dist/entrypoints even thoughdist/is gitignored. Packed-export validation now exercises that clean-checkout flow as a standalone check, and the local changeset gate now considers staged, unstaged, and untracked release-affecting files before it decides whether a changeset is required.