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!
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
You don't seem to have any Continuous Integration service set up!
Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the
service we're trying to provide down to a point where it is more or less meaningless.
This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:
* [Circle CI](https://circleci.com), [Semaphore ](https://semaphoreci.com) and [Travis-CI](https://travis-ci.com) are all excellent options.
* If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github.
* If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with `depfu/`.
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)
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!
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ webpack (4.38.0 → 4.39.1) · Repo
Release Notes
4.39.1
4.39.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 54 commits:
4.39.1
Merge pull request #9513 from webpack/bugfix/terminal-length
make status logging 1 char shorter
update examples
Merge pull request #9512 from webpack/bugfix/100-percent
fix 100% progress output
4.39.0
Merge pull request #9508 from webpack/deps/push
push latest version of dependencies to the end user
Merge pull request #9506 from webpack/logging/status
improve tests for different infrastructure logging levels
Merge pull request #9318 from jamesgeorge007/hotfix/ease-access-of-emitted-assets
add infrastructureLog hook to MulitCompiler
fix Progress and Stats Tests for colors and output
fix Compiler logging test
capture infrastructure log
extract LogTestPlugin
add getInfrastructureLogger to MultiCompiler
fix name for log hook
Colored console for node environment
add test cases
fix code and snapshots
fix: code lint
Minor fix
refactor
ease of access for contents of emitted assets
Merge pull request #9493 from Lyrkan/9491-fix-entrypoint-names
Merge pull request #9507 from webpack/dependabot/npm_and_yarn/types/node-10.14.14
Merge pull request #9503 from webpack/dependabot/npm_and_yarn/terser-webpack-plugin-1.4.1
chore(deps-dev): bump @types/node from 10.14.13 to 10.14.14
update snapshots
chore(deps): bump terser-webpack-plugin from 1.3.0 to 1.4.1
Merge pull request #9505 from webpack/dependabot/npm_and_yarn/webpack-sources-1.4.1
Merge pull request #9496 from BloodyEnterprise/master
chore(deps): bump webpack-sources from 1.3.0 to 1.4.1
Update lib/SystemMainTemplatePlugin.js
Merge pull request #9488 from webpack/dependabot/npm_and_yarn/eslint-plugin-jsdoc-15.8.0
Merge pull request #9497 from webpack/dependabot/npm_and_yarn/eslint-plugin-jest-22.14.1
chore(deps-dev): bump eslint-plugin-jest from 22.14.0 to 22.14.1
a test for resolve system module with evaluation name
Fix JSONP main template to allow currently forbidden chunk IDs (#9491)
fix system library module name
chore(deps-dev): bump eslint-plugin-jsdoc from 15.7.2 to 15.8.0
Merge pull request #9484 from webpack/dependabot/npm_and_yarn/simple-git-1.124.0
chore(deps-dev): bump simple-git from 1.122.0 to 1.124.0
Merge pull request #9481 from webpack/dependabot/npm_and_yarn/eslint-plugin-jest-22.14.0
Merge pull request #9430 from lingxiaoguang/master
Merge pull request #9454 from ijjk/escape-path-variables
chore(deps-dev): bump eslint-plugin-jest from 22.13.0 to 22.14.0
Merge pull request #9431 from mikispag/patch-1
Merge pull request #9459 from webpack/test/cleanup
remove jade dev dependency
avoid writing to stderr while testing
fix deprecation messages in test
👉 No CI detected
You don't seem to have any Continuous Integration service set up!
Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.
This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:
* [Circle CI](https://circleci.com), [Semaphore ](https://semaphoreci.com) and [Travis-CI](https://travis-ci.com) are all excellent options. * If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github. * If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with `depfu/`.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