search

Kir-Antipov / mc-publish

🚀 Your one-stop GitHub Action for seamless Minecraft project publication across various platforms.
MIT License
216 stars 19 forks source link

[help] Error while parsing JSON: missing field `version_number` #78

Closed Fauli1221 closed 6 months ago

Fauli1221 commented 1 year ago

Publishing on modrinth won't work, and it gives me this error

grafik

Pipeline

workflow

Kir-Antipov commented 1 year ago

So, here's what's happening:

options.version ||= githubContext.payload.release?.tag_name || metadata?.version;

At the moment, mc-publish is incapable of inferring the version of your modpack as it doesn't yet support reading .mrpack files (this feature, however, is slated for inclusion in the upcoming v4.0 release). Additionally, because the action was triggered by a tag creation, there isn't a release available from which to infer the version.

Specifically in your case, I'd categorize it as a bug, because mc-publish could use GITHUB_REF in this scenario to determine the modpack version (i.e., v1.0.9). I'll address this problem shortly.