Skip to content

ci: fix Modrinth publish jar path - #179

Merged
tastybento merged 1 commit into
developfrom
fix/modrinth-publish-path
Nov 17, 2026
Merged

tastybento merged 1 commit into
developfrom
fix/modrinth-publish-path

Conversation

@tastybento

Copy link
Copy Markdown
Member

The 2.10.1 Modrinth publish failed (run) with ENOENT on /home/runner/work/.../target/MagicCobblestoneGenerator-2.10.1.jar, even though Maven built that exact file.

cloudnode-pro/modrinth-publish is a Docker action; the workspace is mounted at /github/workspace, so the absolute ${{ github.workspace }} path doesn't exist inside the container. Switched to a relative target/... path (matching Level/BentoBox).

Also adds workflow_dispatch with a tag input (checks out that tag) so 2.10.1 can be re-published once this merges.

🤖 Generated with Claude Code

The cloudnode-pro/modrinth-publish action runs in a Docker container with the
workspace mounted at /github/workspace, so the absolute ${{ github.workspace }}
path to the jar did not exist inside it and the 2.10.1 upload failed with
ENOENT. Use a relative path, as the other addons do.

Also add a workflow_dispatch trigger with a tag input (checking out that tag)
so a failed release can be re-published to Modrinth.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@tastybento
tastybento merged commit b725508 into develop Nov 17, 2026
2 checks passed
@tastybento
tastybento deleted the fix/modrinth-publish-path branch November 17, 2026 06:59
@sonarqubecloud

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant