-
Notifications
You must be signed in to change notification settings - Fork 138
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
Shouldn't tag 'latest' point to latest release? #36
Comments
@jonaszuberbuehler Maybe these article help understand :latest tag: https://vsupalov.com/docker-latest-tag/ https://medium.com/@mccode/the-misunderstood-docker-tag-latest-af3babfd6375 |
Thx!
…--
jonas zuberbuehler
On 14 July 2019 at 13:19:11, Kevin ***@***.***) wrote:
@jonaszuberbuehler <https://github.com/jonaszuberbuehler> Maybe these
article help understand :latest tag:
https://vsupalov.com/docker-latest-tag/
***@***.***/the-misunderstood-docker-tag-latest-af3babfd6375
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#36?email_source=notifications&email_token=AA5C5BWRBCHX667V2BHWU7TP7MDS7A5CNFSM4GYUAO62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZ4DIBI#issuecomment-511194117>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA5C5BUUPEU6CNX4CB65LZ3P7MDS7ANCNFSM4GYUAO6Q>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I was using 'latest' tag and realised that it was using puppeteer version 1.6.0 while tag '1.8.0' uses puppeteer version 1.8.0. IMO the 'latest' tag should point to the latest release.
The text was updated successfully, but these errors were encountered: