-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please Tag Versions #104
Comments
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>
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>
Totally agree on this! I'm not sure to understand what has been done here though. @willnorris PR #122 should have implemented tagging but I'm still unable to see version tags:
Am I missing something? Thanks! |
looks like it's because I just never pushed a new tag after that PR. Maybe I was trying to get a few other PRs landed before tagging, or something? I'm not sure. But I'll go ahead and tag now regardless. |
all set: https://github.com/tailscale/golink/pkgs/container/golink/versions We'll still have to work out a release cadence and such. For now it'll probably just be manual and as needed, but this at least gives folks stable tags to point to. |
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: