Closed ju-manns closed 11 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.
I do have some suggestions for making it better though...
For recipe:
Documentation on acceptable licenses can be found here.
Hi! This is the friendly automated conda-forge-linting service.
I was trying to look for recipes to lint for you, but it appears we have a merge conflict. Please try to merge or rebase with the base branch to resolve this conflict.
Please ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug.
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.
I do have some suggestions for making it better though...
For recipe:
Documentation on acceptable licenses can be found here.
@ju-manns if 8.1.0
is released, the artifact on scipopt.org must not change. You should instead bump bugfix 8.1.1
> 8.1.2
> ... We won't be running out of numbers anytime soon ;)
@AntoinePrv Ah, I was not aware. Does that mean that all past artifacts on scipopt.org should remain available? In that case, we would have to do a SCIP 8.1.1 release too (no big overhead there).
I mean the Conda packages will be fine, but in general (and this is relevant also outside of Conda), once you make a release it's frozen for eternity.
One reason is reproducibility. Even if you think it's the same, it may change something for someone somewhere. The other is security/integrity. Hash mismatch are meant to indicate a corrupt download, either fraudulent or broken.
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)