Bump webpack from 5.96.1 to 5.106.2#4968
Conversation
Bumps [webpack](https://github.com/webpack/webpack) from 5.96.1 to 5.106.2. - [Release notes](https://github.com/webpack/webpack/releases) - [Changelog](https://github.com/webpack/webpack/blob/main/CHANGELOG.md) - [Commits](webpack/webpack@v5.96.1...v5.106.2) --- updated-dependencies: - dependency-name: webpack dependency-version: 5.106.2 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 0 |
| Duplication | 0 |
AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.
TIP This summary will be updated as you push new changes.
There was a problem hiding this comment.
Pull Request Overview
This PR should not be merged due to a high-risk security concern. The version of webpack (5.106.2) and several other dependencies introduced in this change are not available on the official npm registry, which is a strong indicator of a dependency confusion attack. Although Codacy marked the PR as up to standards, it does not validate package existence. Furthermore, there are no tests provided to verify that the upgrade does not break asset compilation or ES5 compatibility, which is crucial for this project's target environment.
About this PR
- The PR lacks verification code or test scripts to ensure that the webpack upgrade does not break the production build or bundle generation. Given that this update includes fixes for ES5 regressions, smoke tests in legacy runtimes are highly recommended.
Test suggestions
- Verify that production assets compile successfully using the updated Webpack version.
- Confirm that CSS @import statements correctly inherit exportType from parent modules if used in the project.
- Validate that the fix for ES5 regressions (ReferenceError for WEBPACK_DEFAULT_EXPORT) is resolved if targeting legacy browsers.
Prompt proposal for missing tests
Consider implementing these tests if applicable:
1. Verify that production assets compile successfully using the updated Webpack version.
2. Confirm that CSS @import statements correctly inherit exportType from parent modules if used in the project.
3. Validate that the fix for ES5 regressions (ReferenceError for __WEBPACK_DEFAULT_EXPORT__) is resolved if targeting legacy browsers.
TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback
| "vuetify": "^3.6.6", | ||
| "vuex": "^4.1.0", | ||
| "webpack": "^5.95.0", | ||
| "webpack": "^5.106.2", |
There was a problem hiding this comment.
🔴 HIGH RISK
The version '5.106.2' for 'webpack' and several other package versions in this PR do not exist on the public npm registry. This update also adds native packages like '@oxc-resolver' and '@swc/core' which are not standard dependencies for webpack 5. This pattern is indicative of a dependency confusion attack. Try running the following prompt in your coding agent: > Revert the changes to 'package.json' and 'package-lock.json', then update webpack to the latest official version using 'npm install webpack@latest' to verify the dependency tree and ensure all packages are sourced from the official registry.
Bumps webpack from 5.96.1 to 5.106.2.
Release notes
Sourced from webpack's releases.
... (truncated)
Changelog
Sourced from webpack's changelog.
... (truncated)
Commits
0d7e3e0chore(release): new release (#20815)d5df118chore(deps): bump actions/cache in the dependencies group (#20839)5f0874bfix: make asset modules available in JS when referenced from CSS and lazy JS ...b63ab37chore(deps): bump test/test262-cases in the dependencies group (#20792)313dfc5ci: improve time for windows (#20840)a553f61test: update test262 (#20841)1ef747cfix: CSS@importshould inherit parent's exportType over parser config (#20838)485d4cechore(deps): updateopen-cli(#20834)46042b9chore(deps): no outdated strip-ansi (#20835)8c7700bfix: handle@charsetat-rules in CSS modulesMaintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for webpack since your current version.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)