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-sources (1.4.3 → 2.2.0) · Repo
Release Notes
2.2.0
2.1.1
2.1.0
2.0.1
2.0.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 55 commits:
2.2.0
Merge pull request #96 from webpack/performance/hash-cache
add caching for updateHash
2.1.1
Merge pull request #95 from webpack/performance/minimized
fix a performance problem with minimized files
2.1.0
Merge pull request #94 from webpack/bugfix/null-map
Instead of return an empty SourceMap in some cases, return null
2.0.1
Merge pull request #91 from webpack/bugfix/non-mapped-source
add workaround for bug in source-map
2.0.0
2.0.0-beta.10
Merge pull request #87 from webpack/cached/lazy-source
allow to use a lazy function as original source for CachedSource
2.0.0-beta.9
Merge pull request #86 from webpack/feature/compat-source
add missing documentation and test for CompatSource
Merge pull request #85 from webpack/infrastructure
test on node.js 14 too
change var to const
switch to jest
upgrade dependencies
update deps in range
Merge pull request #84 from webpack/feature/compat-source
tests should use public API
cache for linting
add CompatSource
2.0.0-beta.8
Merge pull request #78 from webpack/bugfix/no-map
fix crash when Source in CachedSource returns null map
2.0.0-beta.7
Merge pull request #77 from webpack/perf/source-map-cache
avoid strings in CachedSource `map()` cache
2.0.0-beta.6
Merge pull request #76 from webpack/perf/utf-8
Performance improvements
2.0.0-beta.5
Merge pull request #74 from webpack/deps/min-node
Merge pull request #73 from webpack/bugfix/update-hash
Merge pull request #72 from webpack/dependabot/npm_and_yarn/js-yaml-3.13.1
Merge pull request #71 from webpack/dependabot/npm_and_yarn/lodash-4.17.15
Merge pull request #70 from webpack/dependabot/npm_and_yarn/eslint-utils-1.4.3
increase min node.js version to 10
fix updateHash for Sources
Bump js-yaml from 3.12.1 to 3.13.1
Bump lodash from 4.17.11 to 4.17.15
Bump eslint-utils from 1.3.1 to 1.4.3
Merge pull request #46 from webpack/next
2.0.0-beta.4
Merge pull request #69 from webpack/compat/no-buffer
ensure compat with older webpack-sources versions which have no .buffer() function
2.0.0-beta.3
Merge tag 'v1.4.3' into next
👉 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.