Add missing breaking change PRs without label to 0.10 -> 0.11 migration guide #696
Conversation
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
Selene-Amanita
changed the title
cart
approved these changes
Jul 10, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Following #655.
Some PRs didn't have the C-Breaking-Changes label, but had a migration guide in the PR description, those were not added to the Migration Guide.
I found them semi-manually using this: https://discord.com/channels/691052431525675048/692572690833473578/1127412213037150269 , the list is here: https://discord.com/channels/691052431525675048/692572690833473578/1127550222126563399
This PR has a lot of copy/paste, even though I changed a few things, so there might be some errors.
I tried to keep the loose sorting by section order.
bevyengine/bevy#7778 is still missing a migration guide.
bevyengine/bevy#6846 could maybe explain how to get around this (?)