Skip to content

chore: bump datum-cloud/actions to v1.14.0#157

Merged
scotwells merged 1 commit into
mainfrom
chore/bump-actions-v1.14.0
May 12, 2026
Merged

chore: bump datum-cloud/actions to v1.14.0#157
scotwells merged 1 commit into
mainfrom
chore/bump-actions-v1.14.0

Conversation

@scotwells
Copy link
Copy Markdown
Contributor

@scotwells scotwells commented May 12, 2026

Summary

  • Bump publish-docker.yaml from @v1.13.1@v1.14.0
  • Bump publish-kustomize-bundle.yaml from @v1.5.1@v1.14.0

Why

v1.14.0 of the kustomize bundle action adds a v0.0.0- prefix to published OCI tags (e.g. v0.0.0-main-20260512-120000), making them semver-compatible.

The infra repo's staging OCIRepository for network-services-operator-kustomize uses semver: ">=0.0.0-0" with a semver filter to auto-track pre-release bundles. Without the v0.0.0- prefix the filter fails to match any tags, causing the staging Flux Kustomization to stall on a pinned tag.

Test plan

  • CI passes on this PR (workflow runs with new action version)
  • After merge, verify new v0.0.0-main-* tags appear in ghcr.io/datum-cloud/network-services-operator-kustomize
  • Confirm staging OCIRepository in infra repo picks up the new tag

Bump publish-docker.yaml from v1.13.1 and publish-kustomize-bundle.yaml
from v1.5.1 to v1.14.0.

The v1.14.0 kustomize bundle action adds a v0.0.0- prefix to published
tags (e.g. v0.0.0-main-20260512-120000), making them semver-compatible.
This allows the infra repo's staging OCIRepository to use semver range
filtering instead of pinned tags for automatic updates.
@scotwells scotwells enabled auto-merge May 12, 2026 17:54
@scotwells scotwells merged commit d4ad4a0 into main May 12, 2026
11 checks passed
@scotwells scotwells deleted the chore/bump-actions-v1.14.0 branch May 12, 2026 17:54
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.

2 participants