Skip to content
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

3.x #19

Merged
merged 9 commits into from
Sep 13, 2024
Merged

3.x #19

merged 9 commits into from
Sep 13, 2024

Conversation

illlustr
Copy link

No description provided.

akien-mga and others added 9 commits September 8, 2024 22:41
At long last, after 2 years of development, Godot 3.6 is finally out!

Developing it in parallel to the 4.x branch proved to be a challenge,
as eventually I (Rémi) hardly had any time to focus on it.

Thankfully lawnjelly picked up the torch, both on the feature dev side
(most new rendering features are his work) but now also as release
manager for 3.x.

For anyone still using Godot 3.5 for their released or soon-to-be
published titles, upgrading to 3.6 should bring a lot of bug fixes, as
well as a number of useful features and quality of life improvements.
We don't use that info for anything, and it generates unnecessary diffs
every time we bump the minor version (and CI failures if we forget to
sync some files from opt-in modules (mono, text_server_fb).

(cherry picked from commit 81064cc)
Self deleting an object within a call was leading to crashes due to referencing freed memory, due to a raw pointer stored in the debug lock.

Co-authored-by: RandomShaper <pedrojrulez@gmail.com>
[3.x] Fix parsing of `4.` in Expression
[3.x] Fix MSBuild logger exception thrown when processing a warning or an error with no associated file
[3.x] `Object::call()` prevent debug lock accessing dangling pointer
@illlustr illlustr merged commit 39b2d86 into naiiveprojects:3.x Sep 13, 2024
1 check passed
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.

5 participants