You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I opened a pr updating tinyspline yesterday at conan-io/conan-center-index#3639.
The bot has not picked up that pr the day after.
Running conan-center-bot status also marks tinyspline as not updated:
| tinyspline | 0.2.0 | 0.3.0 | v0.3.0 | 0 |
Maybe this is because tinyspline changed its method of tagging releases? 0.2.0 was tagged as 0.2.0 and 0.3.0 as v0.3.0.
The text was updated successfully, but these errors were encountered:
The issue is that both the PR title and body refer to the upgrade as "0.3" instead "0.3.0", which is the string CCB is looking for.
Checking the actual PR content would require cloning and the repo and analyzing the diff (for every opened PR), which I think is both overly complicated and time consuking.
There a "lighter" way to do it: you can download the diff of a PR by using the diff_url property. This does not consume GH API credits,. You can then use https://github.com/matiasb/python-unidiff to analyse the change to conandata.yml files
I opened a pr updating tinyspline yesterday at conan-io/conan-center-index#3639.
The bot has not picked up that pr the day after.
Running
conan-center-bot status
also marks tinyspline as not updated:Maybe this is because tinyspline changed its method of tagging releases?
0.2.0
was tagged as0.2.0
and0.3.0
asv0.3.0
.The text was updated successfully, but these errors were encountered: