Skip to content

chore(deps): update datum-cloud/actions action to v1.29.0 - #86

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/datum-cloud-actions-1.x
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/datum-cloud-actions-1.x

Conversation

@renovate

@renovate renovate Bot commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
datum-cloud/actions workflow minor v1.26.0 → v1.29.0

Release Notes

datum-cloud/actions

v1.29.0: : ActivityPolicy tests and lockfile source check

Compare 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
  • ActivityPolicy tests. test-activity-policies.yaml validates a repository's ActivityPolicy manifests and runs their *.test.yaml unit tests with activitytool. Policies can come from files, folders, or kustomizations, several at once. Tests run in the ghcr.io/milo-os/activitytool image, pinned by digest, offline and read-only. Set activitytool-version to the Activity release you deploy (default v0.10.0). See docs/activity-policies. (#​142)
  • Lockfile source check. lockfile-check.yaml fails 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
  • The SRE team is now a code owner. (#​141)

v1.28.0: : One approval per plugin release

Compare Source

A plugin release now reaches datumctl users after one approval in its catalog instead of two.

What's new
  • Index in the update pull request. update-plugin-index and plugin-catalog-scan now rebuild the catalog's index.yaml inside 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 no index.yaml is left alone. (#​136)

[!NOTE]
This is on by default. Set rebuild-index: false on update-plugin-index to leave index.yaml to the catalog's own rebuild workflow, which still runs for manifests edited by hand.

v1.27.1: : Release scan on any default branch

Compare Source

The plugin release scan now works on catalogs whose default branch isn't main.

What's new
  • Default branch for the release scan. plugin-catalog-scan opens and reuses update pull requests on the catalog's default branch instead of assuming main. (#​133)

v1.27.0: : Shared plugin catalog workflows

Compare 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 workflows. plugin-catalog-validate checks every manifest against a shared schema and datumctl plugin index validate, and downloads changed archives to check their checksums. plugin-catalog-index rebuilds index.yaml through an auto-merging pull request, plugin-catalog-scan opens update pull requests for newer plugin releases daily, and plugin-catalog-health re-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)
  • Build timeout for publish-docker. The new timeout-minutes input, default 60, sets how long a build may run before GitHub cancels it. (#​130)
  • Required CI here. This repository's own pull requests now need its CI check to pass. (#​122)

[!NOTE]
The plugin catalog schema is stricter than the copies catalogs carried: download URLs must be HTTPS with a host, and platform selectors may only use os and arch labels. datumctl already refused the manifests this now rejects.


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.

@renovate renovate Bot added the renovate label Nov 17, 2026
@ecv
ecv requested a review from andrewb3000 November 17, 2026 18:02
andrewb3000
andrewb3000 previously approved these changes Nov 17, 2026

@andrewb3000 andrewb3000 left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Non-blocking

  • .github/workflows/publish.yaml:15: The reusable workflows are pinned to a tag, not a commit SHA, and publish passes secrets: inherit to 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 the uses: tags change. Triggers, permissions and secrets: inherit are the same as before. The one change these workflows pick up is the new 60-minute default timeout-minutes in publish-docker. CI passed.

@renovate
renovate Bot force-pushed the renovate/datum-cloud-actions-1.x branch from 67ab8f3 to 8eab82a Compare November 18, 2026 21:35
@renovate renovate Bot changed the title chore(deps): update datum-cloud/actions action to v1.28.0 chore(deps): update datum-cloud/actions action to v1.29.0 Nov 18, 2026
@renovate
renovate Bot requested a review from a team as a code owner November 18, 2026 21:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants