Skip to content

docs: A checklist for all the things to check on a new minecraft version #465

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

Closed
wants to merge 5 commits into from

Conversation

edayot
Copy link
Contributor

@edayot edayot commented Mar 1, 2025

A little bit of documentation on what to do when a new minecraft version comes out.
I didn't want the test I'd written to be blocking, as it might not pass very often, for example on old PRs. But I'm open to your opinions on the matter, as well as on the location in the guide documentation.

@SpyC0der77
Copy link

datapack.wiki has a breaking changes list. Might be looking into. I am working on a different repo that accomplishes something similar to this repo, and I found that if you want to fix breaking changes, just give ChatGPT the changes from datapack.wiki and give it the code base, summarized by repomix.com and ask it to "Find instances in this repository where the code it generates will break because of these breaking changes. Only include instances where the code it generates will break independent of the users input." It will soon give you a list of instances you can check and fix. If you don't understand, I can just do it when a new version comes out :)

@edayot
Copy link
Contributor Author

edayot commented Jun 17, 2025

I will redo this at some point

@edayot edayot closed this Jun 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants