Closed jameslamb closed 3 months ago
Perhaps a Python version upper bound somewhere, combined with an upgrade to our containers? The original package seems like it's a noarch package, though.
:tada: This PR is included in version 1.15.0 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
I saw conda builds in CI on #106 failing like this:
Looks to me like this is due to the following set of circumstances:
build
This fixes that by switching the dependency in the recipe from
build
topython-build
.Notes for Reviewers
I'm really not sure why this is just breaking now... the latest release of
build
at https://anaconda.org/conda-forge/build/files is a noarch package without any constraints that appear to conflict with other things we're installing here.python-build
is what we want either way, since it's being actively updated, but would be good to understand why this just broke now.I checked across the
rapidsai
org and don't see any other cases where we were relying on the oldbuild
package: https://github.com/search?q=org%3Arapidsai+%22-+build%22+language%3AYAML+path%3Ameta.yaml&type=code