Skip to content

Conversation

@vvoland
Copy link
Collaborator

@vvoland vvoland commented Aug 8, 2025

The version generation script was including the 'v' prefix from git tags in generated version strings, which is inconsistent with our current packages.

  • Tagged releases produce clean version numbers (e.g., "1.0.0" instead of "v1.0.0")
  • Nightly builds generate pseudo-versions without 'v' prefix

The version generation script was including the 'v' prefix from git tags
in generated version strings, which is inconsistent with our current
packages.

- Tagged releases produce clean version numbers (e.g., "1.0.0" instead of
  "v1.0.0")
- Nightly builds generate pseudo-versions without 'v' prefix

Signed-off-by: Paweł Gronowski <pawel.gronowski@docker.com>
@vvoland vvoland self-assigned this Aug 8, 2025
@vvoland
Copy link
Collaborator Author

vvoland commented Aug 8, 2025

Copy link
Member

@crazy-max crazy-max left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't recall if current logic was based on docker-ce-packaging or containerd-packaging but looks related to docker/docker-ce-packaging@a6aa399

So agree to be consistent LGTM

@vvoland vvoland marked this pull request as ready for review August 11, 2025 19:22
Copy link
Member

@crazy-max crazy-max left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Btw on actions-toolkit side we support with and without v prefix for version comparison: https://github.com/docker/actions-toolkit/blob/8b99173e2fc71488f68740756350c02cf10c29d3/src/buildx/buildx.ts#L129

@vvoland
Copy link
Collaborator Author

vvoland commented Aug 12, 2025

Yeah it's not really a blocker, but thought that maybe it would be a good opportunity to actually make it consistent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants