Automation suggestion

[bruno-garcia]

A GHA workflow that runs on a schedule and checks Unity's release page for new releases: https://unity3d.com/unity/whats-new/

If a release came out, it creates a PR in this repo bumping the version in the yml file:

unity-docker/.github/workflows/ci.yml

Lines 26 to 33 in e7c5083

	unity-version: [2019.4.36f1, 2020.3.29f1, 2021.2.11f1]
	include:
	- unity-version: 2019.4.36f1
	unity-version-changeset: 660c164b2fc5
	- unity-version: 2020.3.29f1
	unity-version-changeset: 2ff179115da0
	- unity-version: 2021.2.11f1
	unity-version-changeset: e50cafbb4399

It would need to make sure it won't open a PR if one exists (regardless of its state (merged, open or closed)

[vaind]

There's very likely an API, assuming Hub doesn't parse the pages. I'll first check that.

[vaind]

I've had a look at this and would suggest the following:

• automatically build for the latest available version in the CI script - implemented by Build the latest available version #2
• periodically run this CI, e.g. twice a day, thus picking up the version when there's a new one
• automatically remove unused versions, except for the latest (to reduce GH repo storage)

[bruno-garcia]

Makes sense. Seems like #2 is missing the scheduling
We need to make sure CI on the unity repo doesn't bump to latest automatically though, because, for example, 2019.4.36f (the latest) is broken, so that would stop all of our CI workflows. Ideally a PR would be opened everyday a new Docker image is created bumping not only the docker image there, but also the versions we used in Windows and macOS (e.g: getsentry/sentry-unity#567)

[vaind]

Makes sense. Seems like #2 is missing the scheduling

Wanted to hear your thoughts first before doing that change. Now that I have, I'll update the CI.

We need to make sure CI on the unity repo doesn't bump to latest automatically though, because, for example, 2019.4.36f (the latest) is broken, so that would stop all of our CI workflows. Ideally a PR would be opened everyday a new Docker image is created bumping not only the docker image there, but also the versions we used in Windows and macOS (e.g: getsentry/sentry-unity#567)

Yep, makes sense. Didn't want to do auto-update-to-latest in sentry-unity, just here