chore: Update CHANGELOG for 0.12.2 #427
Merged
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
This comment was marked as duplicate.
This comment was marked as duplicate.
Sorry, something went wrong.
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.
While trying to resolve the incident around our release registry being out of sync we noticed that the last release of
@sentry/[email protected]was made after@sentry/[email protected]was already released. This "incorrectly" redirected NPM'slatestpointer to0.11.5instead of0.12.1. The simplest way to fix this is to release a new 0.12.x version so this PR updates the changelog for it.#skip-changelog
(Note: Alternatively, merging any open PR that updates the changelog would also do. Happy to close this if we can make a somewhat meaningful release)