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.
All Depfu comment commands
@depfu rebase
Rebases against your default branch and redoes this update
@depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@depfu reopen
Restores the branch and reopens this PR (if it's closed)
@depfu pause
Ignores all future updates for this dependency and closes this PR
@depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)
Coverage remained the same at 80.952% when pulling a40d2d5d2d3b75ce86a00bfb684e4d5eb9acff30 on depfu/update/npm/memoizeasync-1.1.0 into 4e4126e5f42e8f7ce459531e8a9d51ee1c7661da 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?
✳️ memoizeasync ( → 1.1.0) · Repo
Commits
See the full diff on Github. The new version differs by 2 commits:
1.1.0
Bypass the memoization if the argumentsStringifier returns false
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
.All Depfu comment commands