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

ENH: update package version to 2024.11.1 #277

Conversation

conda-forge-admin
Copy link
Contributor

Hi! This is the friendly automated conda-forge-webservice.

I've started a version update as instructed in #276.

I'm currently searching for new versions and will update this PR shortly if I find one! Thank you for waiting!

Fixes #276

@conda-forge-admin
Copy link
Contributor Author

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 usually follow the syntax in our documentation for specifying the Python version.
    • For the host section of the recipe, you should usually use python {{ python_min }} for the python entry.
    • For the run section of the recipe, you should usually use python >={{ python_min }} for the python entry.
    • For the test.requires section of the recipe, you should usually use python {{ python_min }} for the python entry.
    • If the package requires a newer Python version than the currently supported minimum version on conda-forge, you can override the python_min variable by adding a Jinja2 set statement at the top of your recipe (or using an equivalent context variable for v1 recipes).
  • ℹ️ PyPI default URL is now pypi.org, and not pypi.io. You may want to update the default source url.

….0, conda-smithy 3.44.3, and conda-forge-pinning 2024.11.11.08.59.26
@conda-forge-admin conda-forge-admin changed the title ENH: update package version ENH: update package version to 2024.11.1 Nov 11, 2024
@conda-forge-admin conda-forge-admin marked this pull request as ready for review November 11, 2024 16:09
@fjetter fjetter added the automerge Merge the PR when CI passes label Nov 11, 2024
@conda-forge-admin
Copy link
Contributor Author

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

  • linter: passed
  • azure: failed

Thus the PR was not passing and not merged.

@fjetter
Copy link
Member

fjetter commented Nov 11, 2024

@conda-forge-admin, please restart ci

@fjetter
Copy link
Member

fjetter commented Nov 11, 2024

@conda-forge-admin, please restart ci

@conda-forge-curator conda-forge-curator bot removed the automerge Merge the PR when CI passes label Nov 11, 2024
@conda-forge-admin
Copy link
Contributor Author

Hi! This is the friendly conda-forge automerge bot!

Commits were made to this PR after the automerge label was added. For security reasons, I have disabled automerge by removing the automerge label. Please add the automerge label again (or ask a maintainer to do so) if you'd like to enable automerge again!

@fjetter fjetter added the automerge Merge the PR when CI passes label Nov 11, 2024
@jrbourbeau
Copy link
Member

Closing in favor of #278

@jrbourbeau jrbourbeau closed this Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automerge Merge the PR when CI passes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

@conda-forge-admin, please update version
3 participants