Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Backport fix to unpin conda-build again #79

Closed
h-vetinari opened this issue Feb 21, 2024 · 2 comments
Closed

Backport fix to unpin conda-build again #79

h-vetinari opened this issue Feb 21, 2024 · 2 comments

Comments

@h-vetinari
Copy link
Member

The current meta.yaml does not have an upper bound for conda-build, but one was recently imposed by conda-forge/conda-forge-repodata-patches-feedstock#657 due to mamba-org/boa#392.

This keeps us from using the newest conda-build in CI (and thus some relevant fixes; c.f. conda-forge/conda-smithy#1844). Looking at mamba-org/boa#393, it shouldn't be a big issue to backport this PR?

CC @jaimergp @mbargull
@h-vetinari h-vetinari mentioned this issue Feb 21, 2024
Merged
5 tasks
@jakirkham jakirkham mentioned this issue Feb 21, 2024
Closed
5 tasks
This was referenced Feb 23, 2024
Merged
Closed
@mbargull
Copy link
Member

We'd also want mamba-org/boa#395 (or similar changes) for upcoming/future conda/conda-build version compat.

@h-vetinari h-vetinari mentioned this issue Mar 21, 2024
Merged
3 tasks
@jaimergp
Copy link
Member

0.17.0 is coming (mamba-org/boa#396) so I think we won't need this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jaimergp @mbargull @h-vetinari