Automatic Release Script

[Peashooter101]

When PRs are merged into main (or master), generally we are going to release a new version of the software.

We should create a GitHub action that can publish to Modrinth (and/or GitHub).

• If possible, this should track the version so we don't re-release an existing version.
  • Any re-releasing of already released versions should be a manual process.
  • This likely can be done in an actions env variable or just looking up what the current version on Modrinth is.
• There should be a way to skip automatic release.
  • In a similar manner where [skip ci] at the start of a commit message skips ci workflows.
• (Rhythmic) There should be a published or publish branch which controls version releases.
  • Releases will only occur when we pull into the publishing branch rather than from main.
  • This likely will change how we approach version bump checking.
• Release should also update the Modrinth README and the changelog should be pulled from the commits in the merge request from main > publish.