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
Hey there, we use Uptrace 1.7.7 in our stack and as I was trying to bring it up the other day, I started receiving errors while trying to pull the image from Docker Hub. Upon investigating, I confirmed that this version, as well as 1.7.6, don't seem to exist anymore: https://hub.docker.com/r/uptrace/uptrace/tags
I'm guessing this the same issue mentioned in #503.
After further digging, I noticed that the following Github Action is failing, and seems to be related to the version in question: https://github.com/uptrace/uptrace/actions/runs/15409688749 . Specifically, it looks like it's failing because actions/cache@v2 was deprecated and has now been fully removed from package repositories. This was addressed in #500, but that branch doesn't appear to have been backported to v1.7.7. I'm guessing this is why just trying to republish that version didn't work the other day.
@vmihailenco this seems like something only a package maintainer can really fix- I hope the extra details here are helpful. Thanks for the work y'all put in, Uptrace is great. 🙂
The text was updated successfully, but these errors were encountered:
Hey there, we use Uptrace 1.7.7 in our stack and as I was trying to bring it up the other day, I started receiving errors while trying to pull the image from Docker Hub. Upon investigating, I confirmed that this version, as well as 1.7.6, don't seem to exist anymore: https://hub.docker.com/r/uptrace/uptrace/tags
I'm guessing this the same issue mentioned in #503.
After further digging, I noticed that the following Github Action is failing, and seems to be related to the version in question: https://github.com/uptrace/uptrace/actions/runs/15409688749 . Specifically, it looks like it's failing because
actions/cache@v2
was deprecated and has now been fully removed from package repositories. This was addressed in #500, but that branch doesn't appear to have been backported tov1.7.7
. I'm guessing this is why just trying to republish that version didn't work the other day.@vmihailenco this seems like something only a package maintainer can really fix- I hope the extra details here are helpful. Thanks for the work y'all put in, Uptrace is great. 🙂
The text was updated successfully, but these errors were encountered: