fix(changelog): remove changes related to unreleased commits #68
Conversation
This file contains 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
There was a bug with v1.0.1-next.1 tag pointing at a wrong commit hash, which resulted in the last two releases to NPM fail. This bug was caused by an attempt to update a semantic-release-bot commit and force-pushing it to 'next' branch. The commit hash changed and so semantic release had no reference to the commit tagged by v1.0.1-next.1. The solution was to force-update the referenced commit hash in v1.0.1-next.1 tag.
AnnaRybkina
approved these changes
Sep 18, 2023
github-actions bot
pushed a commit
that referenced
this pull request
Sep 18, 2023
## [1.0.1-next.1](v1.0.0...v1.0.1-next.1) (2023-09-18) ### Bug Fixes * add test case for negative button as it is not just modifier anymore but it is own button type ([#63](#63)) ([c9d4950](c9d4950)) * **buttons:** set secondary variant styles by default ([#67](#67)) ([cde4077](cde4077)) * **changelog:** remove changes related to unreleased commits ([#68](#68)) ([364a355](364a355)) * use new button classes and improve conditions ([#62](#62)) ([1c9fa6c](1c9fa6c))
github-actions bot
pushed a commit
that referenced
this pull request
Sep 19, 2023
## [1.0.1-next.1](v1.0.0...v1.0.1-next.1) (2023-09-19) ### Bug Fixes * add test case for negative button as it is not just modifier anymore but it is own button type ([#63](#63)) ([c9d4950](c9d4950)) * **buttons:** set secondary variant styles by default ([#67](#67)) ([cde4077](cde4077)) * **changelog:** remove changes related to unreleased commits ([#68](#68)) ([364a355](364a355)) * update test for a button and changelog ([#69](#69)) ([4eb675e](4eb675e)) * use new button classes and improve conditions ([#62](#62)) ([1c9fa6c](1c9fa6c))
github-actions bot
pushed a commit
that referenced
this pull request
Sep 19, 2023
## [1.0.1-next.2](v1.0.1-next.1...v1.0.1-next.2) (2023-09-19) ### Bug Fixes * add test case for negative button as it is not just modifier anymore but it is own button type ([#63](#63)) ([c9d4950](c9d4950)) * **buttons:** set secondary variant styles by default ([#67](#67)) ([cde4077](cde4077)) * **changelog:** remove changes related to unreleased commits ([#68](#68)) ([364a355](364a355)) * remove useless test and update changelog ([#70](#70)) ([4ea3fdc](4ea3fdc)) * update test for a button and changelog ([#69](#69)) ([4eb675e](4eb675e))
github-actions bot
pushed a commit
that referenced
this pull request
Sep 25, 2023
## [1.0.1](v1.0.0...v1.0.1) (2023-09-25) ### Bug Fixes * Add fullWidth button prop ([#72](#72)) ([f0e76e8](f0e76e8)) * add test case for negative button as it is not just modifier anymore but it is own button type ([#63](#63)) ([c9d4950](c9d4950)) * **buttons:** set secondary variant styles by default ([#67](#67)) ([cde4077](cde4077)) * **changelog:** remove changes related to unreleased commits ([#68](#68)) ([364a355](364a355)) * make tabs accessible for using keyboard keys again ([#71](#71)) ([14129cc](14129cc)) * remove useless test and update changelog ([#70](#70)) ([4ea3fdc](4ea3fdc)) * update test for a button and changelog ([#69](#69)) ([4eb675e](4eb675e)) * use new button classes and improve conditions ([#62](#62)) ([1c9fa6c](1c9fa6c))
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
There was a bug with
v1.0.1-next.1tag pointing at a wrong commit hash, which resulted in the last two releases to NPM fail (link to failed job). This bug was caused by an attempt to update a semantic-release-bot commit and force-pushing it tonextbranch. The commit hash changed and so semantic release had no reference to the commit tagged byv1.0.1-next.1.The solution was to force-update the referenced commit hash in
v1.0.1-next.1tag.Now that the two last commits can be released by merging this PR, the related changelog messages can be removed. They will be generated by semantic release upon suffessful release of v1.0.1-next.2 🤞