Repository navigation
chore(deps): update datum-cloud/actions action to v1.29.0 - #86
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
andrewb3000
previously approved these changes
Nov 17, 2026
andrewb3000
left a comment
There was a problem hiding this comment.
Non-blocking
.github/workflows/publish.yaml:15: The reusable workflows are pinned to a tag, not a commit SHA, and publish passessecrets: inheritto them. A moved tag would run new code with this repo's publish secrets. This was already the case before the PR. Consider SHA pinning with Renovate digest updates.
Checked
.github/workflows/publish.yaml:15: Only theuses:tags change. Triggers, permissions andsecrets: inheritare the same as before. The one change these workflows pick up is the new 60-minute defaulttimeout-minutesin publish-docker. CI passed.
renovate
Bot
force-pushed
the
renovate/datum-cloud-actions-1.x
branch
from
November 18, 2026 21:35
67ab8f3 to
8eab82a
Compare
scotwells
approved these changes
Nov 18, 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.26.0→v1.29.0Release Notes
datum-cloud/actions
v1.29.0: : ActivityPolicy tests and lockfile source checkCompare Source
Two new reusable workflows: one tests a repository's ActivityPolicies, the other blocks JavaScript lockfiles that install packages from outside an approved registry.
What's new
test-activity-policies.yamlvalidates a repository'sActivityPolicymanifests and runs their*.test.yamlunit tests withactivitytool. Policies can come from files, folders, or kustomizations, several at once. Tests run in theghcr.io/milo-os/activitytoolimage, pinned by digest, offline and read-only. Setactivitytool-versionto the Activity release you deploy (defaultv0.10.0). See docs/activity-policies. (#142)lockfile-check.yamlfails when a committed npm, pnpm, or Yarn lockfile resolves a package from a tarball URL, a git repository, or a file outside the repository instead of an approved registry. See docs/lockfile-check. (#138)Other changes
v1.28.0: : One approval per plugin releaseCompare Source
A plugin release now reaches datumctl users after one approval in its catalog instead of two.
What's new
update-plugin-indexandplugin-catalog-scannow rebuild the catalog'sindex.yamlinside the update pull request, keeping its header, so merging it publishes the release. Several update pull requests open at once still merge cleanly, and a catalog with noindex.yamlis left alone. (#136)v1.27.1: : Release scan on any default branchCompare Source
The plugin release scan now works on catalogs whose default branch isn't
main.What's new
plugin-catalog-scanopens and reuses update pull requests on the catalog's default branch instead of assumingmain. (#133)v1.27.0: : Shared plugin catalog workflowsCompare Source
A datumctl plugin catalog can now validate, rebuild, and update itself with four reusable workflows instead of its own scripts.
What's new
plugin-catalog-validatechecks every manifest against a shared schema anddatumctl plugin index validate, and downloads changed archives to check their checksums.plugin-catalog-indexrebuildsindex.yamlthrough an auto-merging pull request,plugin-catalog-scanopens update pull requests for newer plugin releases daily, andplugin-catalog-healthre-checks every archive weekly and opens an issue on failure. The index and scan workflows push with a GitHub App token, so their pull requests run CI without a maintainer approving each run. (#131)publish-docker. The newtimeout-minutesinput, default 60, sets how long a build may run before GitHub cancels it. (#130)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.