"Publish to Modrinth" (workflow_dispatch, tag + dry_run inputs) takes the
jars the Release workflow attached to a Gitea release and creates one
Modrinth version per jar: version_number <version>+<mc>, that Minecraft
version, fabric loader, Fabric API as a required dependency, the release
notes as the changelog, and alpha/beta/release from the tag. It doesn't
rebuild, skips versions already on Modrinth, and downloads jars through
the public URL (Gitea's reported URLs use its internal ROOT_URL).
Needs a MODRINTH_TOKEN secret with the "Create versions" scope.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
gitea:3000 isn't resolvable from act_runner's job containers, which run
on their own Docker network. With the panorama downscaled in common the
jars are ~45 MB, under the Cloudflare tunnel's 100 MB request limit, so
upload through github.server_url again. Fail with a readable error
before uploading if any jar is 100 MB or more.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
The Cloudflare tunnel in front of git.selimaj.dev rejects the jar
uploads with 413 Payload Too Large. Call the API at http://gitea:3000
instead, look the release up by tag, and add a workflow_dispatch trigger
that builds a given tag and attaches the jars to its existing release.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
The release workflow no longer overrides mod_version from the tag.
Instead it fails early unless the release tag (optionally prefixed with
"v") matches mod_version in gradle.properties, so released jars always
report the same version as the code the version check sees.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
On a published release, build all versions with buildAll using the tag
as the mod version, and upload build/allJars/*.jar to the release.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
selimaj-devandclaude