proper releases about modpack HOT 6 CLOSED

This should probably block #26 (curseforge presence)

from modpack.

To clarify my understanding: does this mean we'll create (git term-of-art) annotated tags, or does this mean we'll make commits that have specific keyphrases in them which the build system will look for?

My general preference, absent other input, is for a system that uses tags for releases, for ease of finding those points again in the future, so I'd like to make sure my assumptions are aligned with yours.

from modpack.

avakas handles the creation of tags and keys off of them for generating proper version bumps. so each "release" artifact would have an associated tag.

from modpack.

• introduce auto bump bits (can crib from avakas)
• update dev server on all commits to mainline
• upload to curseforge on tagged commits to mainline - no build / prebuild date version bits tho
• upload all mainline builds to curseforge with build/prebuild bits as needed
• introduce branch protection (reviewers optional, tests passing not)

from modpack.

all this is done just needs docs updated. decided to not update on every mainline build.

from modpack.

#68 adds the last few docs i guess 🌳

from modpack.