chore(deps): bump axios from 1.13.5 to 1.15.0 in /apps/Standalone

[dependabot]

Bumps axios from 1.13.5 to 1.15.0.

Release notes

Sourced from axios's releases.

v1.15.0

This release delivers two critical security patches, adds runtime support for Deno and Bun, and includes significant CI hardening, documentation improvements, and routine dependency updates.

⚠️ Important Changes

• Deprecation: url.parse() usage has been replaced to address Node.js deprecation warnings. If you are on a recent version of Node.js, this resolves console warnings you may have been seeing. (#10625)

🔒 Security Fixes

• Proxy Handling: Fixed a no_proxy hostname normalisation bypass that could lead to Server-Side Request Forgery (SSRF). (#10661)
• Header Injection: Fixed an unrestricted cloud metadata exfiltration vulnerability via a header injection chain. (#10660)

🚀 New Features

• Runtime Support: Added compatibility checks and documentation for Deno and Bun environments. (#10652, #10653)

🔧 Maintenance & Chores

• CI Security: Hardened workflow permissions to least privilege, added the zizmor security scanner, pinned action versions, and gated npm publishing with OIDC and environment protection. (#10618, #10619, #10627, #10637, #10666)
• Dependencies: Bumped serialize-javascript, handlebars, picomatch, vite, and denoland/setup-deno to latest versions. Added a 7-day Dependabot cooldown period. (#10574, #10572, #10568, #10663, #10664, #10665, #10669, #10670, #10616)
• Documentation: Unified docs, improved beforeRedirect credential leakage example, clarified withCredentials/withXSRFToken behaviour, HTTP/2 support notes, async/await timeout error handling, header case preservation, and various typo fixes. (#10649, #10624, #7452, #7471, #10654, #10644, #10589)
• Housekeeping: Removed stale files, regenerated lockfile, and updated sponsor scripts and blocks. (#10584, #10650, #10582, #10640, #10659, #10668)
• Tests: Added regression coverage for urlencoded Content-Type casing. (#10573)

🌟 New Contributors

We are thrilled to welcome our new contributors. Thank you for helping improve Axios:

• @​raashish1601 (#10573)
• @​Kilros0817 (#10625)
• @​ashstrc (#10624)
• @​Abhi3975 (#10589)
• @​theamodhshetty (#7452)

v1.14.0

This release focuses on compatibility fixes, adapter stability improvements, and test/tooling modernisation.

⚠️ Important Changes

• Breaking Changes: None identified in this release.
• Action Required: If you rely on env-based proxy behaviour or CJS resolution edge-cases, validate your integration after upgrade (notably proxy-from-env v2 alignment and main entry compatibility fix).

🚀 New Features

• Runtime Features: No new end-user features were introduced in this release.
• Test Coverage Expansion: Added broader smoke/module test coverage for CJS and ESM package usage. (#7510)

🐛 Bug Fixes

• Headers: Trim trailing CRLF in normalised header values. (#7456)
• HTTP/2: Close detached HTTP/2 sessions on timeout to avoid lingering sessions. (#7457)
• Fetch Adapter: Cancel ReadableStream created during request-stream capability probing to prevent async resource leaks. (#7515)
• Proxy Handling: Fixed env proxy behavior with proxy-from-env v2 usage. (#7499)

... (truncated)

Changelog

Sourced from axios's changelog.

v1.15.0 — April 7, 2026

This release delivers two critical security patches targeting header injection and SSRF via proxy bypass, adds official runtime support for Deno and Bun, and includes significant CI security hardening.

🔒 Security Fixes

• Header Injection (CRLF): Rejects any header value containing \r or \n characters to block CRLF injection chains that could be used to exfiltrate cloud metadata (IMDS). Behavior change: headers with CR/LF now throw "Invalid character in header content". (#10660)

• SSRF via no_proxy Bypass: Introduces a shouldBypassProxy helper that normalises hostnames (strips trailing dots, handles bracketed IPv6) before evaluating no_proxy/NO_PROXY rules, closing a gap that could cause loopback or internal hosts to be inadvertently proxied. (#10661)

🚀 New Features

• Deno & Bun Runtime Support: Added full smoke test suites for Deno and Bun, with CI workflows that run both runtimes before any release is cut. (#10652)

🐛 Bug Fixes

• Node.js v22 Compatibility: Replaced deprecated url.parse() calls with the WHATWG URL/URLSearchParams API across examples, sandbox, and tests, eliminating DEP0169 deprecation warnings on Node.js v22+. (#10625)

🔧 Maintenance & Chores

• CI Security Hardening: Added zizmor GitHub Actions security scanner; switched npm publish to OIDC Trusted Publishing (removing the long-lived NODE_AUTH_TOKEN); pinned all action references to full commit SHAs; narrowed workflow permissions to least privilege; gated the publish step behind a dedicated npm-publish environment; and blocked the sponsor-block workflow from running on forks. (#10618, #10619, #10627, #10637, #10641, #10666)

• Docs: Clarified HTTP/2 support and the unsupported httpVersion option; added documentation for header case preservation; improved the beforeRedirect example to prevent accidental credential leakage. (#10644, #10654, #10624)

• Dependencies: Bumped picomatch, handlebars, serialize-javascript, vite (×3), denoland/setup-deno, and 4 additional dev dependencies to latest versions. (#10564, #10565, #10567, #10568, #10572, #10574, #10663, #10664, #10665, #10669, #10670)

🌟 New Contributors

We are thrilled to welcome our new contributors. Thank you for helping improve axios:

• @​Kilros0817 (#10625)
• @​shaanmajid (#10616, #10617, #10618, #10619, #10637, #10641, #10666)
• @​ashstrc (#10624, #10644)
• @​Abhi3975 (#10589)
• @​raashish1601 (#10573)

Full Changelog

---

v1.14.0 — March 27, 2026

This release fixes a security vulnerability in the formidable dependency, resolves a CommonJS compatibility regression, hardens proxy and HTTP/2 handling, and modernises the build and test toolchain.

🔒 Security Fixes

• Formidable Vulnerability: Upgraded formidable from v2 to v3 to address a reported arbitrary-file vulnerability. Updated test server and assertions to align with the v3 API. (#7533)

🐛 Bug Fixes

... (truncated)

Commits

• 772a4e5 chore(release): prepare release 1.15.0 (#10671)
• 4b07137 chore(deps-dev): bump vite from 8.0.0 to 8.0.5 in /tests/smoke/esm (#10663)
• 51e57b3 chore(deps-dev): bump vite from 8.0.2 to 8.0.5 (#10664)
• fba1a77 chore(deps-dev): bump vite from 8.0.2 to 8.0.5 in /tests/module/esm (#10665)
• 0bf6e28 chore(deps): bump denoland/setup-deno in the github-actions group (#10669)
• 8107157 chore(deps-dev): bump the development_dependencies group with 4 updates (#10670)
• e66530e ci: require npm-publish environment for releases (#10666)
• 49f23cb chore(sponsor): update sponsor block (#10668)
• 3631854 fix: unrestricted cloud metadata exfiltration via header injection chain (#10...
• fb3befb fix: no_proxy hostname normalization bypass leads to ssrf (#10661)
• Additional commits viewable in compare view

Install script changes

This version modifies prepare script that runs during installation. Review the package contents before updating.

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 rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will 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 version will 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 dependency will 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.

[github-actions]

📊 Coverage check completed. See workflow run for details.

[github-actions]

🤖 AI PR Validation Report

PR Review Results

Thank you for your submission! Here's detailed feedback on your PR title and body compliance:

✅ PR Title

• Current: chore(deps): bump axios from 1.13.5 to 1.15.0 in /apps/Standalone
• Issue: None — title is clear and follows conventional commit style and scope.
• Recommendation: Keep as-is. Good job including the package, version bump and path.

---

❌ Commit Type

• Missing selection from the required PR body template.
• Commit type should be selected in the PR body. For this change, select: chore (dependency update).
• Note: Only one commit type should be selected. If multiple types apply, leave a comment explaining why.

---

❌ Risk Level

• No risk level selected in the PR body and there is no risk:* label on the PR.
• Assessment: Based on the code diff (single dependency bump in apps/Standalone/package.json), this is a dependency upgrade of axios from 1.13.5 to 1.15.0 which includes security fixes (CRLF header validation and SSRF/no_proxy fixes) and CI/docs maintenance. While the change is scoped and small, it can have behavioral changes (headers with CRLF now throw, proxy/no_proxy normalization), so the advised risk is: risk:medium.
• Recommendation: Add the label risk:medium to the PR and select the matching Risk Level checkbox in the PR body. If your team expects this to be low risk, include justification (e.g. "app only uses axios via our wrapper which sanitizes headers and does not set proxy env vars").

---

❌ What & Why

• Current: (Missing — PR body does not follow the required template fields)
• Issue: The repo requires a short "What & Why" section describing what is changed and why. Dependabot's auto body contains release notes, but the required template fields are not filled in.
• Recommendation: Add a concise "What & Why" section (2–3 lines). Example to paste into the PR body:
  • What & Why: "Bump axios from 1.13.5 to 1.15.0 in /apps/Standalone to apply security fixes (header injection CRLF rejection and SSRF/no_proxy normalization) and get minor maintenance updates."

---

❌ Impact of Change

• Impact details are missing from the template.
• Recommendation: Fill out Impact of Change with short bullet points. Example:
  • Users: No direct UI change expected. Potentially reduced security risk due to axios fixes.
  • Developers: Check for code that programmatically sets header values — header values containing CR/LF will now throw an error. Confirm any proxy environment expectations with the new proxy normalization.
  • System: Minimal. Run full CI and smoke tests for the Standalone app to ensure no runtime regressions.

---

❌ Test Plan

• Assessment: The code diff is a single package.json update (1 file, 1 addition, 1 deletion). No unit tests or E2E tests were added/updated and the PR body does not include the Test Plan section of the template.
• Requirement from policy: If no unit tests and no E2E tests are added, the PR body must explain why and confirm manual testing or CI coverage. Without any explanation this check must fail.
• Recommendation: Update the Test Plan section in the PR body. Options:
  • Add/modify unit or E2E tests if this upgrade affects code paths covered by tests.
  • Or provide manual testing steps and CI confirmations, e.g. run yarn && yarn test and a quick smoke run of /apps/Standalone with Node versions used in CI. Specifically check code paths that set headers and any proxy behavior.

---

⚠️ Contributors

• Assessment: The template field is optional; it's OK if blank, but it's recommended to credit contributors.
• Recommendation: Add a short Contributors line (Dependabot is the opener) or leave blank if not applicable.

---

⚠️ Screenshots/Videos

• Assessment: Not applicable for this non-visual change. OK to leave blank.
• Recommendation: N/A

---

Summary Table

Section	Status	Recommendation
Title	✅	Keep the current title as-is.
Commit Type	❌	Select chore in the PR body.
Risk Level	❌	Add risk:medium label and select it in the PR body.
What & Why	❌	Add a short "What & Why" summary (1–2 lines).
Impact of Change	❌	Fill Users/Developers/System impact bullets.
Test Plan	❌	Add unit/E2E tests or explicit manual/CI test steps explaining why none are needed.
Contributors	⚠️	Optional: add if others contributed.
Screenshots/Videos	⚠️	Not applicable.

---

Summary / Next steps

• This PR does not pass the PR-body/template checks because the required PR template fields are not filled and a risk label is missing. The code change itself is small (single dependency bump) and the PR title is fine.
• Please update the PR body to include the required template fields: Commit Type (select chore), Risk Level (select and add label risk:medium), What & Why, Impact of Change, and Test Plan. In the Test Plan explain the lack of new tests (if you cannot add tests) and include manual verification steps and CI runs that were performed.
• Additionally, since axios 1.15.0 contains security-related behavior changes (headers with CR/LF now throw "Invalid character in header content", and proxy/no_proxy normalization changes), please:
  1. Search code in /apps/Standalone for places that set or sanitize header values and ensure none inject CRLF characters.
  2. Verify any usage that depends on env proxy behavior still behaves as expected.
  3. Run the Standalone app's integration/smoke tests in CI and locally if possible.

Please update the PR with the template fields and the risk label, document the test plan (or add tests), and re-request review. Thank you for keeping dependencies up-to-date — including these details will help make the upgrade safe and clear for reviewers.

---

Last updated: Wed, 15 Apr 2026 23:36:15 GMT