This is a question the Railway community is better placed to answer than support: people who have already worked this out on their own projects and can tell you what actually worked.

So we'd like to open your thread as a community bounty. Railway pays a bounty to the community member who answers it, and threads like this usually get picked up quickly.

Opening it makes this entire thread public, including everything already posted. Nothing becomes public until you decide. Use the buttons below.

• Open to the community - Before you click, take a moment to edit or remove anything you'd rather not share. The thread becomes publicly visible right away.
• Keep it private and close the thread - Nothing becomes public and the thread closes.

Do you have Image Auto Update configured? Also, for the latest tag (fetch newest update), you have to redeploy source image (can be done by pressing CTRL+K > Redeploy source image).

Yes it is configured, also this is incorrect. From your link, latest is supported

For tags like :latest, :canary, or :staging, Railway monitors for new image pushes to that specific tag. When a new image is pushed (same tag, different SHA), Railway redeploys your service.

I had that part wrong indeed, thanks for clarifying it. Nonetheless, since you have it configured, you can still use the redeploy source image suggestion as a workaround, until you find a solution.

That's not a workaround? That's just manually deploying the image.

Registry credentials saved on a service are used when it deploys, but automatic image update checks don't use them right now. That's why a private image can deploy fine while we never detect its newer versions. Your auto-update settings aren't the cause: auto-updates are enabled, not snoozed, and the maintenance window is open all day, every day. Waiting longer or changing those settings won't fix this.

For a private image, the way to move to a newer version today is to change the service's image source to the tag you want and deploy that change. That deploy uses your saved credentials. Also, the service is currently set to a version tag with a patch update policy, not latest.