18 days ago
I’m using Railway with a public GHCR image and enabled:
- Auto updates: Automatically update to the latest tag
- Maintenance window: At any time, immediately
Image:
- ghcr.io/kortyx-io/website:latest
Flow:
1. CI builds/pushes staging-latest and staging-vX.Y.Z.
2. Promote workflow retags staging-latest -> latest using docker buildx imagetools create ....
Issue:
- When a new image version entry is published in GHCR, Railway updates quickly.
- When latest is retagged/moved to a new digest, Railway often does not redeploy immediately (sometimes not for a long time), even though latest digest changed.
Verification:
- GHCR shows latest digest changed and matches staging-latest.
- Running ghcr.io/kortyx-io/website:latest locally pulls the new image.
Question:
- Is GHCR tag retag/move (without creating a new version entry) supported as an immediate trigger for Railway auto-updates?
- If not, what is the recommended approach for immediate production rollout (immutable semver tags, API redeploy, etc.)?
2 Replies
18 days ago
Image upgrades are not guaranteed to be instant. We cache the digest for several hours to avoid rate limiting by image registries.
If you want instant image deploys when you publish a new version, you would have to use something like this -
https://github.com/brody192/image-update-and-redeploy
Status changed to Awaiting User Response Railway • 18 days ago
18 days ago
Thanks @brody, I will check the link.
Edit: Implemented the cli solution, works great!
Status changed to Awaiting Railway Response Railway • 18 days ago
Status changed to Solved neddl • 18 days ago