Repository navigation
Complete tinytrace v1 correctness, privacy, and release hardening - #1
Merged
Merged
Conversation
…istry verification
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.
Fix shutdown ownership across persistent, one-shot, and prepended host handlers before and after initialization. Delegation remains stable during asynchronous host cleanup until reinitialization.
Adds default field/key redaction, generic fatal diagnostics, validated immutable hook output, correctly budgeted Retry-After handling (including dates and overflowing integers), and separate event fingerprint namespaces.
Verified current head 8b74d0d:
CI: https://github.com/garvj65/tinytrace/actions/runs/39464453402
Prepares version 1.0.0 and an exact-commit gated npm release with provenance and registry-integrity verification. Publishing is attempted only after trusted merged-main CI succeeds; npm account/scope authentication may still require setup. Privacy matching and in-memory delivery have explicit documented limits; passing checks are not a guarantee that every possible defect is absent.