This repository was archived by the owner on May 7, 2018. It is now read-only.
Configure Renovate #5
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
renovate bot force-pushed the renovate/configure branch from 20f786f to e2bf8fa Compare 
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
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.
With your current configuration, renovate will initially create the following Pull Requests:
renovate/angulardevDependenciesfrom1.3.0-rc.3to1.3.0renovate/@types/jasmine-2.xdevDependenciesfrom2.5.38to2.5.53renovate/jasmine-spec-reporter-4.xdevDependenciesfrom~4.1.1to~4.2.0renovate/lock-file-maintenanceSometimes 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.