Configure Renovate

[renovate-bot]

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

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

---

Detected Package Files

• ci/test-install/WORKSPACE (bazel)
• bazel/google_cloud_cpp_deps.bzl (bazel)
• ci/benchmarks/Dockerfile (dockerfile)
• ci/kokoro/Dockerfile.refdocs (dockerfile)
• ci/kokoro/docker/Dockerfile.centos (dockerfile)
• ci/kokoro/docker/Dockerfile.fedora (dockerfile)
• ci/kokoro/docker/Dockerfile.fedora-install (dockerfile)
• ci/kokoro/docker/Dockerfile.ubuntu (dockerfile)
• ci/kokoro/docker/Dockerfile.ubuntu-install (dockerfile)
• ci/kokoro/docker/Dockerfile.ubuntu-trusty (dockerfile)
• ci/kokoro/install/Dockerfile.centos (dockerfile)
• ci/kokoro/install/Dockerfile.debian (dockerfile)
• ci/kokoro/install/Dockerfile.fedora (dockerfile)
• ci/kokoro/install/Dockerfile.opensuse (dockerfile)
• ci/kokoro/install/Dockerfile.opensuse-leap (dockerfile)
• ci/kokoro/install/Dockerfile.ubuntu (dockerfile)
• ci/kokoro/install/Dockerfile.ubuntu-trusty (dockerfile)
• ci/kokoro/install/Dockerfile.ubuntu-xenial (dockerfile)
• ci/kokoro/readme/Dockerfile.centos (dockerfile)
• ci/kokoro/readme/Dockerfile.debian (dockerfile)
• ci/kokoro/readme/Dockerfile.fedora (dockerfile)
• ci/kokoro/readme/Dockerfile.opensuse (dockerfile)
• ci/kokoro/readme/Dockerfile.opensuse-leap (dockerfile)
• ci/kokoro/readme/Dockerfile.ubuntu (dockerfile)
• ci/kokoro/readme/Dockerfile.ubuntu-trusty (dockerfile)
• ci/kokoro/readme/Dockerfile.ubuntu-xenial (dockerfile)

Configuration Summary

Based on the default config's 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, vendor 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 open PRs at any time
• Group known monorepo packages together
• Use curated list of recommended non-monorepo package groupings

🔡 Would you like to change the way Renovate is upgrading your dependencies? Simply edit the renovate.json in this branch with your custom config and the list of Pull Requests in the "What to Expect" section below will be updated the next time Renovate runs.

---

What to Expect

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

chore(deps): update com_google_googleapis commit hash to ec379e9

• Schedule: "at any time"
• Branch name: renovate/com_google_googleapis-digest
• Upgrade com_google_googleapis to ec379e9da970e32e911020c794ecfee2656f87d5

chore(deps): update com_google_googletest commit hash to b77e5c7

• Schedule: "at any time"
• Branch name: renovate/com_google_googletest-digest
• Upgrade com_google_googletest to b77e5c76252bac322bb82c5b444f050bd0d92451

chore(deps): update dependency com_github_googleapis_google_cloud_cpp to v0.11.0

• Schedule: "at any time"
• Branch name: renovate/com_github_googleapis_google_cloud_cpp-0.x
• Upgrade com_github_googleapis_google_cloud_cpp to v0.11.0

chore(deps): update dependency com_github_grpc_grpc to v1.22.0

• Schedule: "at any time"
• Branch name: renovate/com_github_grpc_grpc-1.x
• Upgrade com_github_grpc_grpc to v1.22.0

🚸 Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or spam the project. See docs for prhourlylimit for details.

---

❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section.
If you need any further assistance then you can also request help here.

---

This PR has been generated by Renovate Bot. View repository job log here.

---

This change is 

[tmatsuo]

Automated dependency update is a nice concept, but it doesn't seem renovate detects CMakeLists.txt and files under cmake, which are actually holds some dependencies and versions.

I would close this for now, and revisit when I know it works for CMake based projects.

[forking-renovate]

Renovate is disabled

Renovate is disabled due to lack of config. If you wish to reenable it, you can either (a) commit a config file to your base branch, or (b) rename this closed PR to trigger a replacement onboarding PR.

[ghost]

I would close this for now, and revisit when I know it works for CMake based projects.

How will this interact with #2802? If we are using find_package that means there will be nothing to "update" per se, except in the cases where we change the minimum required versions (if/when that is necessary).

But I can see this still being useful for Bazel.

[tmatsuo]

@remyabel Oh that's a good point. Once we only use find_package, there's nothing. I guess it is still useful to update some dependency versions in the Dockerfile?

[coryan]

We should move the discussion to a bug.

I think having something automatically propose updates sounds good.

As to the lack of support for CMake, maybe we could have a simple file that both CMake and Bazel (and Docker!) can read with the version numbers / commit-sha / tarball hashes?