v1.5.x revert to latest v1.5.x and rebuild py312 #186
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 3 commits
October 24, 2023 08:29
…nda-forge-pinning 2023.10.20.09.48.02
admirito
requested review from
TomAugspurger,
WillAyd,
datapythonista,
jorisvandenbossche,
jreback,
lithomas1,
MarcoGorelli,
mroeschke,
msarahan,
ocefpaf,
phofl and
simonjayhawkins
as code owners
|
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 ( |
3 tasks
|
The build failed, so I will close the PR. I apologize for the redundant PRs. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Checklist
conda-smithy(Use the phrase@conda-forge-admin, please rerenderin a comment in this PR for automated rerendering)This is the same as PR 185, but it first reverts all the changes since 66ac579 (the latest v1.5.x) and then applies the commits, so it can be merged without conflict. I apologize for sending redundant PRs, but this PR is an experiment to see if the build system can build using the old files. If it does, I still believe the best approach is to hard reset the target branch to 66ac579, merge the previous PR, and close this one. However, an alternative is to merge this one as well. If the build fails, we can close both PRs. Once again, I apologize for the redundant PRs.