Skip to content

Fix deriveChartTag to support semver wildcard patterns#1502

Draft
gusevda wants to merge 1 commit into
mainfrom
fix/derive-chart-tag-wildcards
Draft

Fix deriveChartTag to support semver wildcard patterns#1502
gusevda wants to merge 1 commit into
mainfrom
fix/derive-chart-tag-wildcards

Conversation

@gusevda
Copy link
Copy Markdown
Contributor

@gusevda gusevda commented Apr 15, 2026

What does this PR do?

deriveChartTag now handles Masterminds/semver wildcard placeholders (x, X, *) by normalizing them to 0. Previously, inputs like 1.2.x or 1.x returned undefined, which disabled the Edit Deployment button with "missing chart version".

What is the effect of this change to users?

Deployments using wildcard semver constraints (e.g. 1.2.x, 1.*.*) can now be edited via the Edit Deployment button.

Any background context you can provide?

deriveAutoUpgradeMode already handles wildcards correctly. Only deriveChartTag needed updating — its regex required all three version components to be digits.

Examples of the new behavior:

  • 1.2.x1.2.0 (patch wildcard)
  • 1.x / 1.*.*1.0.0 (minor wildcard)
  • ~1.2.x1.2.0 (operator + wildcard)
  • * / x.x.x0.0.0 (full wildcard)

Do the docs need to be updated?

No.

Should this change be mentioned in the release notes?

  • A changeset describing the change and affected packages was added. (more info)

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.

1 participant