chore: sync main to dev - #10056
Merged
Merged
chore: sync main to dev#10056
Conversation
release: 2026-09-09
Contributor
Author
🚦 CI StatusBuild skipped — no changes detected under Waiting for lint to start… Waiting for tests to start… Bare-metal benchmarks run automatically after each successful build; results land in this section. Add the On demand — comment |
Merged
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
1 participant
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.
👑 An automated PR
Important
This PR must be merged by an admin, as a merge commit ("Merge pull request", bypassing the linear-history rule) — never squash or rebase it.
Squashing rewrites the synced commits, which makes
mainanddevdiverge silently and surfaces later as release-merge conflicts.The
enforce-approvalsrequired check stays red until an admin approves this PR.This manual procedure has kept
mainanddevin sync for years when followed — see #9566 for the mechanical enforcement plan (ruleset + bot bypass) we will apply if a squash slips through again.