fix(deps): update all non-major dependencies with stable versions (patch) - #899
Merged
Conversation
renovate
Bot
requested review from
adamdehaven and
kongponents-bot
as code owners
July 8, 2026 07:54
renovate
Bot
requested review from
a team,
DariaYeremina,
ValeryG and
jillztom
as code owners
July 8, 2026 07:54
renovate
Bot
force-pushed
the
renovate/patch-all-stable
branch
4 times, most recently
from
July 14, 2026 07:49
f28d438 to
3b236cb
Compare
renovate
Bot
force-pushed
the
renovate/patch-all-stable
branch
9 times, most recently
from
July 23, 2026 06:20
3d44b23 to
fb57895
Compare
renovate
Bot
force-pushed
the
renovate/patch-all-stable
branch
2 times, most recently
from
July 25, 2026 06:53
54bd9d7 to
0b50c0c
Compare
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
renovate
Bot
force-pushed
the
renovate/patch-all-stable
branch
from
July 27, 2026 07:31
0b50c0c to
b152955
Compare
vaibhavrajsingh2001
approved these changes
Jul 27, 2026
Collaborator
|
🎉 This PR is included in version 1.109.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Collaborator
Install the preview package from this PR@kong/spec-renderer@pr-899 |
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:
>=8.0.0→>=8.0.1^2.1.9→^2.1.10^5.2.0→^5.2.1^24.13.2→^24.13.3^6.0.7→^6.0.8^3.2.6→^3.2.7^10.5.1→^10.5.3>=5.2.3→>=5.2.5>=5.2.3→>=5.2.5](https://renovatebot.com/diffs/npm/bn.js@>=5.0.0 <5.2.3/5.2.3/5.2.5)>=5.1.8→>=5.1.9](https://renovatebot.com/diffs/npm/immutable@>=5.0.0 <5.1.8/5.1.8/5.1.9)^14.2.0→^14.3.0>=4.0.4→>=4.0.5>=6.15.2→>=6.15.3](https://renovatebot.com/diffs/npm/qs@>=6.7.0 <=6.15.1/6.15.2/6.15.3)^2.17.5→^2.17.6>=2.17.5→>=2.17.6^25.0.5→^25.0.7^7.3.5→^7.3.6^8.1.3→^8.1.5>=7.3.5→>=7.3.6](https://renovatebot.com/diffs/npm/vite@>=7.0.0 <=7.3.4/7.3.5/7.3.6)>=3.2.6→>=3.2.7^3.5.38→^3.5.39^3.3.5→^3.3.7>=8.21.0→>=8.21.1](https://renovatebot.com/diffs/npm/ws@>=8.0.0 <8.21.0/8.21.0/8.21.1)Release Notes
babel/babel (@babel/core@<8.0.0)
v8.0.1Compare Source
💥 Breaking Change
babel-core,babel-plugin-transform-object-rest-spread,babel-plugin-transform-runtime,babel-preset-env,babel-standalonepreset-env'suseBuiltIns(@nicolo-ribaudo)evilmartians/lefthook (@evilmartians/lefthook)
v2.1.10Compare Source
NO_COLORis set (#1449) by @viralpraxisvitejs/vite-plugin-vue (@vitejs/plugin-vue)
v6.0.8Features
Bug Fixes
vitest-dev/vitest (@vitest/ui)
v3.2.7Compare Source
🐞 Bug Fixes
View changes on GitHub
postcss/autoprefixer (autoprefixer)
v10.5.3Compare Source
indutny/bn.js (bn.js@<4.12.3)
v5.2.5Compare Source
v5.2.4Compare Source
immutable-js/immutable-js (immutable@>=5.0.0 <5.1.8)
v5.1.9Compare Source
Listgrown past 32 elements while all its values areundefinedno longer reads those values back asnull(affectedget, iteration,toArray,equalsandhashCode)micromatch/picomatch (picomatch@<2.3.2)
v4.0.5Compare Source
ljharb/qs (qs@>=6.7.0 <=6.15.1)
v6.15.3Compare Source
parse: enforcethrowOnLimitExceededfor cumulative array growth viacombine/mergeutils: respect encoding of surrogate pairs across chunks (#559)parse: throw thearrayLimiterror before splitting oversized comma valuesutils.merge/utils.assign: avoid invoking__proto__setter when copying own propertiesutils: enforcearrayLimitconsistently acrossmerge's array pathsutils: makecompactO(n) via a side-channel visited-set instead ofArray.indexOfside-channeleslint,mock-property,tapeparse: characterize current lenient handling of unbalanced bracket keys (#558)apostrophecms/apostrophe (sanitize-html)
v2.17.6Fixes
Security
textareaorxmp) nested inside ansvgormathroot were re-emitted without HTML-escaping.sanitize-htmltreated that content as inert raw text becausehtmlparser210.x classified raw-text elements by tag name and ignored the namespace, but a real HTML5 parser treatstextarea/xmpas ordinary foreign elements inside SVG/MathML and re-parses their contents as live markup. As a result, markup and event-handler attributes that the allowlist never permitted (for example<svg><textarea><img src=x onerror=alert(1)>) could survive sanitization and execute in the browser. This is now fixed on two fronts:htmlparser2was upgraded to 12.x, which is namespace-aware and parsestextarea/xmpinside SVG/MathML as ordinary elements, so their non-allowlisted children (such as the injectedimg) are dropped by the allowlist instead of being preserved as raw text; and any raw-text contentsanitize-htmlstill emits for these tags (at HTML integration points such asforeignObject/mtext, or outside foreign content) is always HTML-escaped. The default configuration is not affected; the precondition is anallowedTagsthat includessvgormathtogether withtextareaorxmp. Thanks to khoadb175 for responsibly disclosing the vulnerability.allowedTagsbypass affecting configurations that allow thetextareaorxmpraw-text tags.htmlparser210.x did not recognize an end tag with a trailing solidus (e.g.</textarea/>) as closing the element, so it kept the following markup as raw text, but a spec-compliant browser treats</textarea/>as a valid close and parses that markup as a live element. Because raw-text content was re-emitted without escaping, a payload such as<textarea></textarea/><img src=x onerror=...>could smuggle non-allowlisted, executable markup through the sanitizer. The default configuration was not affected. This is now defended at two layers:htmlparser2was upgraded to 12.x, whose tokenizer closes these end tags correctly, and the raw text sanitize-html emits for these tags is always escaped so no<can reopen a tag when the output is re-parsed (textarea, an RCDATA element whose entitieshtmlparser2decodes, is escaped like normal text, whilexmp, a raw-text element, has only its angle brackets escaped to avoid double-encoding already-encoded entities). Becausehtmlparser2is ESM-only from version 11 onward,sanitize-htmlnow requires Node.js>=22.12.0(the first 22.x release in whichrequire()of an ES module is available unflagged). Thanks to bibu123456 for reporting the vulnerability and Kayiz-PT for coordinating the disclosure (GHSA-jxwj-j7wr-gfrw).semantic-release/semantic-release (semantic-release)
v25.0.7Compare Source
Bug Fixes
v25.0.6Compare Source
Bug Fixes
vitejs/vite (vite@>=7.0.0 <=7.3.4)
v7.3.6Compare Source
Please refer to CHANGELOG.md for details.
vuejs/language-tools (vue-tsc)
v3.3.7Compare Source
language-core
return(#6115) - Thanks to @KazariEX!typescript-plugin
websockets/ws (ws@>=8.0.0 <8.21.0)
v8.21.1Compare Source
Bug fixes
a2f4e7c).maxBufferedChunksandmaxFragmentsoptions havebeen reduced (
f197ac6).Configuration
📅 Schedule: (in timezone America/New_York)
* 0-3 * * *)* * * * 1-5)🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, 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.