Add "Upgrading from Godot 4.1 to Godot 4.2" page #8488
Merged
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
raulsntos
added
enhancement
content:new page
Calinou
reviewed
Nov 17, 2023
Co-authored-by: Hugo Locurcio <[email protected]>
Calinou
reviewed
Nov 20, 2023
Cerno-b
suggested changes
Nov 20, 2023
Co-authored-by: Hugo Locurcio <[email protected]> Co-authored-by: A Thousand Ships <[email protected]> Co-authored-by: Cerno_b <[email protected]>
raulsntos
force-pushed
the
breaking_changes_4.2
branch
from
2972495 to
011e21c
Compare
skyace65
approved these changes
Nov 21, 2023
mhilbrunner
approved these changes
Nov 21, 2023
Member
|
Thank you! Merged. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 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.
Adds the migration guide for 4.2, just like we did for 4.1 (#7611).
Last time we didn't include GDExtension compatibility because 4.1 completely broke compatibility, we added a warning at the top of the page instead. I'm not sure how we want to handle GDExtension compatibility this time, the @godotengine/gdextension team can suggest changes or make a follow-up PR.
Area maintainers should review the changes listed for their area. Also feel free to suggest any addition that I might have missed or make follow-up PRs.