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.

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

conda-smithy 3.44.1 #321

Closed
wants to merge 2 commits into from
Closed

conda-smithy 3.44.1 #321

wants to merge 2 commits into from

Conversation

beckermr
Copy link
Member

@beckermr beckermr commented Nov 7, 2024

Merge only after success.

This pull request was auto-generated by rever

@beckermr beckermr requested a review from a team as a code owner November 7, 2024 12:51
@conda-forge-admin
Copy link
Contributor

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:

  • noarch: python recipes should almost always follow the syntax in our documentation. For the host section of the recipe, you should almost always use python {{ python_min }}.* for the python entry. You may need to override the python_min variable if the package requires a newer Python version than the currently supported minimum version on conda-forge.
  • noarch: python recipes should almost always follow the syntax in our documentation. For the run section of the recipe, you should almost always use python >={{ python_min }} for the python entry. You may need to override the python_min variable if the package requires a newer Python version than the currently supported minimum version on conda-forge.
  • noarch: python recipes should almost always follow the syntax in our documentation. For the test.requires section of the recipe, you should almost always use python ={{ python_min }} for the python entry. You may need to override the python_min variable if the package requires a newer Python version than the currently supported minimum version on conda-forge.

@beckermr
Copy link
Member Author

beckermr commented Nov 7, 2024

Well that hint is wrong. 🤦

@beckermr
Copy link
Member Author

beckermr commented Nov 7, 2024

@conda-forge-admin relint

@beckermr
Copy link
Member Author

beckermr commented Nov 7, 2024

We'll release the next minor bump due to a very silly bug on my part.

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