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 recreate
Recreates this PR, overwriting any edits that you've made to it
@depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@depfu close
Closes this PR and deletes the branch
@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 82.941% when pulling 2d707e37ce7f0dab639075d4a3a3a0b0af0c96e5 on depfu/update/npm/eslint-plugin-promise-5.1.0 into dbb73479190ee7f433655cba17848129088c1386 on master.
Coverage remained the same at 82.941% when pulling 2d707e37ce7f0dab639075d4a3a3a0b0af0c96e5 on depfu/update/npm/eslint-plugin-promise-5.1.0 into dbb73479190ee7f433655cba17848129088c1386 on master.
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ eslint-plugin-promise (^4.2.1 → ^5.1.0) · Repo · Changelog
Release Notes
5.1.0 (from changelog)
Does any of this look wrong? Please let us know.
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