Qt6 New Release Version Update Order

[hmaarrfk]

Comment:

I feel like the bot has trouble launching updates because we pin so hard on the same versions of software.

jschueller and I have been starting the following updates manually and so I figured it would be good to document them.

• This feedstock (manually update, 2-stages build)
• Quick3D - https://github.com/conda-forge/qt-quick3d-feedstock (manually update, 2-stages build)
• Graphs - https://github.com/conda-forge/qt-graphs-feedstock (depends on quick3d)
• Charts - https://github.com/conda-forge/qt-charts-feedstock
• Multimedia - https://github.com/conda-forge/qt-multimedia-feedstock
• Wayland - https://github.com/conda-forge/qt-wayland-feedstock (manually update, 2-stages build)
• GTKPlatformTheme - https://github.com/conda-forge/qt-gtk-platformtheme-feedstock
• NetworkAuth - https://github.com/conda-forge/qt-networkauth-feedstock
• 3D - https://github.com/conda-forge/qt-3d-feedstock
• DataVis3D - https://github.com/conda-forge/qt-datavis3d-feedstock

There may be other feedstocks to manually migrate

Once all completed, you should check the release notes at their code.qt.io page, for example: https://code.qt.io/cgit/qt/qtreleasenotes.git/about/qt/6.9.0/release-note.md

If they claim ABI compatibility,

• update the repo-data-patch in a similar way to Loosen ABI compatibility for packages built with qt6.8 conda-forge-repodata-patches-feedstock#1012
• Bump the global pinning to the new version of qt.

If they do not claim ABI compatibility, start a migration.

[hmaarrfk]

i wonder if it is related to: conda-forge/dagster-cloud-feedstock#4

[hmaarrfk]

My guess is that the bot is not "updating" the version of abi_migration_branches but rather just keeping them "alive" by rerendering as needed.

We should likely "flip" which is a branch, and which is main in 2025....

[jschueller]

yes, they announce 5.15 will be eol in may 2025