I followed the instructions on the README to create a new navidrome app on my server and deploy it but I ran into this error preventing deployment:
FATA lint error in navidrome configs: "only annotated tags used for recipe version" failed lint checks (R014)
It looks like only the first tag in the repository (0.1.0+pr-3349) is annotated and the more recent one (0.2.0+0.58.0) is lightweight. But even when I tried to deploy version 0.1.0+pr-3349 I am still seeing the above error message. I also tried removing the navidrome recipe folder, removing the app via abra and generating it again with abra app new navidrome 0.1.0+pr-3349 but that still didn't work.
I followed the instructions on the README to create a new navidrome app on my server and deploy it but I ran into this error preventing deployment:
```
FATA lint error in navidrome configs: "only annotated tags used for recipe version" failed lint checks (R014)
```
It looks like only the first tag in the repository (0.1.0+pr-3349) is annotated and the more recent one (0.2.0+0.58.0) is lightweight. But even when I tried to deploy version 0.1.0+pr-3349 I am still seeing the above error message. I also tried removing the navidrome recipe folder, removing the app via abra and generating it again with `abra app new navidrome 0.1.0+pr-3349` but that still didn't work.
Thanks for raising @jmakdah2! @pharaohgraphy can you re-release https://git.coopcloud.tech/coop-cloud/navidrome/releases/tag/0.2.0+0.58.0 using `abra` or with `-a` if you're using git directly? it's a limitation in `abra` that it cannot handle lightweight tags 🙈
I had no idea and I'd never used git tag before... apologies ☠️
If you recall, I had issues getting the release working within abra on my Mac, so I resorted to doing it manually via git.
I'm trying to do it now on Linux but it seems there's no way to force the re-release to bypass this error from Abra:
FATA failed to commit changes: no changes discovered in /home/andrew/.abra/recipes/navidrome, nothing to publish?
In lieu of that, I've done it manually & force-pushed via git, I hope that works.
For me: it creates & deploy the app fine now 🙏
> Thanks for raising @jmakdah2! @pharaohgraphy can you re-release https://git.coopcloud.tech/coop-cloud/navidrome/releases/tag/0.2.0+0.58.0 using `abra` or with `-a` if you're using git directly? it's a limitation in `abra` that it cannot handle lightweight tags 🙈
I had no idea and I'd never used `git tag` before... apologies ☠️
If you recall, I had issues getting the release working within `abra` on my Mac, so I resorted to doing it manually via `git`.
I'm trying to do it now on Linux but it seems there's no way to *force* the re-release to bypass this error from Abra:
> FATA failed to commit changes: no changes discovered in /home/andrew/.abra/recipes/navidrome, nothing to publish?
In lieu of that, I've done it manually & force-pushed via `git`, I hope that works.
For me: it creates & deploy the app fine now 🙏
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.
I followed the instructions on the README to create a new navidrome app on my server and deploy it but I ran into this error preventing deployment:
It looks like only the first tag in the repository (0.1.0+pr-3349) is annotated and the more recent one (0.2.0+0.58.0) is lightweight. But even when I tried to deploy version 0.1.0+pr-3349 I am still seeing the above error message. I also tried removing the navidrome recipe folder, removing the app via abra and generating it again with
abra app new navidrome 0.1.0+pr-3349but that still didn't work.Thanks for raising @jmakdah2! @pharaohgraphy can you re-release https://git.coopcloud.tech/coop-cloud/navidrome/releases/tag/0.2.0+0.58.0 using
abraor with-aif you're using git directly? it's a limitation inabrathat it cannot handle lightweight tags 🙈I had no idea and I'd never used
git tagbefore... apologies ☠️If you recall, I had issues getting the release working within
abraon my Mac, so I resorted to doing it manually viagit.I'm trying to do it now on Linux but it seems there's no way to force the re-release to bypass this error from Abra:
In lieu of that, I've done it manually & force-pushed via
git, I hope that works.For me: it creates & deploy the app fine now 🙏
I tried it again after your update @pharaohgraphy and it works now, thanks for the quick fix!