The new Qt 6.12 LTS contains many bug fixes and officially supports macOS 26.
See:
Based on #36592.
Qt 6.12 requires macOS 15 SDK or higher.
See https://doc.qt.io/qt-6.12/macos.html.
The minimum supported macOS version stays at 14.0.
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--006a51241073e994b41acfe9ec718e94-->
<!--021abf342d371248e50ceaed478a90ca-->
See the guideline and AI policy for information on the review process. A summary of reviews will appear here.
<!--5faf32d7da4f0f540f40219e4f7537a3-->
and support macOS 26
Our current version already does?
and support macOS 26
Our current version already does?
It works, obviously. However, macOS 26 is not listed in https://doc.qt.io/qt-6.8/macos.html.
Apparently, Qt 6.12 needs CMake >=3.25.
See https://lists.qt-project.org/pipermail/development/2026-May/047097.html.
0 | @@ -0,0 +1,17 @@ 1 | +Keep compatibility with the current libxkbcommon package
Will this work? I assume Qt increased their required version, because they are using some feature / API from the newer version? Would be good if this explained why this is ok to do.
I'm investigating the API changes now.
<!--85328a0da195eb286784d51f73fa0af9-->
🚧 At least one of the CI tasks failed.
<sub>Task macOS-cross to arm64: https://github.com/bitcoin/bitcoin/actions/runs/39653749364/job/119408481873</sub>
<sub>LLM reason (✨ experimental): CI failed while linking bitcoin-qt because Qt’s Cocoa plugin references the undefined macOS symbol __isPlatformVersionAtLeast.</sub>
<details><summary>Hints</summary>
Try to run the tests locally, according to the documentation. However, a CI failure may still happen due to a number of reasons, for example:
Possibly due to a silent merge conflict (the changes in this pull request being incompatible with the current code in the target branch). If so, make sure to rebase on the latest commit of the target branch.
A sanitizer issue, which can only be found by compiling with the sanitizer and running the affected test.
An intermittent issue.
Leave a comment here, if you need help tracking down a confusing failure.
</details>