chore(deps): update datum-cloud/actions action to v1.20.0

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
datum-cloud/actions	action	minor	v1.5.2 → v1.20.0

---

Release Notes

datum-cloud/actions (datum-cloud/actions)

v1.20.0

Compare Source

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

Compare Source

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)

v1.18.0

Compare Source

update-plugin-index is now a composite action

The plugin-catalog updater from v1.17.0 shipped as a reusable workflow, but that form can't actually authenticate cross-repo: a GitHub App token minted in one job and handed to a reusable-workflow job arrives empty, because masked secret values don't survive the job-to-job hop. This release re-delivers it as a composite action so the token is minted and used in the same job.

Same job — same purpose: when a service publishes a release, open a PR against your datumctl plugin catalog that bumps the plugin's manifest to the new version, refreshing every per-platform download URL and checksum straight from the release's checksums.txt. Nothing about a specific plugin is hardcoded, and the manifest's formatting and comments are preserved.

Using it

Mint the catalog token and call the action in the same job:

- name: Mint catalog token
  id: app-token
  uses: actions/create-github-app-token@v2
  with:
    app-id: ${{ secrets.PLUGIN_INDEX_APP_ID }}
    private-key: ${{ secrets.PLUGIN_INDEX_APP_PRIVATE_KEY }}
    owner: your-org
    repositories: your-catalog

- name: Open the catalog PR
  uses: datum-cloud/actions/update-plugin-index@v1.18.0
  with:
    index-repo: your-org/your-catalog
    plugin-name: your-plugin
    version: ${{ github.event.release.tag_name }}
    token: ${{ steps.app-token.outputs.token }}

Migrating from v1.17.0

• Reference the action path datum-cloud/actions/update-plugin-index@v1.18.0, not the .github/workflows/... reusable-workflow path.
• The credential is now the token input (mint it in the same job) instead of the PLUGIN_INDEX_TOKEN secret.
• The generated PR now links back to the source release so reviewers can see what shipped.

The reusable-workflow form from v1.17.0 is superseded and should not be used.

Full Changelog: datum-cloud/actions@v1.17.0...v1.18.0

v1.17.0

Compare Source

Keep plugin catalogs in sync with releases — automatically

Adds the update-plugin-index reusable workflow. When a service publishes a release, it opens a PR against your datumctl plugin catalog that bumps the plugin's manifest to the new version — refreshing every per-platform download URL and checksum straight from the release's checksums.txt. No more hand-editing a catalog manifest after each release.

• Generic across plugins — it derives what to update from the manifest's existing platform list, so nothing about a specific plugin is hardcoded.
• Safe cross-repo — authenticates to the catalog repo with a token you supply, and preserves the manifest's formatting and comments (only version, URLs, and checksums change).
• Drop-in — leaves the rest of your release pipeline untouched; the catalog's own CI still validates the resulting PR.

Using it

uses: datum-cloud/actions/.github/workflows/update-plugin-index.yaml@v1.17.0
with:
  index-repo: your-org/your-catalog
  plugin-name: your-plugin
  version: ${{ github.event.release.tag_name }}
secrets:
  PLUGIN_INDEX_TOKEN: ${{ steps.app-token.outputs.token }}

Introduced in #​84.

Full Changelog: datum-cloud/actions@v1.16.0...v1.17.0

v1.16.0

Compare Source

What's Changed

• chore(deps): update docker/login-action action to v4.2.0 by @​renovate[bot] in #​74
• feat(nix): add nix-update-hash reusable workflow by @​drewr in #​75
• chore(deps): update peter-evans/create-pull-request action to v8 by @​renovate[bot] in #​76
• fix(nix): push hash update directly to triggering branch by @​drewr in #​77
• feat(validate-kustomize): build with LoadRestrictionsNone by default by @​scotwells in #​80

Full Changelog: datum-cloud/actions@v1.15.0...v1.16.0

v1.15.0

Compare Source

What's Changed

• chore(deps): update pnpm/action-setup action to v6 by @​renovate[bot] in #​68
• feat: add reusable generate-doc-toc workflow by @​drewr in #​69
• fix(generate-doc-toc): open PR instead of pushing to main by @​drewr in #​70
• fix(bump-npm-version): land bump commit on main, not detached HEAD by @​kevwilliams in #​72

Full Changelog: datum-cloud/actions@v1.14.0...v1.15.0

v1.14.0

Compare Source

What's Changed

• Delete _JOS7378.jpg by @​bmertens-datum in #​55
• chore: add CODEOWNERS by @​scotwells in #​65
• feat: add configurable registry-organization input to publish-docker workflow by @​scotwells in #​64
• chore(deps): update docker/login-action action to v3.7.0 by @​renovate[bot] in #​36
• chore(deps): update docker/build-push-action action to v6.19.2 by @​renovate[bot] in #​37
• chore(deps): update actions/checkout action to v6 by @​renovate[bot] in #​40
• chore(deps): update actions/setup-node action to v6 by @​renovate[bot] in #​41
• chore(deps): update actions/upload-artifact action to v7 by @​renovate[bot] in #​43
• chore(deps): update docker/login-action action to v4 by @​renovate[bot] in #​45
• chore(deps): update docker/setup-buildx-action action to v4 by @​renovate[bot] in #​46
• chore(deps): update docker/metadata-action action to v6 by @​renovate[bot] in #​48
• chore(deps): update dorny/paths-filter action to v4 by @​renovate[bot] in #​67
• chore(deps): update actions/create-github-app-token action to v3 by @​renovate[bot] in #​66
• chore(deps): update docker/build-push-action action to v7 by @​renovate[bot] in #​47
• chore: configure Claude Code datum plugins by @​scotwells in #​38

