Release 24.11.3 2

[hmaarrfk]

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.

[SylvainCorlay]

Ad discussed here, I am fine having a release with mamba 1 including the constructor fixes before having another stab at mamba 2.

[hmaarrfk]

I still see 11.1 in the build. is that ok?

[jjerphan]

I still see 11.1 in the build. is that ok?

For now 11.1 being picked is normal but not OK¹.

We probably should wait for a pathway as being discussed in: conda-forge/admin-requests#1433 (comment).

Footnotes

1. Builds of fmt>=11.1 are still present (not yet marked broken) and the adaptation for projects depending on fmt have not been performed yet. ↩

[SylvainCorlay]

I still see 11.1 in the build. is that ok?

For now 11.1 being picked is normal but not OK1.

We probably should wait for a pathway as being discussed in: conda-forge/admin-requests#1433 (comment).

Footnotes

1. Builds of fmt>=11.1 are still present (not yet marked broken) and the adaptation for projects depending on fmt have not been performed yet. ↩

conda-forge/admin-requests#1433 has been merged. Hopefully, 11.1 should not be picked up anymore.

[jjerphan]

LGTM (this should create the same installers as the one of 24.11.3-1 made with #737 taking builds of fmt<11.1).

[hmaarrfk]

fmt 11.1.4 is ok?

[jjerphan]

No, fmt<11.1 have to be used.

Is one of the installer mentioning fmt>=11.1 builds?

[hmaarrfk]

yes the linux x86_64 build was. Lets try to rebuild again.

[hmaarrfk]

ok fmt 11.0 got pulled in.