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.0) · 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 57 commits:
5.37.0
Merge pull request #13334 from webpack/bugfix/depend-on-runtime-async-chunks
Merge pull request #13318 from webpack/dependabot/npm_and_yarn/webpack-cli-4.7.0
Merge pull request #13272 from webpack/dependabot/npm_and_yarn/babel/core-7.14.0
Merge pull request #13338 from webpack/dependabot/npm_and_yarn/eslint-plugin-jsdoc-33.3.0
Merge pull request #13260 from webpack/dependabot/add-v2-config-file
chore(deps-dev): bump eslint-plugin-jsdoc from 33.0.0 to 33.3.0
deduplicate
chore(deps-dev): bump @babel/core from 7.13.16 to 7.14.0
Merge pull request #13298 from webpack/dependabot/npm_and_yarn/fork-ts-checker-webpack-plugin-6.2.6
Merge pull request #13304 from webpack/dependabot/npm_and_yarn/acorn-8.2.4
remove ignores, increase limit
Merge pull request #13305 from webpack/dependabot/npm_and_yarn/types/node-15.0.2
Merge pull request #13326 from webpack/dependabot/npm_and_yarn/date-fns-2.21.3
Merge pull request #13331 from dhruvit-r/bugfix/fs-call-signatures
fix too large runtime chunks when using dependOn
make errors nullable for call signatures of filesystem types
Merge pull request #9856 from koto/tt-integration
normalize output.trustedTypes to an object
fix author
rename to CreateScriptUrlRuntimeModule to have same name as RuntimeGlobal
improve test cases
generate shorter code
better types for normalized options
use createScriptUrl only when needed
rename createScriptURL to createScriptUrl
disable trustedTypes by default
Merge pull request #13325 from webpack/dependabot/npm_and_yarn/hosted-git-info-2.8.9
chore(deps-dev): bump date-fns from 2.21.1 to 2.21.3
chore(deps): [security] bump hosted-git-info from 2.8.8 to 2.8.9
Merge pull request #13164 from johnnyreilly/master
rename validate function to avoid conflict
getOptions returns OptionsType
Merge branch 'master' into johnnyreilly/master
upgrade tooling and update types.d.ts
Merge pull request #13315 from webpack/dependabot/npm_and_yarn/core-js-3.12.0
Skip using Trusted Types checks if trustedTypesPolicyName is empty.
chore(deps-dev): bump webpack-cli from 4.6.0 to 4.7.0
chore(deps-dev): bump core-js from 3.10.2 to 3.12.0
chore(deps-dev): bump @types/node from 15.0.1 to 15.0.2
Only expose createScriptURL function from Trusted Types policy
Split use-trusted-types into two test cases
Added Trusted Types support for importScripts() in workers.
Update snapshots
Make Worker transformation compatible with Trusted Types
Move Trusted Types policy into TrustedTypesRuntimeModule
Added the Trusted Types logic.
Removed a deprecated createURL function reference.
Integrate Trusted Types in webpack
chore(deps): bump acorn from 8.2.2 to 8.2.4
chore(deps-dev): bump fork-ts-checker-webpack-plugin from 6.2.5 to 6.2.6
Merge pull request #13283 from webpack/dependabot/npm_and_yarn/browserslist-4.16.6
Merge pull request #13281 from webpack/dependabot/npm_and_yarn/mini-css-extract-plugin-1.6.0
Merge pull request #13282 from webpack/bugfix/log-info
chore(deps): bump browserslist from 4.16.5 to 4.16.6
make ESM tracking info message less verbose
chore(deps-dev): bump mini-css-extract-plugin from 1.5.1 to 1.6.0
👉 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.