Skip to content

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

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

chore(deps): update datum-cloud/actions action to v1.18.0#234
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/datum-cloud-actions-1.x

Conversation

@renovate

@renovate renovate Bot commented May 21, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
datum-cloud/actions action minor v1.14.0v1.18.0

Release Notes

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

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

Full Changelog: datum-cloud/actions@v1.14.0...v1.15.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.

@renovate renovate Bot requested a review from a team as a code owner May 21, 2026 19:07
@renovate renovate Bot requested a review from slindseysr May 21, 2026 19:07
@renovate renovate Bot force-pushed the renovate/datum-cloud-actions-1.x branch from addff3e to e9f8892 Compare May 28, 2026 21:55
@renovate renovate Bot force-pushed the renovate/datum-cloud-actions-1.x branch from e9f8892 to b59864d Compare June 11, 2026 16:01
@renovate renovate Bot changed the title chore(deps): update datum-cloud/actions action to v1.15.0 chore(deps): update datum-cloud/actions action to v1.16.0 Jun 18, 2026
@renovate renovate Bot force-pushed the renovate/datum-cloud-actions-1.x branch from b59864d to 40a0061 Compare June 18, 2026 02:53
@renovate renovate Bot force-pushed the renovate/datum-cloud-actions-1.x branch from 40a0061 to a08014a Compare July 1, 2026 08:55
@renovate renovate Bot changed the title chore(deps): update datum-cloud/actions action to v1.16.0 chore(deps): update datum-cloud/actions action to v1.17.0 Jul 1, 2026
@renovate renovate Bot changed the title chore(deps): update datum-cloud/actions action to v1.17.0 chore(deps): update datum-cloud/actions action to v1.18.0 Jul 1, 2026
@renovate renovate Bot force-pushed the renovate/datum-cloud-actions-1.x branch from a08014a to d7a0e95 Compare July 1, 2026 18:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants