Support

Something failing?

Most problems have a known answer. Start here:

Troubleshooting explains the error messages Updatecli prints, from authentication to git push and manifest validation.
The FAQ covers the common questions, such as why a run seems to hang or why no pull request was opened.
Docker Hub rate limit explains the most frequent failure in CI.
Rerun with --debug. Several decisions, such as which token was used or why a target was skipped, are only logged at debug level.

GitHub Discussions for questions, ideas, and anything others might search for later.
Matrix for a quick chat. The same room is also reachable through Gitter.

Please be respectful and follow the Code of Conduct.

Search the existing issues first. If nothing matches, open a bug report and include:

The output of updatecli version.
The smallest manifest, and values file if you use one, that reproduces the problem.
The full output of the failing run, with --debug.

The pipeline graph, from:

updatecli manifest show --graph --graph-flavor mermaid --experimental --config <manifest>

Where it runs: locally, or in which CI system. If it fails in CI, say whether updatecli pipeline diff reproduces it locally.

Remove tokens and other secrets, such as UPDATECLI_GITHUB_TOKEN, from anything you paste.

Open a feature request and describe the update you are trying to automate. The use case matters more than a proposed implementation.

Do not report security vulnerabilities through public GitHub issues. Disclose them privately:

Contact the maintainers at for commercial help, such as integration work, migration, or training.

For anything else, see the Contact page. To help the project, by answering questions, triaging issues, or sponsoring it, see Contributing.