Skip to content

docs: Document helm push --oci-strict-version flag#2177

Draft
promptless-for-oss wants to merge 1 commit into
helm:mainfrom
Promptless:promptless/document-oci-strict-version-push-flag
Draft

docs: Document helm push --oci-strict-version flag#2177
promptless-for-oss wants to merge 1 commit into
helm:mainfrom
Promptless:promptless/document-oci-strict-version-push-flag

Conversation

@promptless-for-oss

Copy link
Copy Markdown
Contributor

Open this suggestion in Promptless to view citations and reasoning process

Adds a "Publishing non-strict-semver versions" subsection to the OCI-based registries topic. It explains the new --oci-strict-version flag on helm push, which derives the OCI tag from the canonical strict-semver representation of the chart version (e.g. v1.2.31.2.3) so pushed tags round-trip through helm pull. Based on helm/helm#32349 (open, unmerged).

Trigger Events


Tip: Sort by Shortest Review in the Dashboard to find quick wins ⚡

Add a subsection to the OCI registries topic explaining the
--oci-strict-version flag for helm push, which derives the OCI tag from
the canonical strict-semver representation of the chart version so the
tag round-trips through helm pull.

Refs helm/helm#32349

Signed-off-by: promptless[bot] <promptless[bot]@users.noreply.github.com>
As of version v0.10.0, the plugin has been renamed to `cm-push`.

#### Publishing non-strict-semver versions

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Documented the new --oci-strict-version flag from PR #32349. The flag name, default (false), and help text ("derive the OCI tag from the parsed/sanitized semver representation of the chart version") come from f.BoolVar in pkg/cmd/push.go; the tag-derivation via semver.NewVersion(...).String() (e.g. v1.2.31.2.3) is in resolveOCITagVersion in pkg/pusher/ocipusher.go. The pull-side asymmetry the flag addresses — helm pull discards non-strict-semver tags via semver.StrictNewVersion() in pkg/registry/client.go — informed the "silently skipped" explanation.

Source: helm/helm#32349

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant