Configure Renovate

[renovate]

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

Renovate will begin keeping your dependencies up-to-date only once you merge this Pull Request.
If you close this Pull Request unmerged, then Renovate will be disabled.

If you have any questions, try reading our Docs, particularly the Getting Started section.
You can post questions in our Config Help repository or @ the app author @rarkins in this PR and he'll probably see it.

---

Detected Package Files

• package.json (npm)
• samples/package.json (npm)
• samples/startup-script/package.json (npm)

Configuration Summary

Based on the currently configured presets, Renovate will:

• Start dependency updates only once this Configure Renovate PR is merged
• Separate major versions of dependencies into individual branches/PRs
• Do not separate patch and minor upgrades into separate PRs for the same dependency
• 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 semantic commit type fix for dependencies and chore for all others
• Keep existing branches updated even when not scheduled
• Disable automerging feature - wait for humans to merge all PRs
• Ignore node_modules, bower_components, and various test/tests directories
• Update existing lock files only when package.json is modified
• Autodetect whether to pin dependencies or maintain ranges
• Rate limit PR creation to a maximum of two per hour
• Limit to maximum 20 concurrent Renovate PRs at any time
• Run Renovate on following schedule: after 10pm,before 5am

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. Try to use Config Presets (the extends array) when possible rather than raw config, as then this PR will be able to more accurately describe your settings.

---

What to Expect

With your current configuration, Renovate will create 4 Pull Requests:

1. chore(deps): update dependency @google-cloud/nodejs-repo-tools to v2.3.0

• Schedule: ["after 10pm","before 5am"]
• Branch name: renovate/google-cloud-nodejs-repo-tools-2.x
• Upgrades @google-cloud/nodejs-repo-tools in devDependencies from 2.2.3 to 2.3.0

2. chore(deps): update dependency ava to v0.25.0

• Schedule: ["after 10pm","before 5am"]
• Branch name: renovate/ava-0.x
• Upgrades ava in devDependencies from 0.23.0 to 0.25.0

3. fix(deps): update dependency @google-cloud/common to ^0.20.0

• Schedule: ["after 10pm","before 5am"]
• Branch name: renovate/google-cloud-common-0.x
• Upgrades @google-cloud/common in dependencies from ^0.17.0 to ^0.20.0

4. chore(deps): lock file maintenance

• Schedule: ["before 10am on tuesday"]
• Branch name: renovate/lock-file-maintenance
• Regenerates lock file to use latest dependency versions

---

---

This PR has been generated by Renovate Bot.

[codecov]

Codecov Report

Merging #112 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master   #112   +/-   ##
=====================================
  Coverage     100%   100%           
=====================================
  Files          19     19           
  Lines        1581   1581           
=====================================
  Hits         1581   1581

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 92367e7...91a2e47. Read the comment docs.

[forking-renovate]

Renovate is disabled

Renovate is disabled because there is no Renovate configuration file. To enable Renovate, you can either (a) change this PR's title to get a new onboarding PR, and merge the new onboarding PR, or (b) create a Renovate config file, and commit that file to your base branch.