This is an onboarding PR to help you understand and configure Renovate before any regular Pull Requests begin. Once you close this Pull Request, Renovate will begin keeping your dependencies up-to-date via automated Pull Requests.
If you have any questions, try reading our Getting Started Configuring Renovate page first, or feel free to ask the app author @rarkins a question in a comment below.
Configuration Summary
Based on the currently configured presets, Renovate will:
Start dependency updates once this Configure Renovate PR is merged or closed
Separate major versions of dependencies into individual branches/PRs
Combine any patch and minor upgrades together into same branch/PR
Upgrade to unstable versions only if the existing version is unstable
Raise PRs immediately (after branch is created)
Use renovate/ as prefix for all branch names
If semantic commits detected, use fix(deps): for dependencies and chore(deps): for all others
Disable automerging feature - wait for humans to merge all PRs
Keep Dockerfile FROM sources updated
With your current configuration, renovate will initially create the following Pull Requests:
Pull Requests (1)
chore(deps): pin docker digests
Branch name: renovate/pin-docker-digests
Pins alpine in Dockerfile to sha256:129a7f8c0fae8c3251a8df9370577d9d6b96ca6f1bea33ada677bc153d7b1867
Pins alpine in Dockerfile to sha256:129a7f8c0fae8c3251a8df9370577d9d6b96ca6f1bea33ada677bc153d7b1867
Pins alpine in Dockerfile to sha256:129a7f8c0fae8c3251a8df9370577d9d6b96ca6f1bea33ada677bc153d7b1867
Sometimes you may see multiple options for the same dependency (e.g. pinning in one branch and upgrading in another). This is expected and allows you the flexibility to choose which to merge first. Once you merge any PR, others will be updated or removed the next time Renovate runs.
Would you like to change the way Renovate is upgrading your dependencies? Simply edit the renovate.json in this branch and this Pull Request description will be updated the next time Renovate runs.
Our Configuration Docs should be helpful if you wish to modify any behaviour.
Don't want a renovate.json file?
You are not required to merge this Pull Request - Renovate will begin even if this "Configure Renovate" PR is closed unmerged and without a renovate.json file. However, it's recommended that you add configuration to your repository to ensure behaviour matches what you see described here.
Alternatively, you can add the same configuration settings into a "renovate" section of your package.json file(s) in this branch and delete the renovate.json from this PR. If you make these configuration changes in this branch then the results will be described in this PR after the next time Renovate runs.
Want to start over?
If you'd like Renovate to recreate this "Configure Renovate" PR from scratch - for example if your base branch has had substantial changes - then you need to:
(IMPORTANT) Rename this PR to something else, e.g. "Configure Renovate - old"
Close the PR and delete the branch
If later on you ever wish to reconfigure Renovate then you can use this same trick of renaming the PR, but you'll also need to delete any renovate.json file too. You should then get a new "Configure Renovate" PR like this.
Welcome to Renovate!
This is an onboarding PR to help you understand and configure Renovate before any regular Pull Requests begin. Once you close this Pull Request, Renovate will begin keeping your dependencies up-to-date via automated Pull Requests.
If you have any questions, try reading our Getting Started Configuring Renovate page first, or feel free to ask the app author @rarkins a question in a comment below.
Configuration Summary
Based on the currently configured presets, Renovate will:
renovate/as prefix for all branch namesfix(deps):for dependencies andchore(deps):for all othersWith your current configuration, renovate will initially create the following Pull Requests:
renovate/pin-docker-digestsDockerfiletosha256:129a7f8c0fae8c3251a8df9370577d9d6b96ca6f1bea33ada677bc153d7b1867Dockerfiletosha256:129a7f8c0fae8c3251a8df9370577d9d6b96ca6f1bea33ada677bc153d7b1867Dockerfiletosha256:129a7f8c0fae8c3251a8df9370577d9d6b96ca6f1bea33ada677bc153d7b1867Sometimes you may see multiple options for the same dependency (e.g. pinning in one branch and upgrading in another). This is expected and allows you the flexibility to choose which to merge first. Once you merge any PR, others will be updated or removed the next time Renovate runs.
Would you like to change the way Renovate is upgrading your dependencies? Simply edit the
renovate.jsonin this branch and this Pull Request description will be updated the next time Renovate runs.Our Configuration Docs should be helpful if you wish to modify any behaviour.
Don't want a
renovate.jsonfile?You are not required to merge this Pull Request - Renovate will begin even if this "Configure Renovate" PR is closed unmerged and without a
renovate.jsonfile. However, it's recommended that you add configuration to your repository to ensure behaviour matches what you see described here.Alternatively, you can add the same configuration settings into a "renovate" section of your
package.jsonfile(s) in this branch and delete therenovate.jsonfrom this PR. If you make these configuration changes in this branch then the results will be described in this PR after the next time Renovate runs.Want to start over?
If you'd like Renovate to recreate this "Configure Renovate" PR from scratch - for example if your base branch has had substantial changes - then you need to:
If later on you ever wish to reconfigure Renovate then you can use this same trick of renaming the PR, but you'll also need to delete any
renovate.jsonfile too. You should then get a new "Configure Renovate" PR like this.