[feat] Add a 'stable' docker tag tracking official releases instead of 'latest' #2350
Assignees
Labels
enhancement
New feature or request
Comments
|
Shouldn't only numbered releases get the 'latest' tag? This broke things for me today too. |
|
In latest releases I change the docker meta action that is responsable to create the required tags based on the event that triggers the workflow. I will fix this ASAP to just update latest when there is a new version release |
robertsLando
added a commit
that referenced
this issue
Apr 5, 2022
|
Fixed by bcf8f44 |
|
I'm really sorry for the issues you are having with latest tag, seems the problem is related to serialport module not working on some archs with docker, follow updates here: #2349 |
|
@robertsLando Many thanks for this! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
In #2349 I experienced a situation where the
latesttag updated with commits to the master branch, breaking my installation when I pulled the new image. When I went to check if there was a new release, the last versioned release in github as well as the last version-tagged docker image was 6.6.2, 10 days previous.I was confused then about what had changed until I dug into the commit history and saw that
latestcorresponded to a major change merged into master but not yet tagged and released. The Zwavejs2mqtt documentation states docker tags tags include "latest for the latest official release" and "master for the bleeding edge version". Therefore it seems thelatesttag was changed in error.Describe the solution you'd like
The consensus seems to be the latest tag is tricky and best avoided, and an alternative I've seen (e.g. in projects such as HomeAssistant) is to maintain a separate
stabletag that tracks the latest official release. That avoids accidental tagging of latest in favor of a custom tag that only gets updated by CI in response to a github release.Describe alternatives you've considered
This may reasonably be considered a bug that
latestis tracking updates tomasterrather than the latest stable release as advertised. Preventing that would also work. But as the article above mentions, it can be very difficult to always preventlatestfrom getting updated at the wrong time.The text was updated successfully, but these errors were encountered: