Repository navigation
chore: release 2.1.1 - #6
Merged
Merged
Conversation
2.1.0 was tagged and released on GitHub, but its npm publish failed on an expired token, so it never reached npm. Cut 2.1.1 with the same code so the release goes out through trusted publishing. Release-As: 2.1.1
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
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.
Empty commit with a
Release-As: 2.1.1footer so release-please opens a 2.1.1 release PR.v2.1.0 was tagged and released on GitHub, but its npm publish failed on an expired token (run), so npm is still on 2.0.0. 2.1.1 ships the same code through trusted publishing (#5).
Merge with a merge commit or rebase, not squash, so the
Release-Asfooter lands onmainintact.