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

Close out migration for proxsuite071 #7095

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

olivier-roussel
Copy link
Contributor

@olivier-roussel olivier-roussel commented Mar 3, 2025

Following the discussion in #6998.
Proxsuite 0.7.1 migration is now done for a while ( https://conda-forge.org/status/migration/?name=proxsuite071 ) so this PR closes the migration and adds proxsuite 0.7.1 to global pinning.

Checklist

@olivier-roussel olivier-roussel requested a review from a team as a code owner March 3, 2025 16:15
@olivier-roussel olivier-roussel changed the title Close out migration for proxsuite 071 Close out migration for proxsuite071 Mar 3, 2025
@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:

  • ℹ️ top-level output has some malformed specs:
  • In section test: python >= 3.8 Requirements spec fields should always be space-separated to avoid known issues in conda-build. For example, instead of name =version=build, use name version build`.

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/13635372685. 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