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 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 7a4322c5c67b5a5cf2a783d7ae73f6280b10faac on depfu/update/npm/assetgraph-6.0.0 into 2acae6eb7c3300c25cc7c802207755fb56934abe 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?
✳️ assetgraph (^5.2.0 → ^6.0.0) · Repo
Commits
See the full diff on Github. The new version differs by 4 commits:
6.0.0
Merge pull request #1035 from assetgraph/feature/tryJsdomForXmlAgain
Merge pull request #1041 from assetgraph/tech/removeSubsetFonts
Found a way to update the message of jsdom's DOMException
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