ci: publish releases to CurseForge alongside Modrinth - #24
Merged
Conversation
Add CurseForge upload steps mirroring the Modrinth ones. They run only when the CURSEFORGE_ID repo variable is set and are all continue-on-error, so CurseForge never blocks the gated Modrinth release. Requires a CURSEFORGE_TOKEN secret.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds CurseForge uploads to the release workflow, mirroring the 7 Modrinth steps (5 stable + 2 MC26 beta), via the same
mc-publishaction.Safe by design:
continue-on-error: true— a CurseForge hiccup can never fail the gated Modrinth release or the tag/GitHub-release steps.CURSEFORGE_IDrepo variable is set, so nothing changes until CurseForge is configured.To enable (Settings → Secrets and variables → Actions):
CURSEFORGE_ID= the CurseForge project's numeric IDCURSEFORGE_TOKEN= a CurseForge API tokenCurseForge then publishes on the next version release. Merging this now is a no-op release-wise (tag
v1.6.0exists → release job short-circuits).