Skip to content
This repository has been archived by the owner on Oct 3, 2023. It is now read-only.

Configure Renovate #233

Merged
merged 1 commit into from
Dec 19, 2018
Merged

Configure Renovate #233

merged 1 commit into from
Dec 19, 2018

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 13, 2018

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

  • .circleci/config.yml (circleci)
  • package.json (npm)
  • packages/opencensus-core/package.json (npm)
  • packages/opencensus-example-automatic-tracing/package.json (npm)
  • packages/opencensus-exporter-instana/package.json (npm)
  • packages/opencensus-exporter-jaeger/package.json (npm)
  • packages/opencensus-exporter-ocagent/package.json (npm)
  • packages/opencensus-exporter-prometheus/package.json (npm)
  • packages/opencensus-exporter-stackdriver/package.json (npm)
  • packages/opencensus-exporter-zipkin/package.json (npm)
  • packages/opencensus-exporter-zpages/package.json (npm)
  • packages/opencensus-instrumentation-all/package.json (npm)
  • packages/opencensus-instrumentation-grpc/package.json (npm)
  • packages/opencensus-instrumentation-http/package.json (npm)
  • packages/opencensus-instrumentation-http2/package.json (npm)
  • packages/opencensus-instrumentation-https/package.json (npm)
  • packages/opencensus-instrumentation-mongodb/package.json (npm)
  • packages/opencensus-nodejs/package.json (npm)
  • packages/opencensus-propagation-b3/package.json (npm)
  • packages/opencensus-propagation-jaeger/package.json (npm)
  • packages/opencensus-propagation-stackdriver/package.json (npm)
  • packages/opencensus-propagation-tracecontext/package.json (npm)

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 concurrent Renovate 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 23 Pull Requests:

Pin dependencies
Update dependency @​types/ejs to v2.6.1
  • Schedule: "at any time"
  • Branch name: renovate/ejs-2.x
  • Upgrade @types/ejs to 2.6.1
Update dependency @​types/express to v4.16.0
  • Schedule: "at any time"
  • Branch name: renovate/express-4.x
  • Upgrade @types/express to 4.16.0
Update dependency @​types/lodash to v4.14.119
  • Schedule: "at any time"
  • Branch name: renovate/lodash-4.x
  • Upgrade @types/lodash to 4.14.119
Update dependency @​types/mocha
  • Schedule: "at any time"
  • Branch name: renovate/mocha-5.x
  • Upgrade @types/mocha to 5.2.5
  • Upgrade mocha to 5.2.0
Update dependency @​types/mongodb to v3.1.17
  • Schedule: "at any time"
  • Branch name: renovate/mongodb-3.x
  • Upgrade @types/mongodb to 3.1.17
  • Upgrade mongodb to 3.1.10
Update dependency @​types/nock to v9.3.0
  • Schedule: "at any time"
  • Branch name: renovate/nock-9.x
  • Upgrade @types/nock to 9.3.0
  • Upgrade nock to 9.6.1
Update dependency @​types/node to v10.12.15
  • Schedule: "at any time"
  • Branch name: renovate/node-10.x
  • Upgrade @types/node to 10.12.15
Update dependency @​types/uuid to v3.4.4
  • Schedule: "at any time"
  • Branch name: renovate/uuid-3.x
  • Upgrade @types/uuid to 3.4.4
Update dependency google-proto-files to ^0.18.0
  • Schedule: "at any time"
  • Branch name: renovate/google-proto-files-0.x
  • Upgrade google-proto-files to ^0.18.0
Update dependency grpc to ~1.17.0
  • Schedule: "at any time"
  • Branch name: renovate/grpc-1.x
  • Upgrade grpc to ~1.17.0
Update dependency gts to v0.9.0
  • Schedule: "at any time"
  • Branch name: renovate/gts-0.x
  • Upgrade gts to 0.9.0
Update dependency jaeger-client to ~3.13.0
  • Schedule: "at any time"
  • Branch name: renovate/jaeger-client-3.x
  • Upgrade jaeger-client to ~3.13.0
Update dependency nodemon to v1.18.9
  • Schedule: "at any time"
  • Branch name: renovate/nodemon-1.x
  • Upgrade nodemon to 1.18.9
Update dependency nyc to v11.9.0
  • Schedule: "at any time"
  • Branch name: renovate/nyc-11.x
  • Upgrade nyc to 11.9.0
Update dependency protobufjs to v6.8.8
  • Schedule: "at any time"
  • Branch name: renovate/protobufjs-6.x
  • Upgrade protobufjs to 6.8.8
Update dependency typescript to v2.9.2
  • Schedule: "at any time"
  • Branch name: renovate/typescript-2.x
  • Upgrade typescript to 2.9.2
Update dependency google-auth-library to v2
  • Schedule: "at any time"
  • Branch name: renovate/google-auth-library-2.x
  • Upgrade google-auth-library to ^2.0.0
Update dependency googleapis to v36
  • Schedule: "at any time"
  • Branch name: renovate/googleapis-36.x
  • Upgrade googleapis to 36.0.0
Update dependency lerna to v3
  • Schedule: "at any time"
  • Branch name: renovate/lerna-3.x
  • Upgrade lerna to 3.6.0
Update dependency nock to v10
  • Schedule: "at any time"
  • Branch name: renovate/nock-10.x
  • Upgrade nock to 10.0.4
Update dependency nyc to v13
  • Schedule: "at any time"
  • Branch name: renovate/nyc-13.x
  • Upgrade nyc to 13.1.0
Update dependency typescript to v3
  • Schedule: "at any time"
  • Branch name: renovate/typescript-3.x
  • Upgrade typescript to 3.2.2

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


❓ If you have any questions, try reading the Docs, particularly the Getting Started section.
Also, you can post questions about your config in Renovate's Config Help repository.


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

@googlebot
Copy link

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of all the commit author(s), set the cla label to yes (if enabled on your project), and then merge this pull request when appropriate.

Copy link
Contributor

@justindsmith justindsmith left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

With your current configuration, Renovate will create 23 Pull Requests
Woah. Is there a way we can update those in one PR ourselves so that we start with a "clean slate"?

@mayurkale22
Copy link
Member

Is there a way we can update those in one PR ourselves so that we start with a "clean slate"?

Definately feasible but have to spend some time (~2 hours) to manually update and test all out-of-date dependencies.

@renovate renovate bot force-pushed the renovate/configure branch 2 times, most recently from b677cc2 to 652f65e Compare December 14, 2018 21:03
@codecov-io
Copy link

codecov-io commented Dec 14, 2018

Codecov Report

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

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #233   +/-   ##
=======================================
  Coverage   95.41%   95.41%           
=======================================
  Files          58       58           
  Lines        3841     3841           
  Branches      276      276           
=======================================
  Hits         3665     3665           
  Misses        176      176

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 b572e5e...ef16aa9. Read the comment docs.

Copy link
Contributor

@justindsmith justindsmith left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My concern around a bunch of PRs is definitely a nit. Long term this will be nice to have 👍

@googlebot
Copy link

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

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

Successfully merging this pull request may close these issues.

None yet

5 participants