1.16.5

[Mcdostone]

Supported forge versions

Authmod supports 2 versions of forge.

• 1.12.2
• 1.16.5

Each implementation has its own branch.

others thoughts

• It would be nice if you could rename the master branch to main @Chocorean
• The main branch contains the source code for the latest forge version compatible with authmod.

• The main branch should have a update.json file that contains the following information:

  {
  "homepage": "https://github.com/Chocorean/authmod/releases",
  "promos": {
  "1.16.5-recommended": "1.16.5-1.0.0",
  "1.12.2-recommended": "1.12.2-1.0.0"
  }
  }

How to release a new version?

1. git checkout <branch>
2. The git tag must follow this pattern v<version-of-forge>-<version-of-authmod>. For instance v1.16.5-1.0.0 or v1.12.2-1.0.0
3. git tag -a v1.16.5-1.0.0 -m "Release a new version for forge 1.16.5
4. git push --tags

[Chocorean]

Thanks again for the amazing work. Can you add the release instructions into the readme please?

And if I understand correctly, when a new release is ready on a branch, just pushing the correct tag will create the jar for us correct?

Also, I wonder how we are going to maintain changes on common files between each branches, like the readme for instance. I am not very familiar with get-cherry-pick but do you think this is possible if properly executed?

[Mcdostone]

Yes

Yes

Regarding the common files, I think we should consider each branch as an independent project (or a different repo). There's only 1 common file: the README.md. At first, we can synchronize that file across the branches manually. We'll see later if there is a better solution.

[Chocorean]

Ok makes sense, thx