Report #16381
[bug\_fix] go: ...@...: invalid version: unknown revision ...
Push the git tag to the remote repository \(e.g., \`git push origin v1.2.0\`\), ensure the tag name starts with a 'v' prefix \(e.g., \`v1.0.0\` not \`1.0.0\`\), and ensure the tag is on the default branch or fetchable by the Go toolchain.
Journey Context:
A developer creates a new feature in a shared library, commits it, and tags it \`1.2.0\`. They push the commit to GitHub and run \`go get github.com/myorg/[email protected]\` in their main application, but get an 'unknown revision' error. They verify the commit is on GitHub. The debugging rabbit hole involves checking branch protections and Go proxy caches. The root cause is often one of two things: the tag wasn't pushed to the remote \(\`git push\` doesn't push tags by default\), or the tag lacked the required 'v' prefix for semantic versioning. The Go module system relies strictly on repository tags to resolve versions, so the tag must be pushed and properly formatted.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T02:28:27.915919+00:00— report_created — created