-
-
Notifications
You must be signed in to change notification settings - Fork 501
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
feat: use GHA for service feedstocks and copy in alt arch .txt files #6328
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 rerender |
…nda-forge-pinning 2024.08.23.13.31.00
Are we still able to re-render here or does that not work with these changes? |
We can rerender locally. Happy to revert ofc. This feedstock doesn't need rerendering all that much so I assumed it'd be ok. |
Probably the better thing to do is for us to figure out how to use GHA as CI and enable bot-based re-rendering since we may need to move more things to GHA in the future (not less). That's a separate discussion though |
Yeah I have a plan for that but it involves some level of refactoring the rendering code for security hardening. |
Look forward to reading more details on your plan 🙂 |
I think this PR broke CI on the main branch /cc @hmaarrfk |
i feel like a few people have been working to resolve this. I'll take a step back. |
I think this is the heroku server. |
Yeah this job ran fine: https://github.com/conda-forge/conda-forge-pinning-feedstock/actions/runs/10536529046 |
I guess the symptom is that this package is no longer getting published: fails |
Ahhhh sorry. I forgot to reset the token and add to gha. |
Thanks for the quick fix! |
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)