* ci: Fix Spring Boot matrix version updates

Match the TOML version catalog format when overriding Spring Boot versions in matrix jobs. Preserve whitespace around the assignment and replace the quoted version value so the CI jobs actually test the requested matrix version.

Co-Authored-By: Claude <[email protected]>

* ci: Limit Spring Boot matrix to supported versions

The matrix jobs now actually update the version catalog. Remove Spring Boot versions that the current sample setup cannot build with the repository's Spring GraphQL integrations and Gradle version.

Co-Authored-By: Claude <[email protected]>

* ci(spring): Restore Spring Boot matrix coverage

Expand the Spring Boot 2 and 3 CI matrices to cover supported minor versions. Exclude GraphQL from Spring Boot 2 versions before 2.7 because the starter is unavailable there.

Keep the Spring Boot 3 Gradle plugin pinned to a Gradle-compatible version while importing the tested Spring Boot BOM in samples, so the matrix exercises the intended runtime dependencies.

Co-Authored-By: Claude <[email protected]>

* fix(spring): Avoid deprecated Reactor scheduler in sample

Remove the explicit elastic scheduler from the Spring Boot WebFlux sample. Mono.delay already schedules the delayed work, and using Schedulers.elastic triggers deprecation warnings that fail CI under -Werror.

Co-Authored-By: Claude <[email protected]>

* fix(spring): Exclude Kafka from old Boot 2 matrix

Spring Kafka sample support depends on newer Spring Boot 2 dependency management. Exclude Kafka sources, profile startup, and system tests when the matrix runs Boot 2 versions before 2.7.

Keep the system test classpath aligned with the SDK test helpers by importing the OkHttp and Jackson BOMs after the tested Spring Boot BOMs.

Co-Authored-By: Claude <[email protected]>

* fix(spring): Support older Reactor WebFlux APIs

Spring Boot 2.1 and 2.2 use Reactor versions without Mono.doFirst or Schedulers.onScheduleHook. Avoid those calls in the Boot 2 WebFlux integration so old matrix jobs can start and serve requests.

Co-Authored-By: Claude <[email protected]>

* ci(spring): Skip OTel no-agent sample on old Boot 2

Spring Boot 2.1 and 2.2 cannot parse newer OpenTelemetry auto-configuration classes during startup. Keep the matrix coverage for supported samples and skip the no-agent OTel sample for those versions.

Co-Authored-By: Claude <[email protected]>

* ci(spring): Drop old Boot 2 matrix versions

Remove Spring Boot 2.1 and 2.2 from the matrix instead of carrying WebFlux compatibility changes for their older Reactor and Spring APIs.

Restore the WebFlux filter implementation now that those versions are no longer tested.

Co-Authored-By: Claude <[email protected]>

* fix(spring): Restore WebFlux schedule hook registration

Revert the compatibility guard for Reactor versions that are no longer covered by the Spring Boot matrix.

Co-Authored-By: Claude <[email protected]>

* fix(spring): Support older Spring GraphQL options API

Use the erased Consumer signature in the batch loader registry wrapper so the code compiles with both Spring GraphQL 1.2/1.3 and 1.4.

Let the Spring Boot 3 Gradle plugin follow the tested matrix version instead of pinning it separately.

Co-Authored-By: Claude <[email protected]>

* build: Remove redundant test source set config

Gradle already includes src/test/java in the test source set by default. Remove explicit duplicate source set configuration from the Spring modules and samples touched by this PR.

Co-Authored-By: Claude <[email protected]>

* style: Import Kotlin JVM target in Gradle scripts

Use the JvmTarget import in Spring Gradle scripts touched by this PR instead of repeating the fully qualified class name.

Co-Authored-By: Claude <[email protected]>

* ci: Fail when Spring Boot version update misses

Use a replacement command that exits non-zero when the expected Spring Boot version entry is not found. This prevents matrix jobs from silently running against the wrong dependency version.

Co-Authored-By: Claude <[email protected]>

---------

Co-authored-by: Claude <[email protected]>

* fix(skill): Detect stacked PR context from branch

Update the create-java-pr skill to infer standalone vs stacked PR mode\nfrom git branch and existing PR relationships.\n\nWhen running on main/master, default to standalone PR mode and only\nenter stack mode when explicitly requested by the user.\n\nCo-Authored-By: Claude <[email protected]>

* fix(create-java-pr): Detect collection branches with downstream PRs

Check for downstream PRs even when the current branch already has a PR targeting main/master.

This prevents collection branches in a stacked PR flow from being misclassified as standalone PR context.

Co-Authored-By: Claude <[email protected]>

* fix(create-java-pr): Map stack base detection to defined PR type

When downstream PRs are found for a branch, classify the result as an existing stack flow instead of an undefined "stack base context".

Clarify that the next PR in an existing stack can target either the previous stack PR branch or the collection branch, so all detection outcomes map to actionable PR types.

Co-Authored-By: Claude <[email protected]>

* fix(skills): Add missing standalone PR fallback for fresh feature branches

The decision tree in create-java-pr Step 0 had a gap: when a non-main
branch has no existing PR and no downstream PRs target it, no outcome
was specified. This is the most common case (fresh feature branch).

Add explicit fallback to standalone PR context, matching the behavior
of the parallel branch where a PR exists with base main and no
downstream PRs.

Co-Authored-By: Claude <[email protected]>

---------

Co-authored-by: Claude <[email protected]>

* chore(ci): Update gradle/actions from v5.0.2 to v6.1.0

Remove stale workaround comments for gradle/actions#21 (now closed).

Co-Authored-By: Claude Opus 4.6 <[email protected]>

* Restore workaround comments

Co-Authored-By: Claude Opus 4.6 <[email protected]>

---------

Co-authored-by: Claude Opus 4.6 <[email protected]>

* fix(replay): Populate trace_ids in replay events for trace search

When a transaction is captured while replay is recording, the trace ID
is now registered with the replay controller and included in the next
replay segment. This enables searching for replays by trace ID in the
Sentry UI.

Fixes #5346

Slack thread: https://sentry.slack.com/archives/CP4UUUF1S/p1779889727948439?thread_ts=1777385469.860819&cid=CP4UUUF1S

https://claude.ai/code/session_012wjHQtsEPzcrxSMCufxrDY

* docs: Add changelog entry for trace_ids fix

https://claude.ai/code/session_012wjHQtsEPzcrxSMCufxrDY

* Format code

* api dump

---------

Co-authored-by: Claude <[email protected]>
Co-authored-by: Sentry Github Bot <[email protected]>

* fix(android): Keep replay capturing during animations

Skip only the first unstable PixelCopy capture, then continue emitting frames while the screen keeps invalidating. This prevents animated screens from freezing Session Replay visuals while preserving the existing debounce for one-off redraws.

Fixes GH-5404

Co-Authored-By: Codex <[email protected]>

* test(android): Add replay animation sample screens

Add separate Android sample screens for Lottie, Compose canvas, and classic View animations so replay capture behavior can be tested manually.

Keep the sample app on the Canvas replay screenshot strategy while exercising these animations.

Refs GH-5404

Co-Authored-By: Codex <[email protected]>

* changelog

* fix(android): Make replay animation sample colors API-safe

Use ContextCompat.getColor in ReplayAnimationsActivity so release lint passes with the sample app minSdk.

Refs GH-5489

Co-Authored-By: Codex <[email protected]>

* docs(android): Explain unstable replay captures

Document why PixelCopyStrategy caps skipped unstable captures so continuous animations keep producing replay frames.

Refs GH-5489

Co-Authored-By: Codex <[email protected]>

---------

Co-authored-by: Codex <[email protected]>