Ref: Add warning to session replay

[lucas-zimerman]

📢 Type of change

• Bugfix
• New feature
• Enhancement
• Refactoring

📜 Description

This PR adds warnings for users using session replay that it will be deprecated on the next major version.

💡 Motivation and Context

Session replay doesn't work so we are dropping support for it.

💚 How did you test it?

📝 Checklist

• I added tests to verify changes
• No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled
• I updated the docs if needed.
• I updated the wizard if needed.
• All tests passing
• No breaking changes

🔮 Next steps

Close #1202

[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).

---

Internal Changes 🔧

• Add warning to session replay by lucas-zimerman in #1205

• Update validate-pr workflow by stephanie-anderson in #1198
• Pin GitHub Actions to full-length commit SHAs by joshuarli in #1180

---

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

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

[cursor]

Falsy check skips deprecation warning for zero values

Low Severity

The truthy check on replaysSessionSampleRate and replaysOnErrorSampleRate treats 0 the same as undefined. A user who explicitly sets either option to 0 (a valid sample rate meaning "record none") won't see the deprecation warning, even though they are actively using a deprecated option that will be removed in v4. Comparing against undefined instead of relying on truthiness would correctly detect all explicitly configured values.

 

[lucas-zimerman]

if user sets to 0 then they will never see a replay, there is already a deprecation mark on it. Lets keep the warning only if users are using it.

[antonis]

LGTM