Modpack version
All

Describe the bug
Every release tag on the GitHub repo actually points to files one release behind the tag.

For example, tagged release 0.4.14 : https://github.com/NillerMedDild/Enigmatica6/tree/0.4.14/server_files
Look at server-setup-config.yaml
modpackUrl: https://media.forgecdn.net/files/3313/5/Enigmatica6-0.4.13.zip

Similiarly, tagged release 0.4.13, the server-setup-config.yaml has a url for Enigmatica6-0.4.12.zip

If you download the release off of CurseForge you get the proper files.

Go here and download the 0.4.14 server files, and check the server-setup-config.yaml, the modpackUrl field points to the proper 0.4.14 zip file : https://www.curseforge.com/minecraft/modpacks/enigmatica6/files

Logs
<N/A>

Screenshots
<N/A>

Thanks for the report. I'm aware of the issue, and will see if I can resolve it :)

Great to hear =), if you'd like some assistance I'd be glad to help, re-naming tags can be a bear. Although I think you have to have relatively high permissions on the repo to do it, so probably not feasible for some "random" person to fix it heh.

That's nice of you but I think I can manage, I just need to change the ordering of my publish script a bit.

Just to ad a bit of context from my poking around. Looks like each tag is just behind by 1 commit (the changelog commit). It seems you already knew that but figured I'd throw some context up here just for tracking purposes heh.

Update: Updated the issue title to more accurately reflect the issue.

The release tags are actually behind by 1 commit not an entire release (the changelog commit is happening after the release is tagged, which also updates the server-setup-config.yaml file to point to the proper files)