chore(deps): bump datum-cloud/actions/.github/workflows/publish-kustomize-bundle.yaml from 1.18.0 to 1.21.0

[dependabot]

Bumps datum-cloud/actions/.github/workflows/publish-kustomize-bundle.yaml from 1.18.0 to 1.21.0.

Release notes

Sourced from datum-cloud/actions/.github/workflows/publish-kustomize-bundle.yaml's releases.

v1.21.0

What's Changed

• docs: point agent guidance at shared PR conventions by @​ecv in datum-cloud/actions#92
• feat: Use project Iteration field instead of Month by @​kevwilliams in datum-cloud/actions#93

New Contributors

• @​ecv made their first contribution in datum-cloud/actions#92

Full Changelog: datum-cloud/actions@v1.20.0...v1.21.0

v1.20.0

publish-kustomize-bundle: add a multi-image images input (a list of {path, name, tag}) so a bundle can pin several differently-named images across their overlays in one call. Backward-compatible — the existing single-image image-name / image-overlays inputs are unchanged and used when images is omitted. (#89)

v1.19.0

Add a build-secrets input to publish-docker.yaml for forwarding BuildKit secrets (RUN --mount=type=secret,id=<name>) to the image build — e.g. authenticated apt/package repositories — without baking them into image layers or history. Passed via the caller's secrets: block. (#87)

Commits

• 2dbca23 feat: Use project Iteration field instead of Month (#93)
• ded56f8 feat(set-project-month): use Iteration field instead of Month
• 7e7fe34 docs: point agent guidance at shared PR conventions (#92)
• 8158667 docs: point agent guidance at shared PR conventions
• a39a3b1 feat(publish-kustomize-bundle): stamp multiple images into one bundle (#89)
• 79af1d1 feat(publish-kustomize-bundle): stamp multiple images into the bundle
• db4c3a6 feat(publish-docker): add build-secrets input for BuildKit secrets (#87)
• 1f5c2aa feat(publish-docker): accept build-secrets via the secrets block
• 5af3a92 ci(publish-docker): add trailing newline to workflow file
• 0c3b44c feat(publish-docker): add build-secrets input for BuildKit secrets
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[ecv]

Closing this pull request. Renovate already runs in this repository under the shared policy, and the Dependabot config that opened this pull request is being removed in #64.

Dependabot alerts stay on; only its pull requests go away. The update this pull request carried arrives through Renovate instead.

https://github.com/datum-cloud/infra/issues/5083

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.