How exactly does it infer minecraft version and mod version? #59
-
|
Fabric's tutorial https://fabricmc.net/wiki/tutorial:publishing_mods_using_github_actions uses hardcoded version which I don't like. The README says that the mod version and game version can be inferred from the release tag. How exactly is it inferred? Should I use |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
In my personal opinion, I wouldn't rely on this resolution strategy, as it serves as a last resort solution, implemented for cases when no other information is available for the action to extract. Since you are a mod developer, I assume that you are looking to publish a mod (either Fabric, Forge, or Quilt). In this case, you don't need to worry at all, because mc-publish will obtain the game version directly from the "depends": {
"minecraft": "1.18.x"
},If, for some reason, you still want to use tags as a primary indicator of the Minecraft version in use, I would personally recommend adopting a Sodium-like naming convention, such as Regarding the mod version, the release tag typically corresponds to the new version of your product, whatever it may be. As such, it will be used without any conversions performed on it (i.e., a |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for clarification |
Beta Was this translation helpful? Give feedback.
In my personal opinion, I wouldn't rely on this resolution strategy, as it serves as a last resort solution, implemented for cases when no other information is available for the action to extract.
Since you are a mod developer, I assume that you are looking to publish a mod (either Fabric, Forge, or Quilt). In this case, you don't need to worry at all, because mc-publish will obtain the game version directly from the
minecraftentry in the dependency list of your mod's metadata file (eitherfabric.mod.json,mods.toml, orquilt.mod.json, respectively). For example:If, for some reason, you still want to use tags as a primary indicator of the Minecraf…