Skip to content

feat(replays): Define replayId as a deprecated attribute#401

Draft
mjq wants to merge 1 commit into
mainfrom
mjq/replayid-alias
Draft

feat(replays): Define replayId as a deprecated attribute#401
mjq wants to merge 1 commit into
mainfrom
mjq/replayid-alias

Conversation

@mjq
Copy link
Copy Markdown
Member

@mjq mjq commented May 21, 2026

Description

SDKs currently send replayId on spans, but we'd like to standardize on sentry.replay_id (already defined and in use for other telemetry types). Marking it as deprecated lets the product transparently query either name and return results for either attribute.

PR Checklist

  • I have run yarn test and verified that the tests pass.
  • I have run yarn generate to generate and format code and docs.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 21, 2026

Semver Impact of This PR

🟡 Minor (new features)

📋 Changelog Preview

This is how your changes will appear in the changelog.
Entries from this PR are highlighted with a left border (blockquote style).


New Features ✨

  • (replays) Define replayId as a deprecated attribute by mjq in #401

🤖 This preview updates automatically when you update the PR.

SDKs currently send `replayId` on spans, but we'd like to standardize on
`sentry.replay_id` (already defined and in use for other telemetry types).
Marking it as deprecated lets the product transparently query either name and
return results for either attribute.
@mjq mjq force-pushed the mjq/replayid-alias branch from 5227d29 to ff09ad8 Compare May 21, 2026 20:39
"visibility": "public",
"changelog": [
{
"version": "next"
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: we can link to this PR for reference

Suggested change
"version": "next"
"version": "next"
"prs": [401]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants