Skip to content

Conversation

@h-vetinari
Copy link
Member

@h-vetinari h-vetinari commented Aug 31, 2025

This was first merged in #93, then reverted in #96, reapplied a couple months later in #95 (while being more conservative with unsetting values that might still be needed), and then reverted again pretty much immediately in #99. Xref #94

Given this history here, I think it would make sense to publish these builds to a separate label first and test them on feedstocks that previously were affected. Happy to do this on a separate branch, if desired.

@conda-forge-admin
Copy link
Contributor

conda-forge-admin commented Aug 31, 2025

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

I do have some suggestions for making it better though...

For recipe/meta.yaml:

  • ℹ️ The recipe is not parsable by parser conda-souschef (grayskull). This parser is not currently used by conda-forge, but may be in the future. We are collecting information to see which recipes are compatible with grayskull.
  • ℹ️ The recipe is not parsable by parser conda-recipe-manager. The recipe can only be automatically migrated to the new v1 format if it is parseable by conda-recipe-manager.

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/20689223793. Examine the logs at this URL for more detail.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants