18.0.0 (2019-05-25)
v18 includes a major refactor/rewrite of two key components of Renovate, laying the groundwork for some great future capabilities.
First of all, our GitHub platform code has been converted to use git for file operations rather than GitHub's API. Essentially, we perform a shallow clone of repos each run to get access to the full file system instead of plucking files one by one from the API. gitFs has actually been in use for GitHub in the Renovate App for more than a month and serving more than 60,000 repositories, so we're pretty satisfied with its stability.
If you run your own GitHub Renovate Bot then make sure to read the breaking changes notes about configuring gitAuthor or enabling user:email access in the bot's token.
With this change for GitHub, that now means that all platforms (GitHub, GitLab, Bitbucket Cloud, Bitbucket Server, Azure Devops) now run on gitFs, so we can actually "deprecate" the term gitFs and assume it in all cases.
Next, we rewrote the internals of "hostRules" to allow greater flexibility, e.g.
- Being able to define different rules based on a full match baseUrl
- Defining rules per domain name
This allows for things like having separate authentication for different URLs on the same server, as well as configuring a single authentication for domains such a "docker.io" or "github.com".
We have attempted to find and migrate over all existing ("legacy") hostRules configurations but still please take care to test out that any existing authentication still works for you when you update to v18.
Features
BREAKING CHANGES
- github: GitHub bot admins should either configure gitAuthor in their config or generate a new token with “user:email” permissions.