search

conda-forge / casadi-feedstock

A conda-smithy repository for casadi.
BSD 3-Clause "New" or "Revised" License
8 stars 12 forks source link

autotick bot is not working #102

Open traversaro opened 6 months ago

traversaro commented 6 months ago

Solution to issue cannot be found in the documentation.

Issue

For some reason the autotick bot that automatically updates the recipe is not working. For this reason, we need to manually update the recipe.

Installed packages

.

Environment info

.
traversaro commented 6 months ago

fyi @AlessiaDMiit

traversaro commented 6 months ago

The error from https://conda-forge.org/status/ is :

66.00 attempts - The recipe did not change in the version migration, a URL did not hash, or there is jinja2 syntax the bot cannot handle!

Please check the URLs in your recipe with version '3130' to make sure they exist!

We also found the following errors:

 - could not hash URL template 'https://github.com/casadi/casadi/releases/download/{{ version }}/casadi-source-v{{ version }}.zip'
 -
traversaro commented 6 months ago

I think the logic to find the latest release is finding the https://github.com/casadi/casadi/releases/tag/nightly-issue_3130 (that is not an actual release, just a working tag I guess) and assuming that is the latest releases. To be honest, I do not know how to solve this (it would be cool to have some custom feedstock-specific logic to exclude tags that are unwanted, but I am not sure how this can be implemented. In the meanwhile, we can just update the version manually.

traversaro commented 2 months ago

To be honest, I do not know how to solve this (it would be cool to have some custom feedstock-specific logic to exclude tags that are unwanted, but I am not sure how this can be implemented. In the meanwhile, we can just update the version manually.

I think the logic to find the latest release is finding the https://github.com/casadi/casadi/releases/tag/nightly-issue_3130 (that is not an actual release, just a working tag I guess) and assuming that is the latest releases. To be honest, I do not know how to solve this (it would be cool to have some custom feedstock-specific logic to exclude tags that are unwanted, but I am not sure how this can be implemented. In the meanwhile, we can just update the version manually.

Kind of related to https://github.com/regro/cf-scripts/pull/1441 .

traversaro commented 1 week ago

fyi @agriyakhetarpal I forgot I already opened an issue for the missing automatic update.

traversaro commented 1 week ago

To be honest, I do not know how to solve this (it would be cool to have some custom feedstock-specific logic to exclude tags that are unwanted, but I am not sure how this can be implemented. In the meanwhile, we can just update the version manually.

Probably related to https://github.com/regro/cf-scripts/pull/1441 .