alRex-U
Publishing pipeline
I've created a build pipeline to validate PRs, I've been thinking that maybe it could be useful for you to have a publish pipeline as well.
The difference between those would be that:
- The trigger would only be manual, as you may want to accumulate changes before closing a new version. You could also trigger it through the creation of tags. which would be useful to register each release you do;
- It would build the mod and publish it for every target you want.
It's also possible to create this having the publishing step in a different pipeline for different targets (curseforge, modrinth, etc), and different modloaders so you can trigger every one you want, or just some that you may have missed or not updated yet.
This would require you to register some secret keys in your repository here:
Settings:
Secrets and variables > Actions > Environment Secrets
I'd be happy to do it for you if you want, although you'd need to test it yourself, as I'd not have permission to do so
So are you willing to use CurseForge upload API to upload files built by Github Actions?
Yes, I'm doing the same work here in the ShoulrderSurfing mod, you can take a look. It's a simple pipeline that will publish the mod to curseforge and/or modrinth when you trigger it manually, or when you create a tag. In ShoulderSurfing case, it was already configured to do it through gradlew. If this is not the case in parcool, we can set it up.
The work there is not done yet, though, some details must be decided about how changelog will be handled, but the whole idea is that you can leave the publishing work to the github cloud, you'll need to prepare the changelog and trigger the event, though. Maybe in the future you can even configure it even further and automatize publishing when a merge is done, if you want