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

chore(deps): update dependency mocha to v6 #350

Merged
merged 1 commit into from
Feb 21, 2019
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 19, 2019

This PR contains the following updates:

Package Type Update Change References
mocha devDependencies major ^5.0.4 -> ^6.0.0 homepage, source

Release Notes

mochajs/mocha

v6.0.0

Compare Source

🎉 Enhancements

🐛 Fixes

📖 Documentation

🔩 Other


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

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.

Googlers can find more info about SignCLA and this PR by following this link.

@codecov-io
Copy link

codecov-io commented Feb 19, 2019

Codecov Report

Merging #350 into master will decrease coverage by 0.01%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #350      +/-   ##
==========================================
- Coverage    95.3%   95.29%   -0.02%     
==========================================
  Files         124      124              
  Lines        8412     8390      -22     
  Branches      624      624              
==========================================
- Hits         8017     7995      -22     
  Misses        395      395
Impacted Files Coverage Δ
test/test-root-span.ts 100% <0%> (ø) ⬆️
test/test-tracer.ts 100% <0%> (ø) ⬆️
src/trace/model/tracer.ts 84.26% <0%> (ø) ⬆️
test/test-instana.ts 100% <0%> (ø) ⬆️
src/trace/model/root-span.ts 100% <0%> (ø) ⬆️
src/trace/model/types.ts 100% <0%> (ø) ⬆️
test/test-zipkin.ts 100% <0%> (ø) ⬆️
src/mongodb.ts 92.75% <0%> (ø) ⬆️
test/test-zpages.ts 99.62% <0%> (ø) ⬆️

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 2c56a2a...32fd279. Read the comment docs.

@renovate renovate bot force-pushed the renovate/mocha-6.x branch from 3b288ac to 8b803e7 Compare February 20, 2019 00:02
@mayurkale22 mayurkale22 self-requested a review February 20, 2019 19:06
@renovate renovate bot force-pushed the renovate/mocha-6.x branch 2 times, most recently from c12ce99 to 7cfab8c Compare February 21, 2019 00:53
@renovate renovate bot force-pushed the renovate/mocha-6.x branch from 7cfab8c to 32fd279 Compare February 21, 2019 19:26
@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.)

ℹ️ Googlers: Go here for more info.

@mayurkale22 mayurkale22 merged commit 622cc75 into master Feb 21, 2019
@mayurkale22 mayurkale22 deleted the renovate/mocha-6.x branch February 21, 2019 19:34
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.

4 participants