chore: add changeset for the toast hover-pause stack fix#223
Merged
Conversation
#222 merged without a changeset, so nothing was bumped and the Release run failed trying to re-publish versions already on npm — the fix is on main but consumers still get the pre-fix courier-ui-toast@2.1.10. Patch bump on courier-ui-toast; changesets cascades the dependent bumps (courier-react/react-17/react-components/vue/angular) at version time. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
🦋 Changeset detectedLatest commit: ace7e39 The changes in this PR will be included in the next version bump. This PR includes changesets to release 6 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Why
#222 merged without a changeset. With no pending changeset,
changeset publishhad nothing to bump and tried to re-publish the versions already on npm, so the Release run failed on all 10 packages:(run 30127863348)
Net effect: the fix is on
main, but@trycourier/courier-ui-toast@lateston npm is still 2.1.10 — the pre-fix build from #220 — so consumers still have the bug.What this does
Adds the missing patch changeset for
@trycourier/courier-ui-toast.yarn changeset status --verboseon this branch:Only
courier-ui-toastis listed in the changeset — the rest areupdateInternalDependencies: patchcascades that changesets applies at version time.Merging this opens a "Version Packages" PR; merging that publishes 2.1.11.
Note on the earlier red run
"Version Packages (#221)" also shows a failure, but that one did publish — npm has 2.1.10 and its siblings. It exited non-zero because a subset of packages reported "already published" within the same run. Don't confuse it with the run above, which published nothing.
🤖 Generated with Claude Code