Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: update execa dependency to 2.1.0 #147

Merged
merged 1 commit into from Oct 10, 2019

Conversation

Trott
Copy link
Contributor

@Trott Trott commented Oct 10, 2019

This PR contains:

  • bugfix
  • feature
  • refactor
  • tests
  • documentation
  • metadata

Breaking Changes?

  • yes
  • no

If yes, please describe the breakage.

Please Describe Your Changes

Update execa dependency to 2.1.0 in package-lock.json. Without this
change, tests will fail when run with Node.js 13.x-pre and may fail when
13.0.0 is released in 13 days.

Refs: sindresorhus/execa#370

Update execa dependency to 2.1.0 in package-lock.json. Without this
change, tests will fail when run with Node.js 13.x-pre and may fail when
13.0.0 is released in 13 days.
@codecov-io
Copy link

codecov-io commented Oct 10, 2019

Codecov Report

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

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #147   +/-   ##
=======================================
  Coverage   97.24%   97.24%           
=======================================
  Files           1        1           
  Lines         145      145           
=======================================
  Hits          141      141           
  Misses          4        4

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 d221504...15f0d7b. Read the comment docs.

@shellscape
Copy link
Collaborator

Thanks for this PR 🍺

@shellscape shellscape merged commit 264e15a into mafintosh:master Oct 10, 2019
@Trott
Copy link
Contributor Author

Trott commented Oct 10, 2019

I know it's just a test fix, but any chance I can persuade you to publish a new release? There seem to be some legitimate bug fixes since the last release, so it wouldn't be a complete no-change release for end users. This particular fix will help Node.js's ecosystem-testing tool CITGM, which downloads a tarball of the latest release and runs tests. So CITGM won't use this fix until it's part of a release.

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

Successfully merging this pull request may close these issues.

None yet

3 participants