Skip to content

Add "major" and "major.minor" version tags on docker images #1594

@nop-infra

Description

@nop-infra

Hello!

  • Vote on this issue by adding a 👍 reaction
  • If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

I am using the step-ca docker image in production.
I do not want to use the "latest" tag, to prevent updating the containers to a major version (with breaking changes) by accident.
Today, I have to tag the exact version (major.minor.patch) and manually updating it each time there is a new version.

It would be great to have "major" and "major.minor" tags on docker hub to make maintenance more convenient.

Today, version tags on docker hub only uses full version of semantic versioning : major.minor.patch (0.25.0 for example)

It would be great to have the following tags :

  • "major" (0 for example) : this is the latest image version for the major version 0
  • "major.minor" (0.25 for example) : this is the latest version the the minor version 0.25

Why is this needed?

With these two new tag type, it becomes possible to :

  • If using "major" tag : fix the major version and ensure it is up to date, with all minor update and patches. The update is automatic as with "latest" but we ensure the container is not updated to another major version
  • If using "major.minor" tag : fix the minor version and ensure it is up to date, with all the patches applied.

Metadata

Metadata

Assignees

Labels

enhancementneeds triageWaiting for discussion / prioritization by team

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions