chore: release v0.2.1 - #21
Merged
Merged
Conversation
Ships the native crash fingerprint. Grouping was the defect — every crash of one exception type collapsed into a single issue regardless of where the process faulted — so this is a patch. The playground and release-tooling changes that landed alongside it are not part of the published package (`files` ships only dist, README and licences), so they are deliberately absent from the changelog.
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.
Ships the native crash fingerprint (#20).
Grouping was the defect — every crash of one exception type collapsed into a single issue regardless of where the process faulted — so this is a patch release.
Contents
CHANGELOG.mdalready carries the[0.2.1]section from #20; this PR only movespackage.jsonto0.2.1, which the publish workflow validates the tag against.The other two changes merged alongside it (#18 playground
version, #19 dropping the broken release script) are not in the changelog on purpose:filesships onlydist/,README.mdand the licences, so neither is visible to a consumer of the package.Checks
yarn buildcleanyarn test— 36 files / 691 tests passtsc --noEmitclean[0.2.0]changelog section is byte-identical togit show v0.2.0:CHANGELOG.md, so nothing drifted into an already-released sectionAfter merge
Per the flow documented at the top of
publish.yml: tag the merge commitv0.2.1, then run the Publish workflow from that tag —dry_run=truefirst to validate auth and build, then for real.