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

[v2023.09.01] remove implicit max_pin=x from run-export #85

Merged
merged 1 commit into from
Oct 13, 2024

Conversation

h-vetinari
Copy link
Member

Backport #84 so that feedstocks which haven't rerendered yet after conda-forge/conda-forge-pinning-feedstock@22886ad don't end up causing more wrong run-exports that need to be patched (c.f. conda-forge/conda-forge-repodata-patches-feedstock#879).

@h-vetinari h-vetinari added the automerge Merge the PR when CI passes label Oct 13, 2024
@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.

@github-actions github-actions bot merged commit e9a926b into conda-forge:v2023.09.01 Oct 13, 2024
8 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!

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