Version Packages#162
Merged
Merged
Conversation
Member
|
@coderabbitai review |
✅ Action performedReview finished.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (19)
🔗 Linked repositories identifiedCodeRabbit considers these linked repositories for cross-repo context during reviews:
💤 Files with no reviewable changes (13)
📝 WalkthroughWalkthroughFinalizes the 🚥 Pre-merge checks | ✅ 3 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (3 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@pydantic/logfire-browser@0.17.0
Minor Changes
autoInstrumentations, provider-owned Web Vitals spans, explicit page URL attributes, and clarified session replay correlation semantics.metrics.metricUrlandrum.webVitals.metricsto emit LCP, INP, CLS, FCP, and TTFB metrics in parallel with existing Web Vital spans.rum.webVitals, emitting LCP, INP, CLS, FCP, and TTFB as Logfire spans with attribution fields.sessionReplayintegration with SDK-owned session correlation, replay state span attributes, optional peer loading, telemetry endpoint suppression, and live replay mode reporting.Patch Changes
6760a47: Preserve callable browser cleanup while exposing generation-scoped session replay lifecycle controls, keep Web Vitals spans available when metrics startup fails, and mark Web Vitals point events as Logfire logs.
Remove unused pre-stable replay transport, recorder snapshot, and navigation
loadsurfaces that were never used or emitted.6760a47: Make same-page browser reconfiguration deterministic and ownership-safe. Cached tracers and manual Logfire APIs now follow each sequential provider generation, inactive intervals are non-recording, overlapping configurations fail explicitly, and cleanup preserves application-owned OpenTelemetry globals.
6760a47: Document safer development proxy examples and clarify that the Python telemetry helpers do not forward browser replay uploads.
6760a47: Use privacy-safe browser defaults: omit query strings and fragments from page
attributes and replay URLs, mask rendered replay text, and disable replay
console capture unless explicitly enabled.
6760a47: Harden browser RUM and session replay for their stable releases with transactional replay lifecycle handling, per-session sampling, retry-safe optional instrumentation, and finalized page URL and error-promotion contracts.
Updated dependencies [6760a47]
Updated dependencies [6760a47]
Updated dependencies [6760a47]
Updated dependencies [6760a47]
Updated dependencies [6760a47]
Updated dependencies [6760a47]
@pydantic/logfire-session-replay@0.1.0
Minor Changes
sessionReplayintegration with SDK-owned session correlation, replay state span attributes, optional peer loading, telemetry endpoint suppression, and live replay mode reporting.Patch Changes
6760a47: Preserve callable browser cleanup while exposing generation-scoped session replay lifecycle controls, keep Web Vitals spans available when metrics startup fails, and mark Web Vitals point events as Logfire logs.
Remove unused pre-stable replay transport, recorder snapshot, and navigation
loadsurfaces that were never used or emitted.6760a47: Use privacy-safe browser defaults: omit query strings and fragments from page
attributes and replay URLs, mask rendered replay text, and disable replay
console capture unless explicitly enabled.
6760a47: Make replay delivery more reliable with bounded concurrent lifecycle uploads,
CSP-safe compression fallback,
Retry-Afterhandling, and UTF-8 byte accounting.6760a47: Harden browser RUM and session replay for their stable releases with transactional replay lifecycle handling, per-session sampling, retry-safe optional instrumentation, and finalized page URL and error-promotion contracts.
@pydantic/nextjs-client-side-instrumentation@0.1.16
Patch Changes