-
Notifications
You must be signed in to change notification settings - Fork 513
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
Add 1.X-debian-stable
type alias
#485
Comments
Based on: debuerreotype/docker-debian-artifacts#205 (comment) I have based the `*debian-stable` not on an alias but on a different debian channel. Fixes docker-library#485
Debian is the default variant and the current stable ( |
I see, I missed the Technically debian stable and bookworm are different ( Thx |
I like to use the analogy of a "square wheel" in relation to the way |
Hey I am maintaining some software and I recently noticed that some of our docker images were built with the wrong version of go (
1.19.10
when1.19.12
was the latest on the1.19
branch at the time).AFAIT this is because buster was no longer supported and you switched to bullseye and bookworm instead.
So I should have used
1.19-bulleyes
or1.19-bookworm
images, however our docker deployment is automated and we only really look at it when bumping the major go version (we don't do that automatically due to regressions in the go std ipfs/kubo#10065)As a maintainer that rely on your work it would make my life easier if you could provide an alias along the lines of
1.X-debian-stable
where X is20
or21
to take the current releases of go as example. Exactly like you already do for-alpine
.I guess for consistency the full matrix of precision should also be supported like you do for alpine so:
1.X.Z-debian-stable
1.X-debian-stable
1-debian-stable
debian-stable
But I personally don't need it.
I'm not sure about
-debian-stable
,-debian
or something else could very well be a better name.Thx 🙂
The text was updated successfully, but these errors were encountered: