Shared GitHub Actions and reusable workflows for Minekube repositories.
bump-go-module.yml updates one Go module in the caller repository, runs local
tests, optionally dispatches the caller repository's full CI workflow, opens or
updates a rolling pull request, and requests auto-merge.
jobs:
bump:
uses: minekube/actions/.github/workflows/bump-go-module.yml@v1
permissions:
contents: read
id-token: write
with:
module: go.minekube.com/gate
version: ${{ inputs.version }}
base-ref: main
branch: automation/update-gate
pr-title: "fix(deps): update Gate to ${{ inputs.version }}"
commit-message: "fix(deps): update gate to ${{ inputs.version }}"
ci-workflow: fly.yml
secrets: inheritdispatch-workflow.yml dispatches a workflow in another repository with a
GitHub App installation token.
jobs:
dispatch:
uses: minekube/actions/.github/workflows/dispatch-workflow.yml@v1
permissions:
contents: read
id-token: write
with:
target-repository: gate
target-workflow: bump-managed-dependency.yml
target-ref: master
inputs-json: |
{
"dependency": "vialite",
"version": "${{ needs.release-please.outputs.tag_name }}"
}
secrets: inheritBoth workflows run on direct GH-hosted runners (ubuntu-24.04). The Akua
runner control plane (runner-control-plane.robinbraemer.workers.dev) was
removed after it went down on 2026-08-17 and starved every release-cascade
run; no Minekube workflow may depend on it. Caller workflows therefore do
NOT need id-token: write for the control plane.
The release-cascade GitHub App credential is an explicit workflow_call
input by default, with a vars.RELEASE_CASCADE_APP_CLIENT_ID fallback for
existing v1 callers:
Required caller configuration:
secrets.RELEASE_CASCADE_APP_PRIVATE_KEYsecrets: inheriton the calling job- GitHub App installation on every repository that the reusable workflow needs to write to or dispatch into
Use the major tag @v1 from callers. Move the v1 tag when changing the shared
workflow implementation in a backward-compatible way.