We have released Qt 6.5.3 today. As a patch release, Qt 6.5.3 does not introduce any new features but contains more than 500 bug fixes, security updates, and other improvements to the top of the Qt 6.5.2 release. See more information about the most important changes and bug fixes from Qt 6.5.3 release note.
Get Qt 6.5.3
As earlier, you can add Qt 6.5.3 to the existing online installation by using the maintenance tool or do a clean installation by using the Qt Online Installer, which can be downloaded from the Qt Account Portal (for commercial users) and from the opensource download area (for opensource users).
In addition, Qt 6.5.3 source packages are available in the opensource download area for opensource users. For commercial users, the Qt 6.5.3 offline installers and Qt 6.5.3 source packages are available in the Qt Account Portal.
Provide feedback
For any issues you may find, please submit a detailed bug report to bugreports.qt.io or contact our technical support team in case you have a support plan with your commercial license. You are also welcome to join the discussions in the Qt Project mailing lists and developer forums.
Commenting for this post has ended.
Really looking forward to this. I hope this fixes the PySide6 bug (QTBUG-114115) that has prevented me from using Qt 6.5 in my projects
Thank you, Qt team!
Thank you for this timely release. I was literally sitting at my PC refreshing the "release schedule" page because macOS 14.0 came out the day before and broke Qt completely (qmake cannot run). 6.5.3 fixed this so I can now rebuild my app and give customers a working version for the new macOS. I don't see this change in the release notes, btw, but the important part is that it's there.
Glad you enjoy the 6.5.3 release Alex :) Just to clarify, the issue you are talking about was presumably fixed by https://codereview.qt-project.org/c/qt/qtbase/+/503172, and if so, was an Xcode 15 issue. If you had any other issues building or running your app on macOS 14, please let us know in a bug report, thanks!
Yes, that's the fix I was talking about, and no, I did not notice any other issues. Thanks for your work!