Publish major and minor version tags

[felipecrs]

Such as:

denoland/deno:v2
denoland/deno:v2.1
denoland/deno:alpine-v2
denoland/deno:alpine-v2.1

[felipecrs]

Complementing:

It is already possible to pull on latest version, and that's in fact the only option a user has today to avoid having to update the tags manually.

It is however a lot less safe than pinning on major or on minor versions.

Therefore, these additional tags would allow users to transition to more stable tags, bringing peace of mind for not having to use latest.

Note that using latest is also a break for Hadolint, the Dockerfile linter:

• https://github.com/hadolint/hadolint/wiki/DL3007

[Ionaru]

Sonar also trips on using the latest tag: https://web.archive.org/web/20250519042231/https://rules.sonarsource.com/docker/RSPEC-6596/ (web archive link because Sonar took their rules website down 😑)

I would prefer not to use latest, but still keep up-to-date with minor versions of Deno within the 2.x version range. My expectation was that this was a pretty standard practice.

Is there a workaround for this?

[felipecrs]

Is there a workaround for this?

Not quite a workaround, but you can pin to the specific version and let Renovate update it for you.