Repository navigation
Conversation
Enable the release branch test trigger and repair the inert recovery provenance fixture exposed by that run. No production app code changes.
This was referenced Oct 7, 2026
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
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.
Purpose
Bring the existing release line back into the shared sprint integration branch.
release/2.6.3descends fromrelease/2.6.2, so this single PR carries the already committed 2.5.15–2.6.3 release baseline, including R2, without replaying it in separate PRs.Scope
sprint; no new source changes are authored here.devandmainuntouched; normal promotion can follow review of the integrated release line.Verification and review
sprintis an ancestor ofrelease/2.6.3at PR creation; the comparison is a straight 12-commit advance with no sprint-only commits.git diff --check origin/sprint...origin/release/2.6.3passes.This corrects the branch-flow divergence identified during R3. It does not publish an app build or deploy backend changes.