fix: restore Release Please release state - #50
Merged
Conversation
Contributor
Contributor
|
Preview package published. Floating PR tag: pnpm add @tomny-dev/uzi@pr-50Exact published version: pnpm add @tomny-dev/uzi@0.4.0-pr.50.151.1.6cb49e0Published version: Use the PR tag to track the latest preview build for this PR. Use the exact version to pin a specific build. |
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.
Summary
Restore the three Release Please-managed release artifacts to the last actually published release (
0.4.0).PR #48 manually advanced
package.json,CHANGELOG.md, and.release-please-manifest.jsonto0.5.0, but it was not a Release Please-generated release PR, so merging it did not create theuzi-v0.5.0tag or GitHub release. Release Please therefore interpreted the manifest as already released and opened #49 for0.6.0, incorrectly skipping the intended0.5.0release.After this correction lands, the existing Release Please workflow should generate/update a proper
0.5.0release PR from the still-unreleased changes on main. Merging that generated PR is what creates the tag/release and drives publishing perDEVELOPMENT.md.No product/runtime code is changed.