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

Adjust ruamel_yaml version range #177

Merged
merged 1 commit into from
Sep 27, 2022

Conversation

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

Sync with defaults and upstream

@conda-forge-linter
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.

@jaimergp jaimergp mentioned this pull request Sep 27, 2022
5 tasks
@jaimergp
Copy link
Member Author

I am not sure this is needed after all, ruamel_yaml was only published up to 0.15.x on both conda-forge and defaults 🤷

@beckermr
Copy link
Member

Better to have it correct instead of relying on the non-existence of something.

@jakirkham jakirkham merged commit 020986c into conda-forge:main Sep 27, 2022
@jakirkham
Copy link
Member

Thanks Jaime & Matt! 🙏

Should we do a repodata hotfix too?

@beckermr
Copy link
Member

The previous build had a tighter constraint so no need for a hot fix afaik.

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