Read-only mirror of https://github.com/gisktzh/renovate — Kanton Zürich. Issues & pull requests at the source.
  • JavaScript 65.7%
  • Shell 34.3%
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
2025-12-16 14:01:54 +00:00
.github/workflows Use original keep-alive action again. 2025-12-16 14:01:54 +00:00
.husky GB3-1662: Added a pre-commit-hook to automatically validate any config change. 2024-11-18 17:12:22 +01:00
.gitignore GB3-1662: Added a pre-commit-hook to automatically validate any config change. 2024-11-18 17:12:22 +01:00
LICENSE Initial commit 2024-11-06 16:32:03 +01:00
package-lock.json GB3-1662: Added a pre-commit-hook to automatically validate any config change. 2024-11-18 17:12:22 +01:00
package.json GB3-1662: Added a pre-commit-hook to automatically validate any config change. 2024-11-18 17:12:22 +01:00
prepare.mjs GB3-1662: Added a pre-commit-hook to automatically validate any config change. 2024-11-18 17:12:22 +01:00
README.md Adjust readme 2025-04-22 16:32:49 +02:00
renovate-config.js Update renovate-config.js 2024-11-26 08:40:36 +01:00

Introduction

This repository contains all configuration files and Github actions to run the Renovate bot periodically to update the dependencies in all configured repositories.

Caution

The scheduling mechanism is rather wonky and has some intricacies to keep in mind.

  • The scheduled workflow is disabled if there is no action (e.g. commits) to the repository within 60 days. An email will be sent to the last committer of the given workflow some time before. The workflows can be reenabled in the details of the given workflow.
  • Important: If the last person to change the workflow file is removed from the repository (be it by access removal, or also by changing their email address), the workflows will silently no longer be executed. This can only be reactivated by changing the - cron: part in the workflow, and yes, it needs a changed schedule, otherwise it will not be picked up.
  • The supplied renovate_token can produce issues as well, and also rais authentication errors. If so, a new token has to be created; and this might also be connected to the aforementioned user changes.

Getting Started

What is Renovate?

Renovate automates dependency updates. Multi-platform and multi-language.

This bot frequently updates the dependencies of all linked repositories. It then creates PRs or automatically merges new versions of those dependencies depending on the corresponding configuration. Each repository can have its own configuration.

Adding a new repository to be automatically updated by Renovate

  1. Modify renovate-config.json file in this repository. In this file there is an array repositories. Append your repository at the end of the existing array.
    Use the syntax 'PROJECT_NAME/REPOSITORY_NAME'
    Example: 'gisktzh/gb3-web_ui'
  2. Push your commit
  3. (Optional) Run the Github action manually to immediately run Renovate

Now, if the bot is running for the first time after adding your repository it will scan the repository for the renovate.json configuration. It will automatically create a pull request containing an initial configuration if none is found. You have to approve and merge this PR manually before Renovate will start updating your dependencies.

Note: To enable automerge to work the following repository settings must be set:

  • Settings -> General -> Pull Requests -> Allow auto-merge Loading
  • The account that runs Renovate must have the permission to bypass required reviews
  • (Optional) Settings -> Rules -> Rulesets -> Branch Rules -> Require merge queue
    Don't forget to add on: (...) merge_group: to your GitHub action configuration if you enable the merge queue

How does it work?

There is an Github action based on .github/workflows/main.yml that runs the Renovate bot daily. The bot will operate according to the configuration written in renovate-config.js file. This file contains a list of all repositories that will be checked/updated automatically.

Each checked repository contains its own rules on how to process dependency updates. The goal should be that the updates run mostly silent and the project should be as up-to-date as possible.

More information: https://docs.renovatebot.com/modules/platform/github/