8000 numpy v2.3.0 by h-vetinari · Pull Request #357 · conda-forge/numpy-feedstock · GitHub
[go: up one dir, main page]

Skip to content

numpy v2.3.0 #357

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

Merged
merged 7 commits into from
Jun 9, 2025
Merged

numpy v2.3.0 #357

merged 7 commits into from
Jun 9, 2025

Conversation

h-vetinari
Copy link
Member

No description provided.

@conda-forge-admin
Copy link
Contributor
conda-forge-admin commented May 26, 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-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/15523397112. Examine the logs at this URL for more detail.

@h-vetinari
Copy link
Member Author

@conda-forge-admin, please rerender

@conda-forge-admin
Copy link
Contributor

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

I tried to rerender for you but ran into some issues. Please check the output logs of the GitHub Actions workflow below for more details. You can also ping conda-forge/core (using the @ notation) for further assistance or you can try rerendering locally.

The following suggestions might help debug any issues:

  • Is the recipe/{meta.yaml,recipe.yaml} file valid?
  • If there is a recipe/conda-build-config.yaml file in the feedstock make sure that it is compatible with the current global pinnnings.
  • Is the fork used for this PR on an organization or user GitHub account? Automated rerendering via the webservices admin bot only works for user GitHub accounts.

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

@seisman seisman mentioned this pull request Jun 8, 2025
3 tasks
Co-authored-by: Mark Harfouche <mark.harfouche@gmail.com>
@h-vetinari
Copy link
Member Author

@conda-forge-admin, please rerender

@h-vetinari h-vetinari changed the title numpy v2.3.0rc1 numpy v2.3.0 Jun 8, 2025
@h-vetinari h-vetinari added the automerge Merge the PR when CI passes label Jun 8, 2025
@conda-forge-admin conda-forge-admin merged commit 0f57dbe into conda-forge:main Jun 9, 2025
27 checks passed
@conda-forge-admin
Copy link
Contributor

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

I considered the following status checks when analyzing this PR:

  • linter: passed
  • azure: passed

Thus the PR was passing and merged! Have a great day!

@h-vetinari h-vetinari deleted the rc branch June 9, 2025 01:48
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.

4 participants
0