chore(main): release ui 0.1.0#29
Merged
lukeocodes merged 1 commit intomainfrom May 6, 2026
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
lukeocodes
added a commit
that referenced
this pull request
May 6, 2026
…ly (#30) chore(release): unpin release-as 0.1.0, drop bogus duplicate changelog entry The release-please config still had `release-as: 0.1.0` from the original release pin (commit 53a4f04). That kept release-please from ever bumping past 0.1.0: - PR #29 (autogenerated release for the fix(ui) commit) was titled "release ui 0.1.0" and added a duplicate `## [0.1.0]` changelog entry that compared 0.1.0 to itself. - On merge, release-please tried to re-create tag `ui-v0.1.0`, which already existed from the original 2026-04-30 release. GitHub responded with "already_exists" and the workflow failed. - Net effect: my CSS scoping fix (commit 8742c18) is in main but not on npm. npm still has the original unfixed 0.1.0. Fix: - Remove `release-as: 0.1.0` so release-please bumps from conventional commits going forward. - Delete the duplicate `## [0.1.0]` block PR #29 added to the changelog. The next release-please PR will re-add it under the correct bumped version (0.1.1 per `bump-patch-for-minor-pre-major: true` plus the existing `fix:` commit). After this lands release-please will open a new PR titled 'release ui 0.1.1' (or 0.2.0 depending on what other commits are in the queue). Merging that will publish the fix to npm and trigger the CDN deploy.
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.
🤖 I have created a release beep boop
0.1.0 (2026-05-06)
Bug Fixes
This PR was generated with Release Please. See documentation.