fix(attributes): Apply consistent scrubbing across deprecations

[mjq]

Description

Apply the same scrubbing rules across entire deprecation chains. This keeps the scrubbing behaviour predictable whether or not Relay is doing attribute rewriting. It also make semantic sense - if two attributes have identical semantic meanings, they should also have identical scrubbing rules.

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.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
sentry-conventions	Ready	Preview	Oct 14, 2026 9:00am UTC

[github-actions]

Semver Impact of This PR

🟢 Patch (bug fixes)

📋 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 ✨

• (attributes) Add http.request.duration by loewenheim in #697

Bug Fixes 🐛

• (attributes) Apply consistent scrubbing across deprecations by mjq in #692

Internal Changes 🔧

• (repo) Update CODEOWNERS to include @giortzisg by Lms24 in #708

---

_{🤖 This preview updates automatically when you update the PR.}

[linear-code]

EXP-1275

[elramen]

How come we align on the weaker setting for attributes that can contain user data? Or is the reason text incorrect?

[mjq]

@elramen I'm trying to avoid user-visible changes. We prioritize the latest version of attributes in the product, so effectively, that's the scrubbing rule we're applying - so I took the latest rule and applied it to the older deprecated aliases.

[Lms24]

Good catch, thanks for cleaning this up! The changes from auto to manual look reasonable to me for non-gen_ai attributes. For the gen_ai ones, I'd appreciate a second pair of eyes from agent tracing folks if the policies of the current attributes are intentional, since some of them seem a bit more "risky".

[mjq]

@Lms24 Thanks! Looks like @obostjancic okay'd this on Slack, so I'm going to go ahead. We were already prioritizing the latest version of attributes in Sentry which would have had the weaker scrubbing rules already, so this isn't effectively weakening anything IMO.

[Lms24]

I think this just needs another update since we merged some PRs around the same time. Gonna rebase, then this should auto merge