fix: restore filters canary version - #581
Merged
Merged
Conversation
The menu rewrite (#242) committed a local snapshot version, `0.0.0-20260205122308`, as the package version. Changesets bumps from it, so the next canary came out as `0.0.0-canary.0` instead of `0.4.0-canary.5`. Also drop its CHANGELOG section, which only repeated entries from `0.4.0-canary.0`, `.1`, and `.4`.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
kianbazza
changed the title
kianbazza
marked this pull request as ready for review
September 30, 2026 02:19
This branch was successfully deployed
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.
Restores
@bazza-ui/filtersto0.4.0-canary.4so the next canary is0.4.0-canary.5, not0.0.0-canary.0.Motivation
#242 committed
0.0.0-20260205122308, a localchangeset version --snapshotoutput, as the filters version. Two effects:semver.inc("0.0.0-20260205122308", "patch")is0.0.0, and the prerelease counter restarts at 0, so chore: version canary packages (canary) #519 predicts0.0.0-canary.0. That sorts below0.4.0-canary.4and the0.3.2025091001onlatest.0.0.0-20260205122308was published to npm (on thecanarytag) in March. Since then, every canary publish retried that same version and got403 You cannot publish over the previously published versions, hidden by|| trueinci:publish:canary. That is the recurring filters failure in the publish logs.What's changed
packages/filters/package.json: version0.0.0-20260205122308→0.4.0-canary.4, the last real canary.packages/filters/CHANGELOG.md: removed the0.0.0-20260205122308section. Its three entries repeat0.4.0-canary.0,.1, and.4.changeset status --verboseon this branch:@bazza-ui/filters 0.4.0-canary.5,@bazza-ui/react 0.1.0-canary.17.Closes UI-631