3.15.0rc1

[mgorny]

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

Ref #895

[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.

I do have some suggestions for making it better though...

For recipe/meta.yaml:

• ℹ️ The recipe is not parsable by parser conda-souschef (grayskull). This parser is not currently used by conda-forge, but may be in the future. We are collecting information to see which recipes are compatible with grayskull.
• ℹ️ The recipe is not parsable by parser conda-recipe-manager. The recipe can only be automatically migrated to the new v1 format if it is parseable by conda-recipe-manager.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/31878276007. Examine the logs at this URL for more detail.}

[mgorny]

I'm trying to fix #895 now (mgorny#1 is my WIP), but feel free to merge it as-is (given it's not a regression), and I'll follow up.

[mgorny]

Okay, included the proposed fix for build-details.json. I don't love it, but it seems to be the simplest and most reliable solution until the problem is addressed upstream.

[lucascolley]

thanks, the patch for build-details cross-comp LGTM

[mgorny]

@isuruf, done and confirmed build-details.json looks valid.