Repository navigation
fix(deps): update patch updates (patch) - #1262
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
Contributor
|
Thank you for following the naming conventions! 🙏 |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
renovate
Bot
force-pushed
the
renovate/patch-patch-updates
branch
from
November 6, 2026 11:31
9de9078 to
8049267
Compare
renovate
Bot
force-pushed
the
renovate/patch-patch-updates
branch
2 times, most recently
from
November 10, 2026 11:30
880c6cc to
870f85e
Compare
renovate
Bot
force-pushed
the
renovate/patch-patch-updates
branch
from
November 12, 2026 11:12
870f85e to
f99154c
Compare
Signed-off-by: Renovate Bot <bot@renovateapp.com>
renovate
Bot
force-pushed
the
renovate/patch-patch-updates
branch
from
November 13, 2026 09:42
f99154c to
815859d
Compare
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
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.
This PR contains the following updates:
31.0.0→31.0.34.6.1→4.6.38.1.36→8.1.3713.4.38→13.4.39>=2.1.5→>=2.1.6>=1.21.0→>=1.21.1>=1.21.0→>=1.21.1>=1.21.0→>=1.21.11.0.30001820→1.0.30001823>=1.16.2→>=1.16.3>=14.0.3→>=14.0.4>=4.13.16→>=4.13.17>=10.7.5→>=10.7.60.9.21→0.9.227.0.2005→7.0.20066.1.3→6.1.47.8.5→7.8.6>=8.12.3→>=8.12.4bump,lockfileUpdate, orrollbackupdates, so these are raised without a Minimum Release Age check. You will need to manually validate the Minimum Release Age for these package(s).Release Notes
anolilab/javascript-style-guide (@anolilab/eslint-config)
v31.0.3Compare Source
Dependencies
v31.0.2Compare Source
Bug Fixes
v31.0.1Compare Source
Bug Fixes
Dependencies
anolilab/semantic-release (@anolilab/multi-semantic-release)
v4.6.3Compare Source
Bug Fixes
v4.6.2Compare Source
Miscellaneous Chores
Tests
Dependencies
anolilab/semantic-release (@anolilab/semantic-release-pnpm)
v8.1.37Compare Source
Miscellaneous Chores
Dependencies
anolilab/semantic-release (@anolilab/semantic-release-preset)
v13.4.39Compare Source
Dependencies
honojs/node-server (@hono/node-server@<2.0.5)
v2.1.6Compare Source
Security fixes
This release includes fixes for the following security issues:
Backslash in the request path is parsed as a path separator, bypassing path-based access control at a reverse proxy
Affects: all requests. The raw request-target was passed to the WHATWG URL parser, which treats a backslash in the path as
/and resolves..segments, so/admin\secretreached the application as/admin/secret. A reverse proxy that forwards the backslash unchanged applied its path-based rules to the original path. GHSA-jpvv-r467-5p4wA request whose path contains a raw backslash is now rejected with
400 Bad Request, for HTTP/1.1, HTTP/2 and WebSocket upgrades. A percent-encoded backslash (%5C) and a backslash in the query string are still accepted.WebSocket upgrade request-target starting with
//replaces the host inc.req.url, bypassingOriginchecksAffects:
upgradeWebSocket. The URL of an upgrade request was built by resolving the request-target against theHostheader, so a request-target such as//attacker.example/wsset the host ofc.req.urlto a client-chosen value while routing still saw/ws. An application that comparedOriginwith the origin ofc.req.urlcould be bypassed by a page on another site. GHSA-7v5p-43qr-wch5The host of upgrade requests now comes from the
Hostheader, as for ordinary requests.Unhandled
ECONNRESETon the socket during an asynchronous WebSocket upgrade crashes the processAffects:
upgradeWebSocket. While the application handled an upgrade request, the socket had no error listener. A client that reset the connection during asynchronous middleware caused an unhandled'error'event and terminated the process. GHSA-qv5m-9pm6-hqp3Error and close events on the socket are now handled while the application runs, and a pending upgrade is released when the socket closes.
The backslash fix also ships in
@hono/node-serverv1.19.18. Users ofupgradeWebSocketare encouraged to upgrade to this version.axios/axios (axios@<1.18.0)
v1.21.1Compare Source
v1.21.1 — November 9, 2026
This release raises the minimum
follow-redirectsversion to fix a published CVE, fixes a Next.js prerendering failure caused by the response duration timer, corrects thegetAdaptertypings, and includes documentation corrections, new test coverage, CI runner changes and dependency updates.🔒 Security Fixes
follow-redirectsrange from^1.16.0to^1.16.2to fix CVE-2026-116689 (GHSA-mrwp-f3q8-3g9p). In the vulnerable versions,sensitiveHeadersarrays from another realm were ignored and custom credentials could follow redirects. Only the Node.js HTTP adapter is affected, and there are no API changes. (#11410)🐛 Bug Fixes
dispatchRequestnow measuresresponse.durationwithperformance.now()and usesDate.now()only whenperformance.now()isn't available. In v1.21.0, any axios request from a Server Component failed Next.js production builds with Cache Components (cacheComponents: true), because Next.js rejectsDate.now()while prerendering. The duration is still a whole number of milliseconds, and system clock changes no longer affect it. (#11411)getAdapternow accepts an optionalconfig?: AxiosRequestConfiginindex.d.tsandindex.d.cts, matching what it does at runtime. You can now callgetAdapter('fetch', { env: { fetch: myFetch } })without a cast. (#11404)🔧 Maintenance & Chores
Documentation Corrections: Brought the README and docs site in line with how axios actually behaves:
transformRequestruns for every method, and transformers receive(data, headers, status).responseTypeandContent-Typehave no default value.AxiosHeaders#getand#normalizeare described correctly.axios.isAxiosError(), not byname.ECONNREFUSEDandERR_FORM_DATA_DEPTH_EXCEEDED, and note that FormData parsing has a fixed depth limit thatmaxDepthdoesn't change.redactdoesn't scan, which adapters enforcemaxContentLength/maxBodyLength, and howformToJSON()handles field name collisions.(#11374, #11373, #11389, #11419, #11429, #11430)
Docs Site: Added a Partners page, a shared card design for sponsors and partners, a Namespace sponsor badge, and a blog whose first post announces HeroDevs Never-Ending Support for Axios v0. Also applied the v1.20.0/v1.21.0 release notes to the docs, and fixed internal links in the es, fr and zh translations so they keep their locale prefix. (#11390, #11399, #11400, #11412, #11401)
Test Coverage: Added cancellation tests across the HTTP, fetch and XHR adapters. They cover
AbortSignal,CancelToken, cancelling while a request interceptor is pending, and timeout precedence. Also added tests forno_proxyedge cases inshouldBypassProxy, such as internationalized domain names, malformed CIDR and IPv4 entries, and port-qualified entries. Neither changes runtime behavior. (#11376, #11431)CI: GitHub Actions jobs now run on Namespace runners. The npm publish job stays on GitHub-hosted runners, because npm provenance and trusted publishing (OIDC) only work there. (#11396)
Dependencies: Updated development and tooling dependencies, including
vitestand@vitest/*(to 5.x at the root),typescript(7.x at the root),vite,rollup,eslint,playwright,@commitlint/*,@rollup/plugin-alias,@rollup/plugin-terser,body-parser,multer,serialize-javascript,fast-uri,qs,zizmorcore/zizmor-action, andfollow-redirectsin/docs. (#11383, #11375, #11372, #11345, #11392, #11387, #11386, #11385, #11391, #11388, #11395, #11421, #11422, #11426)Release: Prepared the 1.21.1 release. (#11435)
🌟 New Contributors
We are thrilled to welcome our new contributors. Thank you for helping improve axios:
Full Changelog
browserslist/caniuse-lite (caniuse-lite)
v1.0.30001823Compare Source
v1.0.30001822Compare Source
follow-redirects/follow-redirects (follow-redirects@<=1.15.11)
v1.16.3Compare Source
isaacs/node-glob (glob@>=9.0.0 <=14.0.1)
v14.0.4Compare Source
honojs/hono (hono@<4.12.27)
v4.13.17Compare Source
What's Changed
__Secure-and__Host-prefixes case-insensitively in #5608setMetricin #5363__Secure-and__Host-prefixes case-insensitively inCookieConstraintin #5611ErrorBoundaryin #5430toSSGruns in #5381Full Changelog: honojs/hono@v4.13.16...v4.13.17
beaugunderson/ip-address (ip-address@<=10.1.0)
v10.7.6Compare Source
Full Changelog: beaugunderson/ip-address@v10.7.5...v10.7.6
millionco/react-doctor (oxlint-plugin-react-doctor)
v0.9.22Compare Source
Patch Changes
ad51b5aThanks @aidenybai! - Treat an effect cleanup that only reads a proven local runtime binding as empty. Preserve cleanup exemptions for global identifiers and member reads that can run getters, and keep no-op filtering conservative in other rules.no-mirror-prop-effect,no-event-trigger-state,no-effect-event-handler,no-effect-chainandrendering-hydration-no-flickeralso stop skipping effects with proven empty or read-only inline cleanups. Unknown cleanup factories and other effectful returns remain conservative.isaacs/rimraf (rimraf)
v6.1.4Compare Source
npm/node-semver (semver)
v7.8.6Compare Source
Bug Fixes
69b305d#918 improve range parsing performance (#918) (@reggi, @Copilot)Chores
7257c14#917 cover comparator normalization (#917) (@reggi, @Copilot)nodejs/undici (undici@<8.10.2)
v8.12.4Compare Source
This release fixes six vulnerabilities.
CVE-2026-116592 / GHSA-mqg3-3v4r-cm32 (high)
Undici 8.12.2 and 8.12.3 could cache the final response from a redirect chain under the original request key without applying the origin, cache policy, freshness, or
Varyrequirements of every intermediate hop. This could poison a cache or expose one user's response to another user. The fix validates every redirect hop, combines theirVaryfields, limits freshness and stale serving to the most restrictive hop, and invalidates persistent SQLite entries written by vulnerable releases.CVE-2026-120474 / GHSA-7xg3-fphp-28hg (medium)
A shared cache used with
compose(redirect(), cache())could store a credential-dependent response from a same-origin redirect under the original URL. A later authenticated or unauthenticated request could then receive another user's response. Redirected requests carryingAuthorization,Cookie, orProxy-Authorizationare no longer stored under the original alias key.CVE-2026-116630 / GHSA-5rm8-gv32-r954 (medium)
A cross-origin redirect during cache revalidation could let a
304 Not Modifiedresponse from the redirect target validate a cached response from the original origin. Undici now checks that the revalidation target matches the cached URL and that any returned validator matches the stored representation before replaying the cached body.CVE-2026-120415 / GHSA-9v6h-8rgp-m69f (medium)
The redirect interceptor did not strip credentials correctly when request headers were supplied as an array of
[name, value]pairs. With a header-normalizing interceptor outsideredirect(), credentials could be sent to a cross-origin redirect target. Undici now handles both tuple arrays and flat header arrays when removing sensitive headers.CVE-2026-120222 / GHSA-3g9m-rv3r-w5w2 (medium)
A downstream handler exception during cache replay could escape as an uncaught exception or unhandled promise rejection and terminate the process. This included
dumpsize-limit failures, excessiveContent-Encodingvalues indecompress, asynchronous cache-store failures, and cached-body replay after a304. These failures are now reported as request errors.CVE-2026-120423 / GHSA-r4pc-4jcp-7pqc (medium)
fetch()could skip Subresource Integrity verification when valid integrity metadata was separated or surrounded by ASCII whitespace other than a space, including a horizontal tab. Integrity metadata is now split on all ASCII whitespace before SHA-256, SHA-384, or SHA-512 verification.What's Changed
originis optional only for origin-bound dispatchers by @attilayener in #5994New Contributors
Full Changelog: nodejs/undici@v8.12.3...v8.12.4
Configuration
📅 Schedule: (in timezone Europe/Berlin)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.