firebase-action: New v13.0.1 docker image is unavailable
Download action repository 'w9jds/firebase-action@master' (SHA:40d0dffe78981f0f66d1c704a64fb4ba8b60df20)
Pull down action image 'w9jds/firebase-action:v1[3](https://github.com/zenportinc/web-app/actions/runs/7137315266/job/19437159822#step:2:3).0.1'
/usr/bin/docker pull w9jds/firebase-action:v13.0.1
Error response from daemon: manifest for w9jds/firebase-action:v13.0.1 not found: manifest unknown: manifest unknown
I temporarily fixed my pipeline by changing to w9jds/firebase-action@v12.9.0
About this issue
- Original URL
- State: closed
- Created 7 months ago
- Reactions: 11
- Comments: 17 (2 by maintainers)
@w9jds FYI this just happened again for v13.4.0 haha
Yep, I second this. The v13.0.1 tag no longer exists on docker hub. I guess we shouldn’t be deploying on a Friday anyway 😉
Is it a best practice to tie to a specific version here since @master is unreliable?
I’m having the same issue. All my Github Actions integrations with w9jds/firebase-action@master are currently broken.
If you need to urgently deploy something before an official fix gets released, you can make the following changes in your workflows:
REPLACE:
uses: w9jds/firebase-action@masterWITH:uses: w9jds/firebase-action@v12.9.0@w9jds This is happening for the latest v13.5.2 as well
@w9jds FYI it is happening with the last version v13.5.1
Same here 😢
Hi! Seems to be failing again. Also trying to use version 13.7.4 is failing on my side.
This is occurring with the latest v13.6.1
It appears this version is not aligned with any available docker image tag :13.6.1
As mentioned above, need to update the “uses” flag to the exact version you want to target.
Example: uses: w9jds/firebase-action@v13.6.0
Same issue here