chore: reset version to 0.0.0 after failed 0.1.0 release#12
Merged
Conversation
A failed release run pushed a 0.1.0 bump and marked the initial entries as released. Revert to 0.0.0 and move them back under Unreleased so the release can be retried cleanly. Signed-off-by: Ivan Alvarez Sabin <ivanasabi@ext.inditex.com>
❗ This Pull Request will not trigger a releaseA Pull Request with no |
🚀 Release Preview SuccessYou are going to release the version minor with the following changes: 0.1.0 - 2026-07-20Added
💡 Merge Strategy: Create a merge commitRemember to use the 'Create a merge commit' strategy to merge this Pull Request ( |
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
A prior release run pushed a
0.1.0bump directly tomainand marked the initial entries as released, but publishing failed (prettier check on the generated CHANGELOG). This PR resets the repo so the release can be retried cleanly.0.1.0→0.0.0inpackage.jsonandpackage-lock.json(root +packages[""]).## [Unreleased]/### Added, removing the premature[0.1.0]section and release links.Related: the workflow was fixed separately (push to
main+develop) to runprettier --writeon the generated CHANGELOG, and the stray0.1.0git tag was deleted.Test plan
0.0.0in bothpackage.jsonandpackage-lock.json.prettier --check CHANGELOG.mdpasses.