feat(versioning): Add Unity3D

[ViMaSter]

Changes

Adds versioning for updating the runtime of a project using the Unity game engine.

Context

See #27219, implements part of #27295.

Documentation (please check one with an [x])

• I have updated the documentation, or
• No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

• Code inspection only, or
• Newly added/modified unit tests, or
• No unit tests but ran on a real repository, or
• Both unit tests + ran on a real repository
  • Ran tests locally and via PR on my fork: Adds unity3d versioning ViMaSter/renovate#3

[secustor]

Please split out manager, versioning and datasource in separate PRs.

[ViMaSter]

@secustor The manager depends on the datasource, which in turn depends on the versioning, so I've replaced this PR to only contain the versioning for now. Also rebased it onto the latest main and updated the Pull Request description.

For context: The manager requires the datasource to be present for the supportedDatasources export and the datasource uses the new versioning as defaultVersioning.

Would it be best to create the next PR only after this one is integrated?
As a possible alternative, I can already create the remaining two PRs, but base them on one another instead of main.
Let me know what would be the best approach here! :)

[viceice]

@secustor The manager depends on the datasource, which in turn depends on the versioning, so I've replaced this PR to only contain the versioning for now. Also rebased it onto the latest main and updated the Pull Request description.

For context: The manager requires the datasource to be present for the supportedDatasources export and the datasource uses the new versioning as defaultVersioning.

Would it be best to create the next PR only after this one is integrated?
As a possible alternative, I can already create the remaining two PRs, but base them on one another instead of main.
Let me know what would be the best approach here! :)

you can cascade them. GitHub should automatically change target branch when parent PR gets merged.

[ViMaSter]

Thanks for the review and approval!

you can cascade them. GitHub should automatically change target branch when parent PR gets merged.

Hmm, I'm not sure that works. I've created two PRs that are based on each other ViMaSter#6 (datasource into this branch) and ViMaSter#7 (manager into the datasource branch), but as the branches I'm working on are part of a fork, the Pull Requests aren't part of this repository.

I could create them pointing at renovate:main, but at that point the manager PR would be identical to my initial submission.

[rarkins]

Needs test passing before we can merge this one

[ViMaSter]

Thanks for re-queuing the Actions! I'll resolve the missing test coverage, linter errors and rebase it onto main again, once I'm back from work in around 9 hrs from now.

[ViMaSter]

Rebased the branch and resolved issues with coverage, as one of the regexes was redundant.

Builds look good on my fork: https://github.com/ViMaSter/renovate/actions/runs/8021111410?pr=8

[renovate-release]

🎉 This PR is included in version 37.252.0 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)
• 37.252.0

Your semantic-release bot 📦🚀