-
-
Notifications
You must be signed in to change notification settings - Fork 16
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
aws-parallelcluster v3.6.0 (take 2) #92
base: main
Are you sure you want to change the base?
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 |
…nda-forge-pinning 2023.10.17.07.56.56
the move to 6.0.1 was done here: aws/aws-parallelcluster#5509 as part of the 3.7 release but was possibly unnecessary. it has been reversed at aws/aws-parallelcluster#5719 after the issue aws/aws-parallelcluster#5714 was described
Hi @nyetsche thanks for the contribution, but we are already at version 3.7.2. We started introducing pcluster 3.x on Conda from version 3.6.1: https://anaconda.org/conda-forge/aws-parallelcluster/files, we can avoid 3.6.0. I'm going to close this patch but please let me know if you have any question/comment or if I missed something. |
Hi @enrico-usai - yes, my organization uses Is there something about my PR that precludes creating a 3.6.0 version, but not making it the default? |
Thanks @nyetsche for the explanation. |
There was an attempt to package 3.6.0 in #82 - hopefully this one passes all the checks.
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)