Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configure Renovate #2

Closed
wants to merge 1 commit into from
Closed

Configure Renovate #2

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jul 20, 2017

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:

Pull Requests (4)
Update dependency isarray to version ^0.0.1
  • Branch name: renovate/isarray-0.x
  • Upgrades isarray in dependencies from ^0.0.0 to ^0.0.1
Update dependency isarray to version ^1.0.0
  • Branch name: renovate/isarray-1.x
  • Upgrades isarray in dependencies from ^0.0.0 to ^1.0.0
Update dependency isarray to version ^2.0.0
  • Branch name: renovate/isarray-2.x
  • Upgrades isarray in dependencies from ^0.0.0 to ^2.0.0
Pin dependency assertit to version 0.1.0
  • Branch name: renovate/pin-dependencies
  • Pins assertit in devDependencies from ^0.1.0 to 0.1.0

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.

@coveralls
Copy link

coveralls commented Jul 20, 2017

Coverage Status

Coverage remained the same at 100.0% when pulling 68988f2 on renovate/configure into 5583f18 on master.

2 similar comments
@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 68988f2 on renovate/configure into 5583f18 on master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 68988f2 on renovate/configure into 5583f18 on master.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants