Skip to content

chore: sync main (v10.3.0) into beta - #1426

Merged
github-actions[bot] merged 7 commits into
betafrom
sync/main-v10.3.0-into-beta-37171665601
Oct 4, 2026
Merged

github-actions[bot] merged 7 commits into
betafrom
sync/main-v10.3.0-into-beta-37171665601

Conversation

@github-actions

@github-actions github-actions Bot commented Oct 4, 2026

Copy link
Copy Markdown
Contributor

Automated sync of main back into beta after release v10.3.0, including beta version set to 10.3.1-beta.1.

Scriptwonder and others added 7 commits October 3, 2026 22:04
…0.2.1

release.yml runs from main and calls main's copy of unity-tests.yml against
beta. Main still uses the floating game-ci/unity-test-runner@v4, which moved
to v4.4.0 on 2026-09-09. v4.4.0 defaults githubToken to github.token, so the
runner calls the Checks API with a read-only token, gets a 403, and fails every
leg. That broke beta from 2026-09-20 until #1410; on main it would fail the
10.2.1 release gate the same way.

release.yml also runs beta's tools/update_versions.py after it merges beta,
and that script now updates Server/uv.lock (#1376). Main's release.yml does
not stage uv.lock, so the release commit would leave it at the old version and
`uv sync --locked` would fail afterwards.

Copy these files from beta (5fb7703, df0cba7 and #1410), byte for byte:
- .github/workflows/unity-tests.yml: pinned runner SHA + cliVersion,
  githubToken "", separate domain-reload/regular result gates and artifacts
- tools/check_unity_test_results.py: the result gate script that workflow calls
- .github/workflows/release.yml: stage Server/uv.lock with the version bump

The files are identical to beta, so the release's "merge beta into main" step
merges them without conflict.
ci: bring beta's Unity test gate and uv.lock staging to main before 10.2.1
@github-actions
github-actions Bot merged commit d6981d8 into beta Oct 4, 2026
@github-actions
github-actions Bot deleted the sync/main-v10.3.0-into-beta-37171665601 branch October 4, 2026 02:52
@coderabbitai

coderabbitai Bot commented Oct 4, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration
  • Configuration used: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: ebd5c0d5-ff46-48ae-bf01-902639d99065

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
  • Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants