chore(deps): bump axios from 1.13.5 to 1.15.0#5837
Conversation
Bumps [axios](https://github.com/axios/axios) from 1.13.5 to 1.15.0. - [Release notes](https://github.com/axios/axios/releases) - [Changelog](https://github.com/axios/axios/blob/v1.x/CHANGELOG.md) - [Commits](axios/axios@v1.13.5...v1.15.0) --- updated-dependencies: - dependency-name: axios dependency-version: 1.15.0 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
rtibblesbot
left a comment
There was a problem hiding this comment.
Clean dependency update with two meaningful security fixes.
CI passing.
Dependency Update Review
Package: axios 1.13.5 → 1.15.0
Semver risk: Minor
Dependency type: Production
CI status: Passing
Changelog Analysis
Sources consulted:
- PR body (release notes for v1.14.0 and v1.15.0, changelog entries)
Breaking changes: None that affect this project. The CRLF header validation change (headers containing \r/\n now throw) would only affect code that intentionally embeds control characters in headers — a security vulnerability — which this codebase does not do.
Security fixes:
- v1.15.0 — SSRF via
no_proxyhostname normalisation bypass (strips trailing dots, handles bracketed IPv6 before evaluatingNO_PROXYrules) - v1.15.0 — Header injection (CRLF) blocking cloud metadata (IMDS) exfiltration chains
- v1.14.0 — Formidable v2 → v3 upgrade addressing an arbitrary-file vulnerability
Other notable changes:
- v1.14.0: HTTP/2 session cleanup on timeout;
ReadableStreamcancellation to prevent async resource leaks; CJS compatibility fix; proxy-from-env v2 alignment - v1.15.0: Node.js v22 compatibility (deprecated
url.parse()replaced with WHATWGURL)
Compatibility Assessment
- Project uses axios for HTTP requests with standard CSRF token headers — no usage of CR/LF in header values
- Only
package.jsonandpnpm-lock.yamlchanged — no code migration required - Peer dependency changes: none
- Prior failed attempts: none found
Recommendation
APPROVE — security-motivated minor bump, no breaking changes affecting this project, CI passing.
@rtibblesbot's comments are generated by an LLM, and should be evaluated accordingly
How was this generated?
Reviewed the pull request diff checking for:
- Correctness: bugs, edge cases, undocumented behavior, resource leaks, hardcoded values
- Design: unnecessary complexity, naming, readability, comment accuracy, redundant state
- Architecture: duplicated concerns, minimal interfaces, composition over inheritance
- Testing: behavior-based assertions, mocks only at hard boundaries, accurate coverage
- Completeness: missing dependencies, unupdated usages, i18n, accessibility, security
- Principles: DRY (same reason to change), SRP, Rule of Three (no premature abstraction)
- Checked CI status and linked issue acceptance criteria
- For UI changes: inspected screenshots for layout, visual completeness, and consistency
rtibbles
left a comment
There was a problem hiding this comment.
Only "breaking" change is a security vulnerability - no impact on Studio code.
Bumps axios from 1.13.5 to 1.15.0.
Release notes
Sourced from axios's releases.
... (truncated)
Changelog
Sourced from axios's changelog.
... (truncated)
Commits
772a4e5chore(release): prepare release 1.15.0 (#10671)4b07137chore(deps-dev): bump vite from 8.0.0 to 8.0.5 in /tests/smoke/esm (#10663)51e57b3chore(deps-dev): bump vite from 8.0.2 to 8.0.5 (#10664)fba1a77chore(deps-dev): bump vite from 8.0.2 to 8.0.5 in /tests/module/esm (#10665)0bf6e28chore(deps): bump denoland/setup-deno in the github-actions group (#10669)8107157chore(deps-dev): bump the development_dependencies group with 4 updates (#10670)e66530eci: require npm-publish environment for releases (#10666)49f23cbchore(sponsor): update sponsor block (#10668)3631854fix: unrestricted cloud metadata exfiltration via header injection chain (#10...fb3befbfix: no_proxy hostname normalization bypass leads to ssrf (#10661)Install script changes
This version modifies
preparescript 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 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.