Automatic version update

[deirn]

• Added scheduled actions that run update tasks once a day and make a PR if it detects changes
  • Fetch a list of supported Minecraft versions from fabric meta
  • Fetch latest library versions from maven central. Technically uses internal VersionNumber API to compare versions but I don't think we need to worry about those as FLK doesn't really need loom/gradle update anyway
• Changed the release action to run the readme gen after the build success and commit it to master

Test PR: https://github.com/deirn/flk-automation-test/pull/4

[jakobkmar]

What I worry about here is that often the newest versions are not the ones that match, meaning only a human can update them to the correct combination at some points in time.

[modmuss50]

Yeah, my main worry is that this seems like it will open PRs for pre-release versions.

[deirn]

Yeah, my main worry is that this seems like it will open PRs for pre-release versions.

Shouldn't happen if kotlin dev stick to somewhat semver (dash suffix for pre-releases), it only compare versions without it.

What I worry about here is that often the newest versions are not the ones that match, meaning only a human can update them to the correct combination at some points in time.

Did that ever happened before? What FLK includes are official libraries, kotlin dev should already know if one of their libs would be incompatible, no? If we are that paranoid, we can leave the generated PR open for a few days and let the bot update the pr branch, it should only open one pr at a time.