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

Remove numpy 2 cap #380

Merged
merged 1 commit into from
May 17, 2024
Merged

Remove numpy 2 cap #380

merged 1 commit into from
May 17, 2024

Conversation

dopplershift
Copy link
Member

Checklist

  • Used a personal fork of the feedstock to propose changes
  • Bumped the build number (if the version is unchanged)
  • Reset the build number to 0 (if the version changed)
  • Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
  • Ensured the license file is being packaged.

@conda-forge-webservices
Copy link

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

@dopplershift dopplershift added the automerge Merge the PR when CI passes label May 17, 2024
@jakirkham jakirkham mentioned this pull request May 17, 2024
@@ -53,7 +53,7 @@ outputs:
- cycler >=0.10
- fonttools >=4.22.0
- kiwisolver >=1.3.1
- numpy >=1.21,<2
- numpy >=1.21
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks Ryan! 🙏

@github-actions github-actions bot merged commit de20875 into conda-forge:main May 17, 2024
37 checks passed
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!

@dopplershift dopplershift deleted the numpy2 branch May 17, 2024 20:07
@jakirkham
Copy link
Member

We could also repodata patch the previous package to include this dependency constraint change

@dopplershift dopplershift mentioned this pull request May 17, 2024
5 tasks
@dopplershift
Copy link
Member Author

Since we were overly constrained before, I don't think there's anything to gain on the repodata patch.

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.

2 participants