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

fix(deps): update dependency google-proto-files to ^0.18.0#239

Merged
mayurkale22 merged 1 commit intomasterfrom
renovate/google-proto-files-0.x
Dec 19, 2018
Merged

fix(deps): update dependency google-proto-files to ^0.18.0#239
mayurkale22 merged 1 commit intomasterfrom
renovate/google-proto-files-0.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Dec 19, 2018 •
edited
Loading

This PR contains the following updates:

Package Type Update Change References
google-proto-files dependencies minor ^0.16.1 -> ^0.18.0 source

Release Notes

googleapis/nodejs-proto-files

v0.18.0

Compare Source

11-09-2018 15:34 PST

This is a minor service release, with a few internal changes.

  • refactor: use walkdir instead of globby (#​109)
  • chore: drop contributors from multiple places (#​108)
  • chore: use latest npm on Windows (#​107)
  • refactor: convert to typescript (#​106)
  • refactor: use a src/ directory (#​105)
  • chore: update CircleCI config (#​104)
  • chore: include build in eslintignore (#​101)
  • chore(deps): update dependency eslint-plugin-node to v8 (#​97)
  • chore: update issue templates (#​96)
  • chore: remove old issue template (#​94)
  • build: run tests on node11 (#​93)
  • chores(build): do not collect sponge.xml from windows builds (#​92)
  • chores(build): run codecov on continuous builds (#​91)
  • chore: update new issue template (#​90)
  • build: fix codecov uploading on Kokoro (#​86)
  • build: automate library with synth.py (#​85)
  • chore(deps): update dependency sinon to v7 (#​84)

v0.17.0

Compare Source

Breaking changes
  • fix: drop support for node.js 4.x and 9.x (#​57)
Fixes
  • fix: update linking for samples (#​50)
Internal / Testing Changes
  • chore(deps): update dependency eslint-plugin-prettier to v3 (#​81)
  • test: remove appveyor config (#​80)
  • Enable prefer-const in the eslint config (#​79)
  • Enable no-var in eslint (#​78)
  • Update CI and fix tests (#​77)
  • Retry npm install in CI (#​76)
  • chore(deps): update dependency nyc to v13 (#​75)
  • chore(deps): update dependency eslint-config-prettier to v3 (#​74)
  • chore: ignore package-lock.json (#​73)
  • chore(deps): lock file maintenance (#​72)
  • chore: use let and const (#​71)
  • chore: update renovate config (#​69)
  • remove that whitespace (#​68)
  • chore(deps): lock file maintenance (#​67)
  • chore: move mocha options to mocha.opts (#​66)
  • chore(deps): update dependency eslint-plugin-node to v7 (#​62)
  • chore(deps): lock file maintenance (#​65)
  • chore(deps): lock file maintenance (#​61)
  • chore(deps): lock file maintenance (#​60)
  • chore(deps): lock file maintenance (#​59)
  • chore(deps): lock file maintenance (#​58)
  • fix: remove unused packages (#​56)
  • chore(deps): lock file maintenance (#​55)
  • chore(deps): lock file maintenance (#​54)
  • chore(deps): lock file maintenance (#​53)
  • chore(deps): lock file maintenance (#​52)
  • Configure Renovate (#​48)
  • chore(package): update eslint to version 5.0.0 (#​49)
  • refactor: drop repo-tool as an exec wrapper (#​51)

Renovate configuration

📅 Schedule: "after 9am and before 3pm" (UTC).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever PR is stale, or if you modify the PR title to begin with "rebase!".

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

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

@googlebot
Copy link
Copy Markdown

googlebot commented Dec 19, 2018

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.

@codecov-io
Copy link
Copy Markdown

codecov-io commented Dec 19, 2018 •
edited
Loading

Codecov Report

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

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #239   +/-   ##
=======================================
  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 542c4ec...725b716. Read the comment docs.

@renovate renovate bot changed the title Update dependency google-proto-files to ^0.18.0 fix(deps): update dependency google-proto-files to ^0.18.0 Dec 19, 2018
@renovate renovate bot force-pushed the renovate/google-proto-files-0.x branch from 8af5f7c to 5f0d3f5 Compare December 19, 2018 04:54
@mayurkale22 mayurkale22 self-requested a review December 19, 2018 07:33
@googlebot
Copy link
Copy Markdown

googlebot commented Dec 19, 2018

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.)

@googlebot googlebot removed the cla: no label Dec 19, 2018
@renovate renovate bot force-pushed the renovate/google-proto-files-0.x branch from 5f0d3f5 to 725b716 Compare December 19, 2018 19:50
@googlebot
Copy link
Copy Markdown

googlebot commented Dec 19, 2018

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.

@googlebot
Copy link
Copy Markdown

googlebot commented Dec 19, 2018

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.)

@googlebot googlebot removed the cla: no label Dec 19, 2018
@renovate renovate bot force-pushed the renovate/google-proto-files-0.x branch from 725b716 to 5fceadc Compare December 19, 2018 20:15
@googlebot
Copy link
Copy Markdown

googlebot commented Dec 19, 2018

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.

@googlebot
Copy link
Copy Markdown

googlebot commented Dec 19, 2018

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.)

@googlebot googlebot removed the cla: no label Dec 19, 2018
@mayurkale22 mayurkale22 merged commit 607edc5 into master Dec 19, 2018
@mayurkale22 mayurkale22 deleted the renovate/google-proto-files-0.x branch December 19, 2018 20:22
@mayurkale22 mayurkale22 mentioned this pull request Feb 12, 2019
Merged
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Reviewers

1 more reviewer

@mayurkale22 mayurkale22 mayurkale22 approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

cla: yes

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@googlebot @codecov-io @mayurkale22 @renovate-bot