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
Corntopia now has a unified version number (starting with version 1.1.1)!
Why you should care
Previously there were 3 different version numbers:
The mod version, which did not include a patch number.
The GitHub tag, which was increased each time an automated build occurred.
And the intended version number, which was added to release notes.
This gets confusing quickly! If you experience a bug or want to try the latest version, not only would you need to know the version number of the mod, but where to get the mod from.
Now releases only have a single version number and the jar with the largest number is the latest version.
How it works
Version numbers are typically split into 3 parts. Major, minor and a patch number.
When a change is made that is incompatible with old items and blocks, the major number is increased.
When a new feature is added or a substantial change is made, the minor number is increased.
The patch number is increased for any other changes, including spelling corrections and bug fixes.
The new version number is calculated from the internal mod number and the latest tag from GitHub. The process is simple, first, the largest value is selected (mod version or tag), then the patch component is increased. Every other system uses this version number:
The jar is built with this version number.
GitHub Actions gets assigned this version number and uses it in file names, titles and descriptions (there is no need to make corrections anymore).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Corntopia now has a unified version number (starting with version 1.1.1)!
Why you should care
Previously there were 3 different version numbers:
This gets confusing quickly! If you experience a bug or want to try the latest version, not only would you need to know the version number of the mod, but where to get the mod from.
Now releases only have a single version number and the jar with the largest number is the latest version.
How it works
Version numbers are typically split into 3 parts. Major, minor and a patch number.
The new version number is calculated from the internal mod number and the latest tag from GitHub. The process is simple, first, the largest value is selected (mod version or tag), then the patch component is increased. Every other system uses this version number:
Beta Was this translation helpful? Give feedback.
All reactions