-
-
Notifications
You must be signed in to change notification settings - Fork 23
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
Disable automerge #104
base: main
Are you sure you want to change the base?
Disable automerge #104
Conversation
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 ( |
@conda-forge-admin please rerender |
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 ( I do have some suggestions for making it better though... For recipe/meta.yaml:
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12118772517. Examine the logs at this URL for more detail. |
…onda-forge-pinning 2024.12.02.10.31.23
I refreshed this PR as all the changes in pybind/pybind11#4953 and pybind/pybind11#5439 will require to revise the pybind11-abi package. However, after I opened it I noticed that the The re-rendering does not change the content of the package, so I think we can avoid bump the build number. |
@conda-forge/pybind11 the PR is ready for review/discussion. |
Given all the problems occurring in new pybind11 releases related to abi changes (see #95) perhaps it could make sense to disable automerge here so that new versions can at least be checked before merging?
Checklist
0
(if the version changed)conda-smithy
(Use the phrase@conda-forge-admin, please rerender
in a comment in this PR for automated rerendering)