v3.0.0-beta.1 — Thin wrapper around game-ci/cli (pre-release)

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

What's changing

This is a preview of the next major version of unity-activate — a rewrite as a genuine thin wrapper around game-ci/cli. Instead of doing license activation itself, the action now downloads the game-ci CLI binary and shells out to its activate command. Unity credentials are read by the CLI from its own process environment (inherited from the spawn), never passed as CLI args, to avoid leaking secrets through process listings or command-echo logging.

Full details: unity-activate#111.

How to try it

Pin cliVersion explicitly to the release this was verified against, so your test run is deterministic even if a newer cli release ships mid-beta:

- uses: game-ci/unity-activate@v3.0.0-beta.1
  env:
    UNITY_EMAIL: ${{ secrets.UNITY_EMAIL }}
    UNITY_PASSWORD: ${{ secrets.UNITY_PASSWORD }}
  with:
    cliVersion: v0.1.8

Everything else (inputs, secrets) stays the same as @v2 — swap the version tag and see if activation still works as expected.

Known gaps in this pre-release

• unityVersion is kept for backward compatibility but is now unused — the CLI detects the Unity version itself from the checked-out project's ProjectSettings/ProjectVersion.txt.
• Not yet live-tested against a real runner or real CLI release artifacts by us beyond local vitest/ncc build checks — this release exists specifically so that can happen before the actual v3 cut.

What we need from testers

• Try your actual activation step against @v3.0.0-beta.1 (a separate branch/workflow file is safest).
• Report back in the tracking issue — did activation succeed, personal or professional license, anything that felt different from @v2.

Thank you for helping make sure this lands solid. 🙏