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

Update pin for libode #6676

Conversation

regro-cf-autotick-bot
Copy link
Contributor

This PR has been triggered in an effort to update the pin for libode. The current pinned version is 0.16.2, the latest available version is 0.16.5 and the max pin pattern is x.x.x. This migration will impact 7 feedstocks.

Checklist:

  • The new version is a stable supported pin.
  • I checked that the ABI changed from 0.16.2 to 0.16.5.

**Please note that if you close this PR we presume that the new pin has been rejected.

@conda-forge-admin please ping libode
This PR was generated by https://github.com/regro/cf-scripts/actions/runs/11757598925 - please use this URL for debugging.

@regro-cf-autotick-bot regro-cf-autotick-bot requested a review from a team as a code owner November 9, 2024 16:49
@conda-forge-webservices
Copy link
Contributor

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

I was asked to ping @conda-forge/libode and so here I am doing that.

@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.

@traversaro
Copy link
Contributor

I was asked to ping @conda-forge/libode and so here I am doing that.

The migration seems good to go!

@h-vetinari h-vetinari merged commit d3d22c4 into conda-forge:main Nov 10, 2024
3 checks passed
@regro-cf-autotick-bot regro-cf-autotick-bot deleted the new_pin-libode-0.16.5-0-_h7b3fad branch November 10, 2024 01:05
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.

4 participants