This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.
After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.
Let us know if you have any questions. Thanks so much for giving Depfu a try!
We've updated a dependency and here is what you need to know:
name
version specification
old version
new version
uglifier
>= 1.3.0
4.1.13
4.1.15
You should probably take a good look at the info here and the test results before merging this pull request, of course.
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.
Welcome to Depfu 👋
This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.
After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.
Let us know if you have any questions. Thanks so much for giving Depfu a try!
We've updated a dependency and here is what you need to know:
You should probably take a good look at the info here and the test results before merging this pull request, of course.
What changed?
✳️ uglifier (4.1.13 → 4.1.15) · Repo · Changelog
Commits
See the full diff on Github. The new version differs by 6 commits:
Bump version to 4.1.15
Update UglifyJS to 3.4.4
Bump version to 4.1.14
Disable testing on JRuby 1.9 mode
Update UglifyJS to 3.4.3
Skip updating uglifyjs-harmony
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
.