fix(ci): publish locale refreshes through exact merge#103625
Merged
Conversation
openclaw-barnacle
Bot
added
scripts
Contributor
Author
|
Land-ready proof for exact head
Known proof gaps: none. |
Contributor
Author
|
Merged via squash.
|
This was referenced Jul 10, 2026
github-actions Bot
pushed a commit
to Desicool/openclaw
that referenced
this pull request
Jul 11, 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
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.
Closes #103570
What Problem This Solves
Fixes an issue where Control UI and Native App locale refreshes would pass generation and validation, then fail when their finalizers pushed generated commits directly to protected
main. The exact-merge ruleset rejected every attempt, discarded the generated updates with the runner, and left release CI red.Why This Change Was Made
Both finalizers now call one shared generated-PR action. Each workflow resolves the current default-branch SHA once, pins every locale worker and finalizer to it, and refreshes its complete canonical locale inventory. The action mints the existing primary or fallback OpenClaw GitHub App token with only contents and pull-request write permission, conservatively replays generated blobs onto the latest
mainwithout overwriting concurrent changes, publishes through an exact force lease, and verifies the same-repository PR reaches that exact head.Generated merges trigger one full reconciliation run; a no-change result produces no new commit. Remote operations are noninteractive and bounded. Ruleset failures, unexpected branch movement, divergent ancestry, and unresolved PR state fail closed. Stale no-diff PRs are made unmergeable with a leased branch update rather than an unsafe close mutation. The default workflow token and every checkout remain read-only.
The workflow does not bypass repository rules or auto-merge generated changes.
User Impact
Maintainers can review and land generated locale updates through the normal exact-merge path. Locale refresh workflows no longer spend minutes retrying an impossible direct push, and translation updates are not lost with the runner.
Evidence
pnpm test test/scripts/ci-workflow-guards.test.ts test/scripts/test-projects.test.ts: 227/227 passed, including conservative replay, overlap deferral, and stale PR-head convergence fixtures (AWS Crabboxrun_0b406ff1686f).pnpm check:workflows: actionlint, zizmor, and composite interpolation checks passed (AWS Crabboxrun_082ec4b28b3a).pnpm check:changed -- <changed files>: passed on the final rebased tree (AWS Crabboxrun_7b43088bb505).git diff --check: passed.AI-assisted: yes, implemented with Codex and reviewed against the repository's workflow and landing contracts. No agent transcript is included.