-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump to 0.15.10 #13
Bump to 0.15.10 #13
Conversation
And did you actually test this properly, or just assume that because you were able to join that it was production-ready? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This does not help the project at all. It is much more convenient to change the version number ourselves directly than merging a pull request, and we are not bumping the version number for some reasons. Please show, or at least, declare that you have confirmed there are indeed no otherwise protocol changes in this protocol bump.
This protocol bump has to do sth with capes/skin handling. Not breaking the current code in any way, we do not (yet) read/write/send cape data. |
This does not break any code in any way as 0.15.10 only added skins |
that you know about. Protocol changes are not documented in the changelogs. |
@robske110 please prove or confirm that this protocol dump only involves skins/capes information. |
I will fully test this very soon when i do ill get back to you |
Tested. Production ready. Up to you to merge |
The CONTRIBUTING.md will be updated soon to disallow this kind of pull requests which contribute as little as updating minor values that we know that we have to change (unlike typos, which we aren't aware of) but have not done so yet. |
No description provided.