v5.0.0-beta.1 — Delegates to game-ci/cli's extracted logic (pre-release)

This is a pre-release for testers only. It does not affect @v4, @v3, or any other tag you're already using.

What's changing

This is a preview of the next major version of unity-test-runner. Unlike unity-builder/unity-activate's v6/v3 pre-releases (which shell out to the game-ci CLI binary directly), this action's own local build/test/report logic has been extracted into game-ci/cli's in-repo plugins/unity/ workspace and this action now re-exports it as a pinned git dependency. game-ci/cli doesn't have a Docker-based test command yet (game-ci/cli#71 tracks that prerequisite), so this isn't the same "shell out to the CLI binary" architecture as the other two - it's the interim step.

No new inputs, nothing to configure differently - this is meant to be a drop-in replacement.

Full details: unity-test-runner#310.

How to try it

- uses: game-ci/unity-test-runner@v5.0.0-beta.1
  with:
    projectPath: test-project

Everything else (inputs, secrets, artifacts, coverage, GitHub Checks reporting) stays the same as @v4 - swap the version tag and see if your existing workflow still works as expected.

Known context

• Depends on a pinned commit of game-ci/cli's plugins/unity/ workspace (currently up to date with cli's main, including a recent fix for intermittent Windows Docker-launch failures - see unity-test-runner#314).
• The underlying test/build logic itself hasn't changed in behavior, only where it physically lives - this is meant to be a drop-in replacement.

What we need from testers

• Try your actual test workflow against @v5.0.0-beta.1 (a separate branch/workflow file is safest, not a change to your main CI).
• Report back in the tracking issue - what worked, what broke, anything that felt different from @v4, even if it's minor.

Thank you for helping make sure this lands solid. 🙏