Please Tag Versions #104
Assignees
Comments
willnorris
added a commit
that referenced
this issue
Apr 2, 2024
we've never tagged stable releases, but should really do so. This change will cause our docker images to be tagged following typical semver fashion... the initial `v1.0.0` release will be tagged `v1`, `v1.0`, `v1.0.0`, and `latest`. Updates #104 Signed-off-by: Will Norris <will@tailscale.com>
willnorris
added a commit
that referenced
this issue
May 8, 2024
we've never tagged stable releases, but should really do so. This change will cause our docker images to be tagged following typical semver fashion... the initial `v1.0.0` release will be tagged `v1`, `v1.0`, `v1.0.0`, and `latest`. Updates #104 Signed-off-by: Will Norris <will@tailscale.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While it's nice to be able to just use the "main" tag for the latest update, I would like to specifically know when I'm using a newer version of golink.
The primary problem is right now golink will fall behind in versioning from the tailscale.com go module, hence the "upgrade available" notification in the UI. Right now, I just do a re-deploy from time to time in hopes that maybe the tailscale.com version has been upgraded. Sometimes it has been updated and sometimes it hasn't. Instead of just blindly deploying just to see if the dependency has been updated, I'd rather pin to a specific tagged semantic version so I know if there isn't a new semantic version available, then there is no need to re-deploy.
The text was updated successfully, but these errors were encountered: