Skip to content

[TT-16890] fix: sync critical commits from release-5.12.1#8069

Merged
buger merged 1 commit intorelease-5.12from
sync/5.12-missing-commits
Apr 17, 2026
Merged

[TT-16890] fix: sync critical commits from release-5.12.1#8069
buger merged 1 commit intorelease-5.12from
sync/5.12-missing-commits

Conversation

@buger
Copy link
Copy Markdown
Member

@buger buger commented Apr 17, 2026

Summary

Sync critical commits that are on release-5.12.1 but missing from release-5.12.

The branches diverged on Feb 16 with no merge flow between them. This PR brings release-5.12 up to parity with release-5.12.1 for critical fixes.

Missing commits synced

Test plan

  • Unit Tests & Linting passes
  • go build ./gateway/... passes

🤖 Generated with Claude Code

Cherry-pick critical fixes that were on release-5.12.1 but missing
from release-5.12:
- #8029: [TT-16890] validate request middleware regression fix
- #8067: backport #7974 validate middleware collapsed path fix
- #7862: dependency updates in go.mod and go.sum

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@buger buger added the deps-reviewed Dependency changes reviewed and approved for CI execution label Apr 17, 2026
@buger buger merged commit 00ce563 into release-5.12 Apr 17, 2026
32 of 45 checks passed
@buger buger deleted the sync/5.12-missing-commits branch April 17, 2026 06:24
@probelabs probelabs bot changed the title fix: sync critical commits from release-5.12.1 [TT-16890] fix: sync critical commits from release-5.12.1 Apr 17, 2026
@github-actions
Copy link
Copy Markdown
Contributor

🚨 Jira Linter Failed

Commit: fddd0e4
Failed at: 2026-04-17 16:48:54 UTC

The Jira linter failed to validate your PR. Please check the error details below:

🔍 Click to view error details
failed to validate branch and PR title rules: branch name 'sync/5.12-missing-commits' must contain a valid Jira ticket ID (e.g., ABC-123)

Next Steps

  • Ensure your branch name contains a valid Jira ticket ID (e.g., ABC-123)
  • Verify your PR title matches the branch's Jira ticket ID
  • Check that the Jira ticket exists and is accessible

This comment will be automatically deleted once the linter passes.

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

Labels

deps-reviewed Dependency changes reviewed and approved for CI execution

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant