chore: release v0.2.0 - #17
Merged
Merged
Conversation
Bump the package version and correct the changelog so the released sections describe what each version actually shipped. `[0.1.0]` had drifted: it carried the `setUser` / `getUser` / `clearUser` entry, which landed after the v0.1.0 tag. That section is published, so it is restored to the text the tag carries and the entry moves to `[0.2.0]`. `[0.2.0]` was missing five changes that shipped on it, two of them silent data loss that a reader of these notes needs to know about: - Native crash reports never reached the intake, on any released version: the crash date came from the dump file's `fs.Stats` and was fractional, and the intake decodes `date` as an int64. - Main-process `resource` events had the same defect, from dividing a nanosecond span start by 1e6. The other three are `addError`'s `startTime` rounding, the SDK-owned bridge preload with its anonymous-id and session-id accessors, and the `usr.anonymous_id` stamp on main-process events.
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.
Bumps the package version to 0.2.0 and corrects
CHANGELOG.mdso each released section describes what that version actually shipped.Changelog corrections
[0.1.0]is a published section, and it had drifted — it carried thesetUser/getUser/clearUserentry, which landed after the v0.1.0 tag. It is restored here to the exact text the tag carries (verified byte-identical), and the entry moves to[0.2.0].[0.2.0]was missing five changes that ship on it. Two are silent data loss that a reader of these notes needs to know about:fs.Stats, which carries sub-millisecond precision, and the intake decodesdateas an int64 — the whole event fails. The intake answers202before it decodes, so nothing surfaced on the SDK side.resourceevents had the same defect, from dividing a nanosecond dd-trace span start by 1e6.The other three:
addError'sstartTimerounding, the SDK-owned bridge preload with itsgetAnonymousId()/getSessionId()accessors, and theusr.anonymous_idstamp on main-process events.Verification
Run locally on the release commit — the same gates the publish workflow runs:
yarn typecheck— cleanyarn build— clean;0.2.0is stamped intodist/via__SDK_VERSION__, anddist/preload.jsis presentyarn test:unit— 37 files, 689 tests, all passingyarn format:check— clean across all tracked filesAlso confirmed the workflow's release-notes
awkextracts the[0.2.0]section and stops at[0.1.0].After merge
Tag the merge commit
v0.2.0and run the Publish workflow from that tag, per the flow documented at the top of.github/workflows/publish.yml.