Solution skill
Pin rudder-server to a real release tag, not the odd-looking 31082021.130106 tag
Complete solution
Shows how to fix pin rudder-server to a real release tag, not the odd-looking 31082021.130106 tag. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
The maintainers recommend either rudderlabs/rudder-server:latest or, if you want stability without surprise breaking changes, a pinned release tag like rudder-server:1.32. Check the GitHub Releases section of rudderlabs/rudder-server for the current stable tag before pinning.
Steps
- If your dependency manager (Renovate, Dependabot, etc.) suggests the rudder-server tag 31082021.130106, ignore it: that is an old build artifact, not a real release, and pulling it would downgrade you years back. The maintainers recommend either rudderlabs/rudder-server:latest or, if you want stability without surprise breaking changes, a pinned release tag like rudder-server:1.32. Check the GitHub Releases section of rudderlabs/rudder-server for the current stable tag before pinning. This is a good general rule for this image: never trust a numeric-looking tag you do not recognize; the release tags are the ones documented in the releases page.
- Source: https://github.com/rudderlabs/rudder-server/issues/5026 (RudderStack)
When to use
You are seeing this: If your dependency manager (Renovate, Dependabot, etc.) suggests the rudder-server tag 31082021.130106, ignore it: that is an old build artifact, not a real release, and pulling it would downgrade you years back. Use this skill when you run into "Pin rudder-server to a real release tag, not the odd-looking 31082021.130106 tag".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Sources
- https://github.com/rudderlabs/rudder-server/issues/5026
Evidence
In gh:rudderlabs/rudder-server#5026, the issue was: A user wiring up Renovate noticed it wanted to upgrade the rudderlabs/rudder-server image to the strange tag 31082021.130106. A maintainer confirmed that tag is just a very old build and not a release: use the latest tag or pin a specific stable version instead. The reporter said they avoid latest in production to dodge breaking changes, and the maintainer pointed them at pulling a specific release tag like 1.32, checkable in the repo GitHub Releases section.. The verified answer: If your dependency manager (Renovate, Dependabot, etc.) suggests the rudder-server tag 31082021.130106, ignore it: that is an old build artifact, not a real release, and pulling it would downgrade you years back. The maintainers recommend either rudderlabs/rudder-server:latest or, if you want stability without surprise breaking changes, a pinned release tag like rudder-server:1.32. Check the GitHub Releases section of rudderlabs/rudder-server for the current stable tag before pinning.. Issue URL: https://github.com/rudderlabs/rudder-server/issues/5026
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_mjx19vUB3vYOHmGsgyKPjg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Pin rudder-server to a real release tag, not the odd-looking 31082021.130106 tag <span>— Vectle</span></a>