1.21.8 - #4820
Merged
Merged
Conversation
Collaborator
|
Just noticed that bumping the version field in update prs like this without creating a tag means that the git vs. non-git version numbers differ not only in the extra information they provide but also in the major/minor/patch triple (e.g. I'll just do what I apparently already did for v1.14.0 and put the version tag directly on the merge commit, without an extra commit to bump the version. That means there's still a month of builds using |
Collaborator
|
Released as v1.15.0 |
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
3 participants
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.
Happy Ghast parkourDownload: https://nightly.link/cabaletta/baritone/actions/runs/16396403911/Artifacts.zip
Baritone 1.21.8 is also compatible with MC 1.21.6 and 1.21.7