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 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)
Go to the Depfu Dashboard to see the state of your dependencies and to customize how Depfu works.
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?
✳️ webpack (4.42.0 → 5.37.1) · Repo
Release Notes
Too many releases to show here. View the full release notes.
Commits
See the full diff on Github. The new version differs by 52 commits:
5.37.1
Merge pull request #13296 from bolariin/issue-13284
Merge pull request #13401 from webpack/pascal-readonly-array
Merge pull request #13399 from webpack/bugfix/resume-watching
Merge pull request #13400 from webpack/bugfix/use-after-free
Merge pull request #13397 from webpack/dependabot/npm_and_yarn/babel/core-7.14.3
fix type error
Merge branch 'master' into pascal-readonly-array
fixes #13330
update typings
fix collecting of changed files and aggregating when suspending
improve test case
Merge pull request #13395 from webpack/bugfix/respect-multi-compiler-config-invalidate
Update snaphots
chore(deps-dev): bump @babel/core from 7.14.2 to 7.14.3
add test cases from #12897 and #12881
Merge branch 'master' into issue-13284
fix schema for absolute conditions and add test cases
Merge pull request #13347 from webpack/dependabot/npm_and_yarn/lint-staged-11.0.0
Merge pull request #13393 from webpack/dependabot/npm_and_yarn/fork-ts-checker-webpack-plugin-6.2.9
Merge pull request #13368 from snitin315/docs-update
Merge pull request #13383 from webpack/dependabot/npm_and_yarn/simple-git-2.39.0
Merge pull request #13374 from webpack/dependabot/npm_and_yarn/babel/core-7.14.2
Merge pull request #13394 from webpack/dependabot/npm_and_yarn/types/node-15.3.0
Merge pull request #13340 from webpack/bugfix/coverage
respect multi compiler `dependencies` and `parallelism` when using `invalidate`
chore(deps-dev): bump @types/node from 15.0.3 to 15.3.0
chore(deps-dev): bump fork-ts-checker-webpack-plugin from 6.2.7 to 6.2.9
chore(deps-dev): bump simple-git from 2.38.1 to 2.39.0
Merge pull request #13376 from webpack/dependabot/npm_and_yarn/types/node-15.0.3
chore(deps-dev): bump @types/node from 15.0.2 to 15.0.3
chore(deps-dev): bump @babel/core from 7.14.0 to 7.14.2
fix coverage for child process
fix lint
docs: remove traceur-loader
Merge pull request #13348 from webpack/dependabot/npm_and_yarn/core-js-3.12.1
Merge pull request #13363 from webpack/dependabot/npm_and_yarn/fork-ts-checker-webpack-plugin-6.2.7
deduplicate
chore(deps-dev): bump fork-ts-checker-webpack-plugin from 6.2.6 to 6.2.7
Merge pull request #13344 from webpack/dependabot/npm_and_yarn/typescript-4.2.4
Merge pull request #13352 from webpack/dependabot/npm_and_yarn/eslint-7.26.0
Merge pull request #13319 from webpack/dependabot/npm_and_yarn/handlebars-4.7.7
Merge pull request #13343 from webpack/dependabot/npm_and_yarn/prettier-2.3.0
pretty files
Merge remote-tracking branch 'origin/master' into dependabot/npm_and_yarn/prettier-2.3.0
update declarations
Merge pull request #13345 from webpack/dependabot/npm_and_yarn/simple-git-2.38.1
Merge pull request #13346 from webpack/dependabot/npm_and_yarn/webpack-cli-4.7.0
Merge pull request #13359 from webpack/dependabot/npm_and_yarn/mini-svg-data-uri-1.3.3
Merge pull request #13360 from webpack/dependabot/npm_and_yarn/enhanced-resolve-5.8.2
chore(deps): bump enhanced-resolve from 5.8.0 to 5.8.2
chore(deps-dev): bump mini-svg-data-uri from 1.2.3 to 1.3.3
👉 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
Go to the Depfu Dashboard to see the state of your dependencies and to customize how Depfu works.