New Contributors

• @​bmertens-datum made their first contribution in #​55

Full Changelog: datum-cloud/actions@v1.13.3...v1.14.0

v1.13.3

Compare Source

Remove manual kustomize install steps — kustomize is already pre-installed on GitHub-hosted runners.

v1.13.2

Compare Source

What's Changed

• feat: add set-project-month reusable workflow by @​kevwilliams in #​61
• feat: switch set-project-month to GitHub App token by @​kevwilliams in #​62

Full Changelog: datum-cloud/actions@v1.13.1...v1.13.2

v1.13.1

Compare Source

v1.13.0

Compare Source

v1.12.1

Compare Source

What's Changed

• fix: checkout main branch in publish-release to fix detached HEAD push failure by @​scotwells in #​57

Full Changelog: datum-cloud/actions@v0.12.0...v1.12.1

v1.12.0

Compare Source

What's Changed

• feat: add dev build mode to npm publish workflow by @​scotwells in #​56

Full Changelog: datum-cloud/actions@v1.11.0...v0.12.0

What's Changed

• feat: add dev build mode to npm publish workflow by @​scotwells in #​56

Full Changelog: datum-cloud/actions@v1.11.0...v1.12.0

v1.11.0

Compare Source

What's Changed

• fix: support packages in subdirectories for npm publishing — The publish-npm-package workflow now correctly handles packages that live in subdirectories (e.g. ui/) by reading packageManager from the package's own package.json and running install/build in the correct working directory.

v1.10.0

Compare Source

What's Changed

• Adding publish npm package workflow by @​kevwilliams in #​39
• Enforce single assignee on issues by @​drewr in #​49
• fix(enforce-single-assignee): comment when multiple owners by @​drewr in #​51
• fix(enforce-single-assignee): add concurrency group by @​drewr in #​52
• fix(enforce-single-assignee): fetch live assignees and sleep before acting by @​drewr in #​53

New Contributors

• @​kevwilliams made their first contribution in #​39
• @​drewr made their first contribution in #​49

Full Changelog: datum-cloud/actions@v1.9.0...v1.10.0

v1.9.0

Compare Source

What's Changed

• chore(deps): update actions/checkout action to v6 by @​renovate[bot] in #​32
• chore(deps): update actions/upload-artifact action to v5 by @​renovate[bot] in #​30
• chore(deps): update fluxcd/flux2 action to v2.7.5 by @​renovate[bot] in #​28
• chore(deps): update actions/upload-artifact action to v6 by @​renovate[bot] in #​34
• chore(deps): update docker/login-action action to v3.6.0 by @​renovate[bot] in #​17
• chore: add context and dockerfile-path params and resolve intermittent kustomize OCI artifact structure by @​OscarLlamas6 in #​33

Full Changelog: datum-cloud/actions@v1.8.1...v1.9.0

v1.8.1

Compare Source

What's Changed

• Support multi-arch builds by @​wnagele in #​31

New Contributors

• @​wnagele made their first contribution in #​31

Full Changelog: datum-cloud/actions@v1.8.0...v1.8.1

v1.8.0

Compare Source

What's Changed

• Add snyk scan by @​OscarLlamas6 in #​29

Full Changelog: datum-cloud/actions@v1.7.4...v1.8.0

v1.7.4

Compare Source

What's Changed

• chore: Specifying version for Flux action by @​OscarLlamas6 in #​27

Full Changelog: datum-cloud/actions@v1.7.3...v1.7.4

v1.7.3

Compare Source

What's Changed

• chore: prioritize timestamped tags in metadata extraction by @​OscarLlamas6 in #​26

Full Changelog: datum-cloud/actions@v1.7.2...v1.7.3

v1.7.2

Compare Source

What's Changed

• chore: add semver compliance, new outputs and build target support to workflows by @​OscarLlamas6 in #​25

Full Changelog: datum-cloud/actions@v1.7.1...v1.7.2

v1.7.1

Compare Source

What's Changed

• Forces a SemVer compliant version number on all builds

Full Changelog: datum-cloud/actions@v1.7.0...v1.7.1

v1.7.0

Compare Source

What's Changed

• feat: add build information to docker build args by @​scotwells in #​24

Full Changelog: datum-cloud/actions@v1.6.5...v1.7.0

v1.6.5

Compare Source

What's Changed

• chore: sentry token as optional build arg by @​OscarLlamas6 in #​23

Full Changelog: datum-cloud/actions@v1.6.4...v1.6.5

v1.6.4

Compare Source

What's Changed

• Add version tag extraction step to Docker workflow by @​OscarLlamas6 in #​22

Full Changelog: datum-cloud/actions@v1.6.3...v1.6.4

v1.6.3

Compare Source

What's Changed

• chore: extract version by @​OscarLlamas6 in #​21

Full Changelog: datum-cloud/actions@v1.6.2...v1.6.3

v1.6.2

Compare Source

What's Changed

• chore: add version as build arg by @​OscarLlamas6 in #​20

Full Changelog: datum-cloud/actions@v1.6.1...v1.6.2

v1.6.1

Compare Source

What's Changed

• chore: enable helm for kustomizations validator by @​OscarLlamas6 in #​19

Full Changelog: datum-cloud/actions@v1.6.0...v1.6.1

v1.6.0

Compare Source

What's Changed

• add: kustomization validator action by @​OscarLlamas6 in #​16

New Contributors

• @​OscarLlamas6 made their first contribution in #​16

Full Changelog: datum-cloud/actions@v1.5.2...v1.6.0

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[cla-assistant]

All committers have signed the CLA.

[cla-assistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}