You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This upgrade covers a wide range of versions from December 2024 to May 2026. [7] While not a major version bump, version 1.16.0 introduces several behavioral changes and security hardening that could impact specific use cases. [5]
Notable Changes:
Enforced Size Limits: The fetch adapter now enforces maxBodyLength and maxContentLength. Previously, these limits were ignored, so requests that were unknowingly sending oversized bodies may now fail. [5]
Proxy Header Behavior: Proxy requests will now correctly preserve a user-supplied Host header, which was previously being overwritten. This fixes buggy behavior but could impact applications that relied on the old logic. [5]
URL-Embedded Authentication: Basic authentication credentials embedded in URLs are now correctly URL-decoded. [5]
Security Hardening: The release includes numerous security-adjacent fixes, such as stricter URL validation and stripping sensitive headers on cross-origin redirects. [3, 5]
Recommendation:
Verify application behavior related to file uploads (especially when using the fetch adapter), requests made through proxies, and authentication provided directly in the URL.
This is a minor version upgrade within the v10 series. The release notes for this range primarily consist of enhancements, bug fixes, and dependency updates. [11] No breaking API changes or significant behavioral shifts are documented for the v10.x line. Major breaking changes, such as dropping support for older Node.js versions, were reserved for the v11 and v12 releases. [8, 9]
Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This file contains hidden or 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
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.
Snyk has created this PR to fix 4 vulnerabilities in the npm dependencies of this project.
Snyk changed the following file(s):
package.jsonVulnerabilities that will be fixed with an upgrade:
SNYK-JS-AXIOS-17172532
SNYK-JS-AXIOS-17172681
SNYK-JS-AXIOS-17172751
SNYK-JS-JSYAML-17342520
Breaking Change Risk
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Regular Expression Denial of Service (ReDoS)
🦉 Allocation of Resources Without Limits or Throttling
This change is