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

fix: update shipit-deploy's peerDependency to v4.1.0 #192

Merged
merged 1 commit into from
Apr 28, 2018

Conversation

smccollum-blurb
Copy link
Contributor

No description provided.

@codecov-io
Copy link

codecov-io commented Apr 27, 2018

Codecov Report

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

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #192   +/-   ##
=======================================
  Coverage   81.31%   81.31%           
=======================================
  Files          26       26           
  Lines         562      562           
  Branches      103       99    -4     
=======================================
  Hits          457      457           
- Misses         77       78    +1     
+ Partials       28       27    -1
Impacted Files Coverage Δ
packages/ssh-pool/src/commands/tar.js 65.21% <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 e57cf93...c99e1dd. Read the comment docs.

@gregberge gregberge merged commit 6f7b407 into shipitjs:master Apr 28, 2018
@gregberge
Copy link
Member

Thanks!

@richardkmichael
Copy link

@neoziro

I was upgrading from shipit v3 and encountered this unmet peerDep and started digging into node/npm to see if there was a node or package related problem during upgrade.

I notice from the history that you've release minor patches, e.g., 4.0.0, 4.0.1, 4.0.2 quickly. It's been a month since 4.1.0, so it seems stable, would you consider releasing 4.1.1 with this tiny fix? It might save people head scratching during upgrade. Cheers!

@gregberge
Copy link
Member

@richardkmichael deployed!

@alubbe
Copy link

alubbe commented May 30, 2018

Thanks, just ran into this :)

@richardkmichael
Copy link

@neoziro Thank you!

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

Successfully merging this pull request may close these issues.

5 participants