[Bug]: Incorrect Unity version when activating license

[NicolasChicunque]

What happened?

unityVersion value is not passing from ci-cd-pipeline to avalin/unity-ci-cd/.github/workflows/step-1-test.yml@v1 or to game-ci/unity-activate@v2, then the license is not activated.

Steps to reproduce and Workflow details

List the steps:

1. I already set up .github/config/defaults.json with unityVersion "6000.3.2f1"
2. When run the ci-cd-dispatcher workflow everything is ok and pass to ci-cd-pipeline.
3. When ci-cd-pipeline is doing the run_tests step and needs (call) avalin/unity-ci-cd/.github/workflows/step-1-test.yml@v1 , it is not sending the unityVersion: ${{ needs.unpack_inputs.outputs.unityVersion }} in the line 91.
4. Then the Activate Unity Licence steps running game-ci/unity-activate@v2 shows unityVersion: 2019.2.11f1

Expected behavior

unityVersion value pass from ci-cd-pipeline to avalin/unity-ci-cd/.github/workflows/step-1-test.yml@v1

Logs or screenshots

___ ___

Note

When I isolate the game-ci/unity-activate@v2.0.0 the step runs successfully:

Environment

• Unity version: 6000.3.2f1 (docker allowed)
• OS: Windows 11
• GitHub Runner (ubuntu-latest, macos-latest)

Thank you :)

[Avalin]

Hey Nicolas!
I attempted fixing this, and you're right that Unity Activation in the pipeline ignores the unity version entirely, I haven't had problems with the version mismatch personally, but I also haven't used the Unity 6 version much yet. It isn't as easy a fix as I had hoped.

I can see someone has reported an issue with 6000 version patterning to GameCI which I seem to stumble into as well here:

(Link to run: https://github.com/Avalin/Unity-CI-CD/actions/runs/22232231104/job/64314744246)

And when I run activation with other UnityVersions, I risk there not being an available image for the specific version I am using:

(Link to run: https://github.com/Avalin/Unity-CI-CD/actions/runs/22232707494/job/64316420031)
I am unsure if GameCI allows for a fallback Unity version in these cases, if they don't, I think we'd need to make it a separate feature to avoid pipelines failing with unsupported versions.

Here's my current code:
https://github.com/Avalin/Unity-CI-CD/blob/activate-license-on-correct-unity-version/.github/workflows/unity-license-uploader.yml

I also attempted using the matrix solution exactly as written in your working screenshot (which I'd rather avoid if possible) but it also gave errors.
Do you maybe have an idea where to go from here?

[NicolasChicunque]

Hi Avalin,

I confirmed that we don't need a unityVersion to use with unity-activate@v2:

We just need this:

Maybe the builder or other actions need it, but not for activation.

I suggest removing the unityVersion from unity-activate@v2 in ci-cd-pipeline.yml

---

I apologize for the confusion.

Nico

[NicolasChicunque]

On other news. I fixed the regex problem: game-ci/unity-activate#109 hehehe.

[Avalin]

No worries! I'll close the issue, but feel free to open a new one if you experience any problems!