Hello, I've been working on a new recipe for mealie here: https://git.coopcloud.tech/coop-cloud/mealie
Yesterday I released [v1.0.1+v2.8.0]([url](https://git.coopcloud.tech/coop-cloud/mealie/commit/69c7953e4ebcf4072275c4f8318addc960d0be35)) and I see that the drone job for updating the catalogue ran successfully: https://build.coopcloud.tech/coop-cloud/mealie/7/1/1
But no commit landed in this repo.
From the logs, looks like the drone job in the mealie repo just triggers [this new run](https://build.coopcloud.tech/toolshed/auto-recipes-catalogue-json/1665/1/2), which doesn't mention mealie.
Did I skip a step somewhere? Thanks in advance!
PS: looks like the matrix password expired for [alerts of CI failures](https://build.coopcloud.tech/toolshed/auto-recipes-catalogue-json/1665/1/3).
It turns out that https://git.coopcloud.tech/toolshed/auto-recipes-catalogue-json is using an old version of abra (0.9.0) since that's the version used by https://git.coopcloud.tech/toolshed/drone-abra/, and we can't update it since there's no 0.10.1 version of the abra docker image (only `latest`).
As a result, 0.9.0 of abra has code that will skip repos unless they have the "recipe" topic, which was later removed: https://git.coopcloud.tech/toolshed/abra/pulls/445/files
The real fix for this issue is to update drone-abra, but the workaround is to add the "recipe" topic to new repos by clicking "Manage topics":
<img width="327" alt="image.png" src="attachments/b60ff90f-35bb-49bb-b796-bb445a742274">
Once I did that and pushed a new tag, the build worked: https://build.coopcloud.tech/toolshed/auto-recipes-catalogue-json/1734/1/2
https://git.coopcloud.tech/toolshed/recipes-catalogue-json/commit/00220f920001994b9b05cf852ccba3f78dafb66a
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Hello, I've been working on a new recipe for mealie here: https://git.coopcloud.tech/coop-cloud/mealie
Yesterday I released v1.0.1+v2.8.0 and I see that the drone job for updating the catalogue ran successfully: https://build.coopcloud.tech/coop-cloud/mealie/7/1/1
But no commit landed in this repo.
From the logs, looks like the drone job in the mealie repo just triggers this new run, which doesn't mention mealie.
Did I skip a step somewhere? Thanks in advance!
PS: looks like the matrix password expired for alerts of CI failures.
It turns out that https://git.coopcloud.tech/toolshed/auto-recipes-catalogue-json is using an old version of abra (0.9.0) since that's the version used by https://git.coopcloud.tech/toolshed/drone-abra/, and we can't update it since there's no 0.10.1 version of the abra docker image (only
latest).As a result, 0.9.0 of abra has code that will skip repos unless they have the "recipe" topic, which was later removed: https://git.coopcloud.tech/toolshed/abra/pulls/445/files
The real fix for this issue is to update drone-abra, but the workaround is to add the "recipe" topic to new repos by clicking "Manage topics":
Once I did that and pushed a new tag, the build worked: https://build.coopcloud.tech/toolshed/auto-recipes-catalogue-json/1734/1/2
00220f9200