ci: bump publish-platforms pin to the multipart-JSON fix - #547
Merged
Conversation
The pinned SHA (ca2dcd16, 2026-07-03) predates BentoBoxWorld/.github#13, which moved the CurseForge `metadata` and Hangar `versionUpload` JSON out of inline `-F` values and into files. curl treats `;` in an inline -F value as the start of a `type=`/`filename=` attribute, so a release body containing a semicolon truncates the JSON: the 1.26.3 publish failed with CurseForge "Error in field `metadata`: Invalid JSON" and Hangar "Failed to read request". Earlier releases only passed because their notes happened to contain no semicolons. Pin moved to master HEAD 1f91a0e, which contains the fix. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SAQ3YQkcfRoCZEwa6SPJcp
|
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.
What
Bumps the pinned SHA of the shared
publish-platforms.ymlreusable workflow fromca2dcd16(2026-07-03) to1f91a0e(master HEAD, 2026-07-20).Why
The 1.26.3 publish failed on both CurseForge and Hangar (run):
{"errorCode":1002,"errorMessage":"Error in field \metadata`:\nInvalid JSON."}`{"status":400,"detail":"Failed to read request"}Both are the same root cause. The pinned version passes the multipart JSON as an inline curl value:
curl reads
;in an inline-Fvalue as the start of atype=/filename=attribute, so the JSON is truncated at the first semicolon in the changelog. The 1.26.3 release notes contain one (...(ChunkBlock #11); that panel was derived...); earlier releases only succeeded because their notes happened to contain none.BentoBoxWorld/.github#13 fixed this on 2026-07-20 by writing the JSON to a file and using curl's
<fileform (-F "metadata=<cf_meta.json;type=application/json"), but this repo was still pinned to the commit before it.Follow-up
Every other BentoBoxWorld repo except AcidIsland is still pinned to the stale
ca2dcd16and will hit this the moment a release body contains a semicolon.Modrinth was unaffected — it does not go through this workflow.
🤖 Generated with Claude Code
https://claude.ai/code/session_01SAQ3YQkcfRoCZEwa6SPJcp