Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.
Coverage remained the same at 91.728% when pulling 136599e7b011c8dcfc0da4c11ee3f6fc900615f0 on depfu/update/npm/magicpen-5.12.0 into 91348df96d93004e9a15c32e61e33312010248f3 on master.
Coverage remained the same at 91.728% when pulling 136599e7b011c8dcfc0da4c11ee3f6fc900615f0 on depfu/update/npm/magicpen-5.12.0 into 91348df96d93004e9a15c32e61e33312010248f3 on master.
Coverage remained the same at 91.728% when pulling 136599e7b011c8dcfc0da4c11ee3f6fc900615f0 on depfu/update/npm/magicpen-5.12.0 into 91348df96d93004e9a15c32e61e33312010248f3 on master.
We've upgraded a dependency and all tests pass. \o/
You should probably take a good look at this before merging this pull request, of course.
What changed?
✳️ magicpen ( → 5.12.0) · Repo
Commits
See the full diff on Github. The new version differs by 2 commits:
5.12.0
Change behavior of MagicPen#clone so it's more compatible with expect.child() (#24)
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.