You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 16, 2024. It is now read-only.
Before implementing I just want to check that we can support this way of versioning in both the fabric.mod.json and the forge tomls when declaring dependencies on pingbypass versions with this scheme.
Before this is solved I would also not publish a docker image, as I want to reuse the old 3arthh4ck docker hub repo, which has the old 3arthh4ck versioning. Since 3arthh4ck went up to 1.8, I would also update the version to 2.0.0 for this project, once it is usable.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I would like to to return to the versioning as described by Forge:
https://docs.minecraftforge.net/en/1.14.x/conventions/versioning/
MCVERSION-MAJORMOD.MAJORAPI.MINOR.PATCH
,maybe without the PATCH part, but something that contains the mc version.
Before implementing I just want to check that we can support this way of versioning in both the fabric.mod.json and the forge tomls when declaring dependencies on pingbypass versions with this scheme.
Before this is solved I would also not publish a docker image, as I want to reuse the old 3arthh4ck docker hub repo, which has the old 3arthh4ck versioning. Since 3arthh4ck went up to 1.8, I would also update the version to 2.0.0 for this project, once it is usable.
The text was updated successfully, but these errors were encountered: