Skip to content
This repository has been archived by the owner on Dec 8, 2021. It is now read-only.

Configure Renovate #254

Closed

Conversation

renovate-bot
Copy link

@renovate-bot renovate-bot commented Jul 25, 2019

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_spanner_deps.bzl (bazel)
  • ci/kokoro/Dockerfile.centos (dockerfile)
  • ci/kokoro/Dockerfile.fedora-install (dockerfile)
  • ci/kokoro/Dockerfile.fedora-libcxx-msan (dockerfile)
  • ci/kokoro/Dockerfile.ubuntu (dockerfile)
  • ci/kokoro/install/Dockerfile.fedora (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 3 Pull Requests:

chore(deps): update com_github_googleapis_google_cloud_cpp commit hash to dcd1f89
  • Schedule: "at any time"
  • Branch name: renovate/com_github_googleapis_google_cloud_cpp-digest
  • Upgrade com_github_googleapis_google_cloud_cpp to dcd1f897c4e2a63142cc8a708d96d245f36895bc
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

🚸 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 Reviewable

@googlebot googlebot added the cla: yes This human has signed the Contributor License Agreement. label Jul 25, 2019
@tmatsuo
Copy link
Contributor

tmatsuo commented Jul 25, 2019

Closing, see googleapis/google-cloud-cpp#2915 for rationale.

@tmatsuo tmatsuo closed this Jul 25, 2019
@forking-renovate
Copy link

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
cla: yes This human has signed the Contributor License Agreement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants