Release 1.5.4

[JohanMabille]

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.

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

[JohanMabille]

@conda-forge-admin, please rerender

[mbargull]

Given the comments from, e.g., mamba-org/mamba#3033 (comment) and conda-forge/conda-forge-repodata-patches-feedstock#608 (comment), it would make sense to have this as

Suggested change

	- conda >=23.11,<24
	- conda >=23.11,<23.12

. Whenever there is a new conda release for which mamba is still compatible with, we can just relax the constraint and issue a new build here.

[mbargull]

Thanks everyone for the quick handling of this!

[JohanMabille]

Not sure to understand, the build fails with : "Error: package/version missing in: '/home/conda/recipe_root/meta.yaml'", but we never had a package/version in this recipes (since it's a split package, we have a version per output). Were new tests added recently?

[mbargull]

Not sure to understand, the build fails with : "Error: package/version missing in: '/home/conda/recipe_root/meta.yaml'", but we never had a package/version in this recipes (since it's a split package, we have a version per output). Were new tests added recently?

conda-forge/conda-build-feedstock#210 has also been merge today -- probably some kind of change(/regression?!?) in conda-build=3.28.

[SylvainCorlay]

conda-forge/conda-build-feedstock#210 has also been merge today -- probably some kind of change(/regression?!?) in conda-build=3.28.

Indeed, should we mark conda-build 3.28 as broken?

[mattwthompson]

Here's something in the diff that might be relevant (haven't dug deeply myself): conda/conda-build@3.27.0...3.28.0#diff-cf6e2d8905542a0e7aac26cae115f65b848dd3498b72a43051f0a8900de2c13cL684-R686

If that link doesn't open to the right lines: Files Changed -> search "package/version"

Change from blame: https://github.com/conda/conda-build/pull/5055/files

[JohanMabille]

Thanks, let's add a version to the split package then, but there's a chance that this new version breaks a lot of recipes.

[mbargull]

conda-forge/conda-build-feedstock#210 has also been merge today -- probably some kind of change(/regression?!?) in conda-build=3.28.

Indeed, should we mark conda-build 3.28 as broken?

Could you open a PR at https://github.com/conda-forge/admin-requests ?

[SylvainCorlay]

Maybe add a comment that it is a workaround?

[JohanMabille]

conda-forge/conda-build-feedstock#210 has also been merge today -- probably some kind of change(/regression?!?) in conda-build=3.28.

Indeed, should we mark conda-build 3.28 as broken?

Could you open a PR at https://github.com/conda-forge/admin-requests ?

See conda-forge/admin-requests#890

[jezdez]

Just a note that we've seen this and we're coordinating a response

[mbargull]

CI went through. Good to merge?

[mbargull]

CI went through. Good to merge?

Sorry for being pushy on this.
Thing is just that any user of mamba which does a conda update --all/mamba update --all will break mamba as of now, see mamba-org/mamba#3033 (comment) .

[JohanMabille]

CI went through. Good to merge?

Sorry for being pushy on this. Thing is just that any user of mamba which does a conda update --all/mamba update --all will break mamba as of now, see mamba-org/mamba#3033 (comment) .

No worries, sorry for the delay, I've been preempted

[mbargull]

Thanks, appreciated! Bonne soirée!