Repository navigation
chore(release): prepare UI package release - #72
github-actions[bot] wants to merge 1 commit into
Conversation
|
This release proposal repeats a README correction already shipped in UI 2.6.0 via #67. The packaged tree has no change between 2.6.0 and current main. The stale Changeset was retained while synchronizing the public-distribution branch and should not cause a duplicate 2.6.1 publication. The correction is prepared in #73. Holding this version proposal as draft until that correction is reviewed. Merging #73 can also mirror the already-published 2.6.0 original tarball through the existing main workflow, so its explicit delivery effect is documented there. No new npm version is needed. |
|
The correction in #73 is merged, and the existing workflow has successfully mirrored the original UI 2.6.0 tarball. The README change proposed here was already included in that version. Closing this duplicate version proposal without publishing 2.6.1; no package version bump is needed for the original-tarball distribution tooling. |
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
@inkcre/ui-web@2.6.1
Patch Changes