what stackpulse tracks
Axios releases from GitHub
StackPulse watches Axios release notes and keeps the original source link close to every summary.
Promise based HTTP client for the browser and Node.js StackPulse turns upstream changelogs into scannable summaries with risky changes, deprecations, migration notes, and source links.
what stackpulse tracks
StackPulse watches Axios release notes and keeps the original source link close to every summary.
upgrade risk
Risky changes are separated from normal feature notes so you can scan upgrade impact before changing production dependencies.
migration notes
Migration steps and recommended actions are only shown when the upstream release notes support them.
Axios v1.21.1 raises the minimum `follow-redirects` version to address CVE-2026-116689, affecting redirects in the Node.js HTTP adapter. It also fixes a Next.js prerendering failure by measuring response duration with `performance.now()` when available, and corrects the TypeScript signature for `getAdapter`.
Users of Axios’s Node.js HTTP adapter are affected by the redirect credential vulnerability; users building Next.js Server Components with Cache Components and TypeScript users of `getAdapter` also benefit from the fixes.
Upgrade to Axios 1.21.1 to receive the `follow-redirects` security fix and the reported compatibility and typing corrections.
Axios v0.35.0 tightens parameter validation and changes form serialization behavior, with stricter handling of deeply nested parameters and native proxy-agent configurations. It also fixes connection-pool handling, upload limits, FileList conversion, and browser/runtime compatibility across Node and browser environments.
Users relying on deeply nested `params`, prior sparse-array or numeric-index form serialization, or custom agents overriding native proxy lifecycle hooks may see changed behavior or validation errors.
Review parameter depth, form serialization expectations, and custom native-proxy agent configurations before upgrading.
Axios 1.21.0 adds response-duration reporting and opt-in UTF-8 Basic authentication, alongside broad fixes to runtime compatibility, adapters, headers, and diagnostics. It also changes how header defaults are recognized: custom class instances are no longer treated as method-specific defaults unless converted to a plain map or compatible AxiosHeaders instance.
Axios users relying on custom class instances for header defaults may need to convert them; users needing Unicode Basic authentication can opt in, while other users benefit from timing and compatibility fixes.
Review header-default configuration for custom class instances and convert any such defaults to plain maps or compatible AxiosHeaders instances.
This release backports security and hardening fixes from the v1.x branch into v0.x, including prototype-pollution protections, default error redaction, stricter proxy/cookie/socket handling, and a breaking change to merged config and header object prototypes.
Users relying on implicit string coercion against merged config or header objects will be affected.
Update code to use Object.prototype.hasOwnProperty.call(obj, key) for merged config or header objects.