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 cancel merge
Cancels automatic merging of this PR
@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)
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 (5.92.0 → 5.92.1) · Repo
Release Notes
5.92.1
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 16 commits:
chore(release): 5.92.1
fix: error with contenthash and css experiment
test: added
chore(deps-dev): bump eslint-plugin-n from 17.8.1 to 17.9.0
chore(deps-dev): bump lint-staged from 15.2.5 to 15.2.7
chore(deps-dev): bump @eslint/js from 9.4.0 to 9.5.0
chore(deps): bump acorn from 8.11.3 to 8.12.0
chore(deps-dev): bump globals from 15.4.0 to 15.6.0
chore(deps-dev): bump @types/node from 20.14.2 to 20.14.5
chore(deps-dev): bump @types/node from 20.14.2 to 20.14.5
fix: error with contenthash and css experiment
chore(deps-dev): bump globals from 15.4.0 to 15.6.0
chore(deps): bump acorn from 8.11.3 to 8.12.0
chore(deps-dev): bump @eslint/js from 9.4.0 to 9.5.0
chore(deps-dev): bump eslint-plugin-n from 17.8.1 to 17.9.0
chore(deps-dev): bump lint-staged from 15.2.5 to 15.2.7
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