Update pin for qt6_main

[regro-cf-autotick-bot]

This PR has been triggered in an effort to update the pin for qt6_main. The current pinned version is 6.9, the latest available version is 6.10 and the max pin pattern is x.x. This migration will impact 33 feedstocks.

Checklist:

• The new version is a stable supported pin.
• I checked that the ABI changed from 6.9 to 6.10.

**Please note that if you close this PR we presume that the new pin has been rejected.

@conda-forge-admin please ping qt-main

_{This PR was generated by https://github.com/regro/cf-scripts/actions/runs/19451621444 - please use this URL for debugging.}

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-webservice.

I was asked to ping @conda-forge/qt-main and so here I am doing that.

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

[hmaarrfk]

https://code.qt.io/cgit/qt/qtreleasenotes.git/about/qt/6.10.0/release-note.md

They claim that they have maintained ABI compatibility

from 6.9 to 6.10.

So given that we patched 6.8 for compatibility with 6.9 we should be compatible all the way back to 6.8

[h-vetinari]

The bigger issue here seems to me that qt 6.10 requires (in terms of upstream docs & current package metadata) __osx >=13.0, which is much more recent than anything else I'm aware of (certainly something so widespread), see here.

In other words, if we want to move the qt pinning to 6.10, we'd have to somehow zip it with c_stdlib_version on osx, or stay stuck on 6.9 until we've dropped support for __osx <13 (which would be a loooong time at current velocity).

It's worth noting though that qt6-main 6.9 already requires __osx >=11.0, which is strictly speaking also not compatible with our pinning, and somehow that seems to work...

Marking this as a draft for now (both because we don't need the migrator, and should discuss the __osx impact).

[hmaarrfk]

Do you want to start a maintenance branch for at 6.8?

the osx packages that need older support can pin to it.

We can also state compatibility all the way up to 6.10 for packages built with that new version of 6.8