Skip to main content
The bump command runs Renovate in Docker for a sitectl project. Use it to update image tags, GitHub Actions, and application dependencies without editing dependency files by hand. Compose templates pin direct images as tag@sha256:digest. Renovate keeps that human-readable version and immutable digest together; do not remove the digest to make an update easier. A Dockerfile base-tag change can also change the upstream application release for OJS, Omeka, or ArchivesSpace, while Composer changes control Drupal, ISLE, and WordPress application code. Review those updates as application releases, including backups, smoke tests, and migration gates. Pick exactly one update level. Levels are cumulative: --minor includes patch updates, and --major includes minor and patch updates.
With --context, sitectl uses that local context’s project directory:
Without --context, it uses the current working directory:
Use --dry-run to inspect Renovate’s candidate updates without creating branches or pull requests:
By default, all update scopes are enabled. Turn scopes off when you want a narrower update:
For non-dry runs, Renovate needs a GitHub token. Set RENOVATE_TOKEN or GITHUB_TOKEN in the shell before running the command.

​
Reference

Run Renovate in Docker for the selected repository. With --context, sitectl uses that local context’s project directory. Without --context, sitectl uses the current working directory. Dry runs analyze the local checkout and print Renovate’s candidate updates. Non-dry runs infer the GitHub repository from origin and create or update Renovate branches and PRs.