Closed AntoinePrv closed 10 months ago
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 (recipe
) and found it was in an excellent condition.
@conda-forge-admin, please rerender
Hi! This is the friendly automated conda-forge-webservice.
I tried to rerender for you, but it looks like there was nothing to do.
This message was generated by GitHub actions workflow run https://github.com/conda-forge/libsolv-feedstock/actions/runs/5940219711.
Could you please share a bit more about what the build number bump was addressing?
We uploaded broken (or at least breaking) builds as noticed in #73. We mark them as broken in https://github.com/conda-forge/admin-requests/pull/800. Then reverted the changes in this feedstock (so that the next changes are not based on the broken code), and here I am uploading new builds as a complementary measure to marking the builds as broken (if the builds take some time to be marked as broken, these builds should have higher precedence over the broken ones). This should not be necessary but my goal was to get back to a clean state ASAP.
Checklist
0
(if the version changed)conda-smithy
(Use the phrase code>@<space/conda-forge-admin, please rerender in a comment in this PR for automated rerendering)Follow up to #73, upload new builds with higher precedence.