🚨 [security] Update axios 1.3.4 → 1.6.1 (minor) #439
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![depfu[bot]](https://avatars.githubusercontent.com/in/715?s=60&v=4){kind=small}
|
Sorry, but the merge failed with:
|
|
Closed in favor of #485. |
|
Closed in favor of #485. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🚨 Your current dependencies have known security vulnerabilities 🚨
This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ axios (1.3.4 → 1.6.1) · Repo · Changelog
Security Advisories 🚨
🚨 Axios Cross-Site Request Forgery Vulnerability
Release Notes
1.6.1
1.6.0
1.5.1
1.5.0
1.4.0
1.3.6
1.3.5
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 47 commits:
chore(ci): fix publish action content permission; (#6061)chore(release): v1.6.1 (#6060)chore(ci): Publish to NPM with provenance (#5835)chore(ci): added labeling and notification for published PRs; (#6059)fix(formdata): fixed content-type header normalization for non-standard browser environments; (#6056)fix(platform): fixed emulated browser detection in node.js environment; (#6055)chore(release): v1.6.0 (#6031)chore(ci): fix release-it arg; (#6032)fix(CSRF): fixed CSRF vulnerability CVE-2023-45857 (#6028)chore(tests): fixed tests to pass in node v19 and v20 with `keep-alive` enabled; (#6021)fix(dns): fixed lookup function decorator to work properly in node v20; (#6011)chore(docs): added AxiosHeaders docs; (#5932)fix(types): fix AxiosHeaders types; (#5931)chore(docs): update readme.md (#5889)chore(release): v1.5.1 (#5920)fix(adapters): improved adapters loading logic to have clear error messages; (#5919)fix(formdata): fixed automatic addition of the `Content-Type` header for FormData in non-browser environments; (#5917)fix(headers): allow `content-encoding` header to handle case-insensitive values (#5890) (#5892)docs(paramsSerializer config within request config): update documentation for paramsSerializerChange isNaN to Number.isNaNdocs: fix CommonJS usage notefix(types): removed duplicated codechore(release): v1.5.0 (#5838)feat(export): export adapters without `unsafe` prefix (#5839)docs: linting documentation notes (#5791)feat: export getAdapter function (#5324)fix(adapter): make adapter loading error more clear by using platform-specific adapters explicitly (#5837)fix(dns): fixed `cacheable-lookup` integration; (#5836)fix(headers): fixed common Content-Type header merging; (#5832)fix(headers): added support for setting header names that overlap with class methods; (#5831)docs: Add axios error type definitions in README.MD (#5788)chore(release): v1.4.0 (#5683)chore(utils): refactored isAsyncFn util to avoid inlining additional Babel helpers to the build; (#5684)refactor: remove deprecated url-search-params polyfill for URLSearchParams (#5670)feat(types): export `AxiosHeaderValue` type. (#5525)feat(dns): added support for a custom lookup function; (#5339)perf(merge-config): optimize mergeConfig performance by avoiding duplicate key visits; (#5679)fix(formdata): add `multipart/form-data` content type for FormData payload on custom client environments; (#5678)fix(package): export package internals with unsafe path prefix; (#5677)chore(release): v1.3.6 (#5666)chore(template): improve issue template; (#5665)fix(utils): make isFormData detection logic stricter to avoid unnecessary calling of the `toString` method on the target; (#5661)chore(ci): use package-lock in test & build github actions; (#5663)fix(types): added transport to RawAxiosRequestConfig (#5445)chore(release): v1.3.5 (#5634)fix(params): re-added the ability to set the function as `paramsSerializer` config; (#5633)fix(headers): fixed isValidHeaderName to support full list of allowed characters; (#5584)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