You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
failed in Create Pull Request with Cannot read properties of undefined (reading number).
The runner also reports that the Node 20 actions are being forced onto Node 24. The failure is therefore in PR reconciliation, not translation generation.
Scope
Keep this separate from Beta 3 artifact issue #5876. It affects the scheduled documentation synchronization path and leaves the existing translation PR branch updated even though the workflow is red.
Acceptance criteria
Update or replace the create/update-PR action with a maintained version compatible with the current runner.
Verify the path where chore/sync-translations and its pull request already exist.
Preserve safe branch-update behavior and do not create duplicate PRs.
A scheduled or equivalent test run completes the PR-update step successfully.
No Project 16 membership or release milestone is assigned: this item was discovered during release triage but is not an eligible current-stage Blocker/Required workstream.
Reproduction evidence
Scheduled Sync Translations run 30774299881 failed on 2026-08-03 while updating the existing
chore/sync-translationspull request branch.The translation generation step succeeded.
peter-evans/create-pull-request@v4then:chore/sync-translations,Fetching existing pull request, andCreate Pull RequestwithCannot read properties of undefined (reading number).The runner also reports that the Node 20 actions are being forced onto Node 24. The failure is therefore in PR reconciliation, not translation generation.
Scope
Keep this separate from Beta 3 artifact issue #5876. It affects the scheduled documentation synchronization path and leaves the existing translation PR branch updated even though the workflow is red.
Acceptance criteria
chore/sync-translationsand its pull request already exist.No Project 16 membership or release milestone is assigned: this item was discovered during release triage but is not an eligible current-stage Blocker/Required workstream.