Bump 24.3.0

[jezdez]

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.

closes gh-233

[conda-forge-webservices]

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

I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.

Here's what I've got...

For recipe:

• Package version 24.3.0. doesn't match conda spec

[jezdez]

@conda-forge-admin, please rerender

[conda-forge-webservices]

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) and found it was in an excellent condition.

[dbast]

seems to require conda-build 24.3.0 to not break conda-smithy.

[jezdez]

seems to require conda-build 24.3.0 to not break conda-smithy.

That'll be released soon-ish, I think we can wait.

[isuruf]

Let's wait until conda-forge/conda-forge.github.io#2117 is fixed so that our infrastructure does not break

[h-vetinari]

Let's wait until conda-forge/conda-forge.github.io#2117 is fixed so that our infrastructure does not break

That makes no sense to me, the relevant conda-build PR isn't even merged yet (aside from the fact that it's only a deprecation, not the removal).

[h-vetinari]

seems to require conda-build 24.3.0 to not break conda-smithy.

It's conda 24.3 breaking conda-build 24.1, see conda/conda-build#5221.

We should update the existing run_constraint here to conda-build >=24.3, to avoid breaking existing conda-build artefacts (c.f. conda-forge/conda-forge-repodata-patches-feedstock#685).

[h-vetinari]

Note that the run-constraint turns the upgrade into a bit of a chicken-and-egg problem, in the sense that while the CI here is green, we didn't actually run the conda-smithy downstream test:

WARNING: Skipping downstream test for spec conda-smithy; was unsatisfiable.  Error was Unsatisfiable dependencies for platform linux-64: {'package conda-smithy-3.21.2-pyhd8ed1ab_0 requires conda-build >=3.18.3,<3.28.2.0a0, but none of the providers can be installed'}

AFAIU we'd have to merge conda-forge/conda-build-feedstock#221 first, then the constraints for smithy could be resolved.

Or we merge without that downstream test, but I think it'd be safer to do conda-build first.

[mbargull]

@conda-forge-admin, please restart ci

[mbargull]

@conda-forge-admin, please rerender

[github-actions]

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

I tried to rerender for you, but it looks like there was nothing to do.

This message was generated by GitHub actions workflow run https://github.com/conda-forge/conda-feedstock/actions/runs/8419380517.

[mbargull]

@conda-forge-admin, please restart ci
(conda-forge::conda-build=24.3.0[subdir=win-64] hadn't been sync'ed to CDN for the previous run.)

conda-forge/conda-forge.github.io#2117 is all done

[mbargull]

LGTM!
Shall we merge this in today or is there anything else we'd like to check beforehand?

[mbargull]

Shall we merge this in today or is there anything else we'd like to check beforehand?

No takers and it's the new day => merging this in!

Thanks to @jezdez for the changes and to everyone for looking out for current/future compatibility efforts!

[mbargull]

(This defaulted to "Rebase and merge" for me which did not create a merge commit; no idea why that was the default 🤷.)