Open beckermr opened 1 month ago
I think for the conda-forge-feedstock-check solvable I will have a good grip on what needs to be done.
For the second point, ensure that ABI migrations in the bot can go through, I actually don't really know where to start. Do you have additional pointers?
Right so for that, once the solver checks work, we should add a test to the bot repo that does an abi migration and make sure it all runs.
https://github.com/regro/conda-forge-feedstock-check-solvable/pull/58 this is the PR for adding solvability checks with rattler-build.
https://github.com/conda-forge/conda-forge-webservices/pull/685 opened to enable lints on PRs etc.
@beckermr - I think I need some help / guidance in order to understand what's needed for the cf-graph items. How can I ensure that?
Thanks @beckermr for updating the todo items. I can make the build number PR right away (it's a subset of the version bump PR) so we can get that one in straight away! If you let me know how / where to add tests for migrations I can do it tomorrow, too :)
I updated the issue list above with a pointer to the correct test file. We should replicate all of the tests there for yaml migrations to ensure they work on v1 recipes.
Added PR for build number bumps: https://github.com/regro/cf-scripts/pull/3009
Only the tests to go! :)
Ticked off the last one (uploading packages) :)
There are two more on staged-recipes:
@beckermr are you OK if I edit your initial comment to include the additional TODO items?
This issue is to track progress on supporting the v1 recipe format via rattler build.
Minimal Work Items for Uploads:
Next Steps + Bug Reports
superceeds #1612