You can trigger the pipeline and open the PR from your local machine as needed.
The updatecli configuration uses a modular structure with shared values:
values/scms.yaml- GitHub authentication and repository settingsvalues/artifacts.yaml- Shared OCI artifacts and Helm charts definitions (used by all pipelines)values/update-deps-pr-values.yaml- PR configuration for weekly dependency updatesvalues/release-pr-values.yaml- PR configuration for release PRs
This structure ensures a single source of truth for artifact definitions while allowing different PR configurations per pipeline.
Change updatecli/values/scms.yaml as needed to target forks.
$ cd kubewarden-controller/
$ export UPDATECLI_GITHUB_TOKEN=<your token>
$ export UPDATECLI_GITHUB_OWNER=kubewarden
$ updatecli compose apply --file updatecli/open-release-pr.yaml
(...)
Run Summary
===========
Pipeline(s) run:
* Changed: 1
* Failed: 0
* Skipped: 0
* Succeeded: 0
* Total: 1
One action to follow up:
* https://github.com/kubewarden/kubewarden-controller/pull/XXXAll dependency updates are consolidated into a single weekly workflow.
Runs weekly (Monday 3:30 AM) via .github/workflows/update-dependencies.yaml using update-deps.yaml.
Updates the following dependencies:
- Rust toolchain version
- Policy image tags in Helm chart values
- Policy-reporter and openreports chart versions
- Kuberlr-kubectl image version
- Hauler manifest with all component versions
For manual runs of all dependency updates:
$ export UPDATECLI_GITHUB_TOKEN=<your token>
$ export UPDATECLI_GITHUB_OWNER=kubewarden
$ updatecli compose diff --file updatecli/update-deps.yamlTo add a new OCI artifact or Helm chart:
- Edit
updatecli/values/artifacts.yaml - Add the artifact to the
ociArtifactsorhelmChartslist - Test with
updatecli compose diffbefore committing