Repository navigation
chore(deps): update datum-cloud/actions action to v1.22.0 - #30
Merged
Merged
Conversation
scotwells
approved these changes
Oct 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.9.0→v1.22.0Release Notes
datum-cloud/actions
v1.22.0: : Keep NOTICE files currentCompare Source
Repositories with a NOTICE file can now keep it current automatically, and dependency pull requests get both their NOTICE and Nix hash commits.
What's new
update-noticeruns a repository's NOTICE task when Go dependencies change on a branch and commits the result to that branch. (#100)nix-update-hashnow rebases and retries its push when another workflow commits to the branch first, rather than failing. (#100)publish-dockerstampsBUILD_DATEas the build time in UTC, and sets it on release builds, where it was empty. (#94)update-plugin-indexrefreshes the existing catalog pull request for a plugin instead of opening another one. (#98)v1.21.0Compare Source
What's Changed
New Contributors
Full Changelog: datum-cloud/actions@v1.20.0...v1.21.0
v1.20.0Compare Source
publish-kustomize-bundle: add a multi-imageimagesinput (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-imageimage-name/image-overlaysinputs are unchanged and used whenimagesis omitted. (#89)v1.19.0Compare Source
Add a
build-secretsinput topublish-docker.yamlfor 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'ssecrets:block. (#87)v1.18.0Compare Source
update-plugin-indexis now a composite actionThe 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:
Migrating from v1.17.0
datum-cloud/actions/update-plugin-index@v1.18.0, not the.github/workflows/...reusable-workflow path.tokeninput (mint it in the same job) instead of thePLUGIN_INDEX_TOKENsecret.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.0Compare Source
Keep plugin catalogs in sync with releases — automatically
Adds the
update-plugin-indexreusable 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'schecksums.txt. No more hand-editing a catalog manifest after each release.Using it
Introduced in #84.
Full Changelog: datum-cloud/actions@v1.16.0...v1.17.0
v1.16.0Compare Source
What's Changed
Full Changelog: datum-cloud/actions@v1.15.0...v1.16.0
v1.15.0Compare Source
What's Changed
Full Changelog: datum-cloud/actions@v1.14.0...v1.15.0
v1.14.0Compare Source
What's Changed
New Contributors
Full Changelog: datum-cloud/actions@v1.13.3...v1.14.0
v1.13.3Compare Source
Remove manual kustomize install steps — kustomize is already pre-installed on GitHub-hosted runners.
v1.13.2Compare Source
What's Changed
Full Changelog: datum-cloud/actions@v1.13.1...v1.13.2
v1.13.1Compare Source
v1.13.0Compare Source
v1.12.1Compare Source
What's Changed
Full Changelog: datum-cloud/actions@v0.12.0...v1.12.1
v1.12.0Compare Source
What's Changed
Full Changelog: datum-cloud/actions@v1.11.0...v0.12.0
What's Changed
Full Changelog: datum-cloud/actions@v1.11.0...v1.12.0
v1.11.0Compare Source
What's Changed
publish-npm-packageworkflow now correctly handles packages that live in subdirectories (e.g.ui/) by readingpackageManagerfrom the package's ownpackage.jsonand running install/build in the correct working directory.v1.10.0Compare Source
What's Changed
New Contributors
Full Changelog: datum-cloud/actions@v1.9.0...v1.10.0
Configuration
📅 Schedule: (UTC)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.