chore(deps): bump axios from 0.21.0 to 0.32.0 in /docs/multiple-tests/pattern-vulnerability-high/src/javascript#302
Conversation
Bumps [axios](https://github.com/axios/axios) from 0.21.0 to 0.32.0. - [Release notes](https://github.com/axios/axios/releases) - [Changelog](https://github.com/axios/axios/blob/v1.x/CHANGELOG.md) - [Commits](axios/axios@v0.21.0...v0.32.0) --- updated-dependencies: - dependency-name: axios dependency-version: 0.32.0 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
Up to standards ✅🟢 Issues
|
There was a problem hiding this comment.
Pull Request Overview
This pull request updates the axios dependency to address several high-risk security vulnerabilities, including prototype pollution, Denial of Service via recursion, and credential leaks in logs. While essential for security, this version change introduces significant breaking changes. Most notably, merged configuration and header objects now use null prototypes, which can cause failures in logic that relies on the inheritance of Object.prototype methods (such as hasOwnProperty). Additionally, the removal of 'dist/' artifacts and Bower support may impact existing build pipelines or deployment configurations. Given the absence of new tests or smoke checks, manual verification of these breaking changes is required before merging.
About this PR
- This axios update introduces a breaking change where merged configuration and header objects are created with a null prototype. This will cause code such as
config.hasOwnProperty('prop')to throw an error. Furthermore, the 'dist/' folder has been removed; ensure that no part of the build or deployment process relies on these artifacts.
Test suggestions
- Verify that the application's handling of axios config and headers is compatible with the new null-prototype merged objects (breaking change).
- Ensure the build or runtime environment does not depend on the removed 'dist/' artifacts or Bower support (breaking change).
Prompt proposal for missing tests
Consider implementing these tests if applicable:
1. Verify that the application's handling of axios config and headers is compatible with the new null-prototype merged objects (breaking change).
2. Ensure the build or runtime environment does not depend on the removed 'dist/' artifacts or Bower support (breaking change).
TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback
Bumps axios from 0.21.0 to 0.32.0.
Release notes
Sourced from axios's releases.
... (truncated)
Commits
8db2d44chore: bump version to v0.32.0 (#10840)2af6116chore: backport fixes from the v1x branch (#10838)a589dc5chore: bump version to v0.31.1 (#10766)b0c632ffix: backport security issues (#10764)b52187ffix: harden config merging (#10752)e3ddeb4fix: header security issues (#10750)f4f2d76chore: stop committing dist/ and remove bower (#10747)1f2f644chore: add CODEOWNERS (#10740)44bca90fix: improve regex in AxiosURLSearchParams (#10737)4c4f07ffix: form data recursion (#10728)Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for axios 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)You can disable automated security fix PRs for this repo from the Security Alerts page.