Skip to content

fix(deps): bump the npm group with 9 updates - #197

Merged
kneshi merged 2 commits into
mainfrom
dependabot/npm_and_yarn/npm-1764b919b6
Nov 22, 2026
Merged

kneshi merged 2 commits into
mainfrom
dependabot/npm_and_yarn/npm-1764b919b6

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 22, 2026

Copy link
Copy Markdown
Contributor

Bumps the npm group with 9 updates:

Package From To
@nestjs/schedule 12.0.2 12.0.4
@nestjs/throttler 6.7.1 6.8.0
nestjs-pino 5.3.1 5.3.2
sanitize-html 2.18.1 2.18.2
next 16.4.5 16.4.6
@tailwindcss/postcss 4.3.3 4.3.5
@testing-library/jest-dom 7.0.1 8.0.0
jsdom 30.1.3 31.0.1
tailwindcss 4.3.3 4.3.5

Updates @nestjs/schedule from 12.0.2 to 12.0.4

Release notes

Sourced from @​nestjs/schedule's releases.

Release 12.0.4

Bug fixes

Full Changelog: nestjs/schedule@12.0.3...12.0.4

Release 12.0.3

Bug fixes

Full Changelog: nestjs/schedule@12.0.2...12.0.3

Commits
  • 3c29c58 chore(): release v12.0.4
  • 9cab45d chore(deps): update nest monorepo to v12.5.0 (#2417)
  • 8c55228 chore(deps): update dependency prettier to v3.10.1 (#2416)
  • a8e320a chore(deps): update dependency prettier to v3.10.0 (#2415)
  • 23dd72e fix: skip aliased providers when exploring scheduled methods (#2413)
  • f2f7299 chore(deps): update dependency vite to v8.3.8 (#2414)
  • acd5c3a chore(deps): update dependency oxlint to v1.93.0 (#2412)
  • 04e0cf1 chore(deps): update nest monorepo to v12.4.2 (#2411)
  • 6ba1880 chore(deps): update dependency vite to v8.3.7 (#2410)
  • d89e448 chore(deps): update dependency oxlint to v1.92.0 (#2409)
  • Additional commits viewable in compare view

Updates @nestjs/throttler from 6.7.1 to 6.8.0

Release notes

Sourced from @​nestjs/throttler's releases.

v6.8.0

Minor Changes

  • 2e075c6: Allow skipIf to return a promise, so the decision to skip throttling can depend on an asynchronous lookup such as a database or Redis call. Synchronous skipIf callbacks keep working unchanged.

Patch Changes

  • 23b32ee: Stop throwing RangeError: Maximum call stack size exceeded with blockDuration: 0 once a window holds more than about 125,000 hits. Every request on that key failed with a 500 instead of being counted, even below the limit.
  • 22e9340: Keep rejecting requests with limit: 0 after a block has elapsed. One request got through at the end of every block, because the first hit after a block was not checked against the limit.
  • 35b1b84: Track NAT64 well-known prefix (64:ff9b::a.b.c.d) source addresses by their embedded IPv4 address. The default tracker used to mask them to a /64 like any other IPv6 address, which merged every IPv4 client behind a NAT64 gateway into a single rate-limit bucket.
  • edbfd85: Support request-scoped guards. Nest does not call onModuleInit() on these instances, so a guard that is request-scoped, or depends on a request-scoped provider, failed every request with this.throttlers is not iterable.
  • bd78317: Sort throttlers by ttl when one of them uses a callback ttl. The comparator was not consistent, so a throttler with a callback ttl could stay ahead of the others and the static ones were left unsorted. A request rejected by a short throttler was then still counted against a longer one, which could block the client for the whole longer window.
  • 4cfda86: Match every request against ignoreUserAgents patterns that use the g or y flag. These patterns keep their position between checks, so every other matching request was counted against the limit.
Changelog

Sourced from @​nestjs/throttler's changelog.

6.8.0

Minor Changes

  • 2e075c6: Allow skipIf to return a promise, so the decision to skip throttling can depend on an asynchronous lookup such as a database or Redis call. Synchronous skipIf callbacks keep working unchanged.

Patch Changes

  • 23b32ee: Stop throwing RangeError: Maximum call stack size exceeded with blockDuration: 0 once a window holds more than about 125,000 hits. Every request on that key failed with a 500 instead of being counted, even below the limit.
  • 22e9340: Keep rejecting requests with limit: 0 after a block has elapsed. One request got through at the end of every block, because the first hit after a block was not checked against the limit.
  • 35b1b84: Track NAT64 well-known prefix (64:ff9b::a.b.c.d) source addresses by their embedded IPv4 address. The default tracker used to mask them to a /64 like any other IPv6 address, which merged every IPv4 client behind a NAT64 gateway into a single rate-limit bucket.
  • edbfd85: Support request-scoped guards. Nest does not call onModuleInit() on these instances, so a guard that is request-scoped, or depends on a request-scoped provider, failed every request with this.throttlers is not iterable.
  • bd78317: Sort throttlers by ttl when one of them uses a callback ttl. The comparator was not consistent, so a throttler with a callback ttl could stay ahead of the others and the static ones were left unsorted. A request rejected by a short throttler was then still counted against a longer one, which could block the client for the whole longer window.
  • 4cfda86: Match every request against ignoreUserAgents patterns that use the g or y flag. These patterns keep their position between checks, so every other matching request was counted against the limit.
Commits
  • 919f9c7 chore: version packages (#2720)
  • bd78317 fix(guard): sort throttlers consistently with a callback ttl (#2738)
  • 23b32ee fix(storage): avoid stack overflow on large unblocked windows (#2739)
  • 4cfda86 fix(guard): match stateful user agent patterns on every request (#2736)
  • edbfd85 fix(guard): support request-scoped guards (#2735)
  • 22e9340 fix(storage): keep rejecting requests with a limit of zero (#2734)
  • 2e075c6 feat: allow skipIf to return a promise (#2732)
  • 143e7e0 Merge pull request #2719 from phankieuphu/issue/2718
  • e3e6bd9 fix: only collapse nat64 and ipv4-mapped addresses
  • 35b1b84 fix: track nat64 and ipv4-compatible addresses by their embedded ipv4
  • See full diff in compare view

Updates nestjs-pino from 5.3.1 to 5.3.2

Release notes

Sourced from nestjs-pino's releases.

5.3.2: log nested paths on Fastify without a global prefix

What's Changed

New Contributors

Full Changelog: iamolegga/nestjs-pino@5.3.1...5.3.2

Commits
  • 6b15c3a build(deps-dev): bump supertest from 7.3.1 to 7.3.2
  • e211e2d build(deps-dev): bump the nestjs group across 1 directory with 6 updates
  • 4b61a92 build(deps-dev): bump @​swc/core
  • 1ee306b fix: log nested paths on Fastify without a global prefix
  • c0c90a0 fix: run the logger middleware once per request
  • 46d0a03 build(deps-dev): bump @​biomejs/biome
  • 38bdd29 build(deps-dev): bump rimraf from 6.1.3 to 6.1.4
  • 00b397f build(deps-dev): bump the vitest group with 3 updates
  • adece54 build(deps-dev): bump @​biomejs/biome
  • 15c4975 build(deps-dev): bump the nestjs group with 6 updates
  • Additional commits viewable in compare view

Updates sanitize-html from 2.18.1 to 2.18.2

Changelog

Sourced from sanitize-html's changelog.

2.18.2 (2026-11-11)

Fixes

  • With parser.decodeEntities: false, named entities longer than 20 characters, such as &CounterClockwiseContourIntegral;, are no longer double-encoded. Thanks to Kenny for the contribution.

Security

  • Outside SVG and MathML, browsers parse <![CDATA[ as a bogus comment that ends at the first >, but the underlying parser read it all the way to ]]>. Markup between those two points was hidden from sanitize-html, so a start tag for one of the nonTextTags (such as noscript, style, script, textarea or xmp) placed there was not seen, and content the browser would keep inert inside that element was emitted as live markup. Only tags, attributes and URL schemes permitted by the allowlist could be emitted this way. A <![CDATA[ section now always ends at the first >, as it does in HTML content in a browser. As a result, the text of a real CDATA section inside SVG or MathML is now dropped or sanitized as markup instead of being kept as text, and the literal sequence <![CDATA[ inside an allowed script or style element is written as <!&[#91](https://github.com/apostrophecms/apostrophe/tree/HEAD/packages/sanitize-html/issues/91);CDATA[ (CWE-79, CWE-436, GHSA-2rjc-9xvg-45j7).

    Thanks to Oscar Rodríguez for reporting the vulnerability.

  • The check that drops SVG animation elements (animate, animateColor, animateMotion, animateTransform, set) when they retarget a URL attribute such as href took only the part of attributeName after its last colon as the target. Browsers split a name with more than one colon differently, and current Chrome resolves a spelling such as xlink:href:x to xlink:href, so the animation was kept and could retarget a link to a javascript: URL after sanitization. Every colon-separated part of attributeName, and of the element name, is now matched. The default configuration is not affected: it only applies when animation elements are allowed together with attributeName and an animation value attribute such as values or to (CWE-79, CWE-184, GHSA-8g6g-w2rq-xcmc).

    Thanks to Zachariah Mithani for reporting the vulnerability.

  • When style was allowed, the content of a <style> element inside svg or math could be emitted as live markup, even when svg and math themselves were not allowed. The underlying parser and browsers do not always agree on whether such a <style> is an HTML element, whose content is raw CSS text, or an SVG/MathML element, whose content is markup: for example a <style> inside MathML annotation-xml without an HTML encoding is a MathML element to a browser but raw text to the parser, and inside svg or math the parser decodes &lt; in its content. Because sanitize-html emitted style content as is, markup that the allowlist never permitted, including event handler attributes, could reach the browser. Inside svg or math, a < in style content is now written as the equivalent CSS escape \3c , which means the same in a stylesheet and cannot open a tag. Other stylesheets are unchanged. Exposure is limited: style is not allowed by default, it is one of the vulnerableTags that sanitize-html warns about unless allowVulnerableTags is set, and allowing it already permits CSS-based attacks (CWE-79, GHSA-6wrv-5cp6-h3c5).

    Thanks to Ali Mustafa for reporting the vulnerability.

Commits

Updates next from 16.4.5 to 16.4.6

Release notes

Sourced from next's releases.

v16.4.6

[!NOTE] This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

  • [lts-active] Pin Tailwind to 4.3.3 in create-next-app and tests (#101061, #101176) (#101307)
  • [lts-active] Automatically compress route handler responses if not already compressed (#101280)
  • [lts-active] Turbopack GC fixes for dev (#100279, #100370) (#101308)

Credits

Huge thanks to @​lukesandberg and @​eps1lon for helping!

Commits

Updates @tailwindcss/postcss from 4.3.3 to 4.3.5

Release notes

Sourced from @​tailwindcss/postcss's releases.

v4.3.5

Fixed

  • Canonicalization: improve performance in projects with many functional variant values (e.g. a matchVariant plugin with thousands of values) (#20663)
  • Don't crash or create a fallback with the wrong color for a color-mix(…) without a color interpolation method (e.g. color-mix(var(--color-red-500)) or color-mix(currentcolor 50%, transparent)) (#20658, #20666)
  • Ensure @tailwindcss/oxide-wasm32-wasi loads instead of hanging forever (e.g. with NAPI_RS_FORCE_WASI=error or in WebContainers) (#20667)
  • Remove as: '*.css' from the @tailwindcss/turbopack setup in its README, because it breaks CSS modules (#20660)
  • Ignore <!-- and --> between top-level rules in CSS instead of throwing or swallowing the next rule (e.g. a { color: red } --> b { color: blue }) (#20665)
  • Ensure @tailwindcss/oxide-wasm32-wasi detects changed and new source files after the first scan (e.g. in WebContainers) (#20487)
  • Prevent type errors with skipLibCheck: false caused by imports of unshipped modules in the @tailwindcss/node type declarations (#20632)

v4.3.4

Added

  • Add @tailwindcss/turbopack, a Turbopack loader for using Tailwind CSS with Next.js (#20367)

Fixed

  • Ensure watch mode detects changes to symlinked @source files whose real paths aren't otherwise scanned (#20356)
  • Ensure variants using @scope wrap generated utilities instead of nesting inside them (#20369)
  • Ensure nested @scope rules preserve their scoping semantics when flattened (#20369)
  • Preserve declarations directly inside @scope by wrapping them in :where(:scope) (#20369)
  • Ensure generated utilities include a space in empty var() fallbacks (e.g. var(--tw-blur,) → var(--tw-blur, )) (#20373)
  • Canonicalization: convert arbitrary breakpoint and container query variants to named equivalents (e.g. max-[64rem]:flex → max-lg:flex) (#20380)
  • Prevent @tailwindcss/vite from crashing on every edit under Vite's experimental bundledDev mode (#20379)
  • Ensure @tailwindcss/oxide falls back to WASM on platforms without native bindings (@tailwindcss/oxide-wasm32-wasi now installs on all platforms, but only loads when no native binding is available) (#20383)
  • Extract class candidates from Ruby %w and %W literals using angle brackets or custom delimiters (e.g. %w<flex>, %w|flex|), including in Slim and Haml templates (#20387)
  • Preserve whitespace in --default(…) values in functional @utility definitions (e.g. --default(box alphabetic) no longer becomes boxalphabetic) (#20392)
  • Ensure automatic source detection respects negation-based .gitignore files (e.g. /* followed by !/… patterns) (#20397)
  • Ensure root theme('…') namespace lookups in JavaScript plugins and config files return the full namespace object instead of the value of its DEFAULT key (#20399)
  • Skip ignored directories when generating watch globs instead of walking their contents on every rebuild (#20408)
  • Drop invalid UTF-8 candidates during class detection (#20389)
  • Prevent @tailwindcss/vite from forcing full-page reloads for scanned files that Vite does not handle as modules (e.g. .php files) (#20414)
  • Canonicalization: don't merge utilities that reference different theme variables set to CSS-wide keywords like unset (#20417)
  • Don't generate utilities when a modifier is used that would otherwise be silently ignored (e.g. rounded-sm/[5], shadow-sm/foo, stroke-2/50) (#20419)
  • Preserve and, or, and not inside selectors in supports-[…] variants (e.g. supports-[selector(a:not(.foo))]:flex) (#20420)
  • Don't warn about Angular's ::ng-deep and :host-context() when optimizing CSS (#20434)
  • Don't generate CSS for candidates containing an empty additional modifier (e.g. bg-red-500/50/ and group-hover/foo//bar:flex) (#20466)
  • Ensure min-*, max-*, and container query variants with decimal values are sorted numerically (e.g. min-[40.25rem] before min-[40.5rem]) (#20512)
  • Ensure CSS comments ending with \*/ are closed correctly instead of swallowing the CSS that follows (e.g. /* C:\temp\*/) (#20508)
  • Improve style invalidation performance of group-* and peer-* variants (#20513)
  • Ensure cached compilers release their loadModule and loadStylesheet callbacks after compilation (#20531)
  • Canonicalization: preserve & when moving a pseudo-element into * or ** (e.g. [&_::before]:flex → **:[&::before]:flex) (#20550)
  • Ensure the Set.prototype.intersection polyfill in canonicalizeCandidates(…) returns the intersection instead of the first set on Node.js < 22 (#20562)
  • Canonicalization: ensure inline theme(…) alphas with more than 2 decimals migrate to a percentage modifier with the same opacity (e.g. theme(colors.red.500/.12345) → text-red-500/[12.345%], not text-red-500/[12.345]) (#20563)
  • Canonicalization: preserve inline theme(…) alphas as an arbitrary percentage when a custom --opacity-* theme value would change the opacity (e.g. theme(colors.red.500/50%) → text-red-500/[50%] with --opacity-50: 10%) (#20563)
  • Ensure the @property fallback isn't applied in Safari versions that no longer support margin-trim: inline (#20569)
  • Treat viewport units like dvmin and svi and font-relative units like cap and rex as lengths in arbitrary values (e.g. text-[10dvmin] generates font-size instead of color) (#20516)
  • Write plugin logs to stderr in tailwindcss canonicalize so they don't end up in the results on stdout (#20561)
  • Extract class shorthands on later lines when Pug text, comments, or quoted attribute values contain unbalanced brackets, or a quote that doesn't start a string (e.g. input(pattern=/"/.source)) (#20547, #20572)

... (truncated)

Changelog

Sourced from @​tailwindcss/postcss's changelog.

[4.3.5] - 2026-11-06

Fixed

  • Canonicalization: improve performance in projects with many functional variant values (e.g. a matchVariant plugin with thousands of values) (#20663)
  • Don't crash or create a fallback with the wrong color for a color-mix(…) without a color interpolation method (e.g. color-mix(var(--color-red-500)) or color-mix(currentcolor 50%, transparent)) (#20658, #20666)
  • Ensure @tailwindcss/oxide-wasm32-wasi loads instead of hanging forever (e.g. with NAPI_RS_FORCE_WASI=error or in WebContainers) (#20667)
  • Remove as: '*.css' from the @tailwindcss/turbopack setup in its README, because it breaks CSS modules (#20660)
  • Ignore <!-- and --> between top-level rules in CSS instead of throwing or swallowing the next rule (e.g. a { color: red } --> b { color: blue }) (#20665)
  • Ensure @tailwindcss/oxide-wasm32-wasi detects changed and new source files after the first scan (e.g. in WebContainers) (#20487)
  • Prevent type errors with skipLibCheck: false caused by imports of unshipped modules in the @tailwindcss/node type declarations (#20632)

[4.3.4] - 2026-11-02

Added

  • Add @tailwindcss/turbopack, a Turbopack loader for using Tailwind CSS with Next.js (#20367)

Fixed

  • Ensure watch mode detects changes to symlinked @source files whose real paths aren't otherwise scanned (#20356)
  • Ensure variants using @scope wrap generated utilities instead of nesting inside them (#20369)
  • Ensure nested @scope rules preserve their scoping semantics when flattened (#20369)
  • Preserve declarations directly inside @scope by wrapping them in :where(:scope) (#20369)
  • Ensure generated utilities include a space in empty var() fallbacks (e.g. var(--tw-blur,) → var(--tw-blur, )) (#20373)
  • Canonicalization: convert arbitrary breakpoint and container query variants to named equivalents (e.g. max-[64rem]:flex → max-lg:flex) (#20380)
  • Prevent @tailwindcss/vite from crashing on every edit under Vite's experimental bundledDev mode (#20379)
  • Ensure @tailwindcss/oxide falls back to WASM on platforms without native bindings (@tailwindcss/oxide-wasm32-wasi now installs on all platforms, but only loads when no native binding is available) (#20383)
  • Extract class candidates from Ruby %w and %W literals using angle brackets or custom delimiters (e.g. %w<flex>, %w|flex|), including in Slim and Haml templates (#20387)
  • Preserve whitespace in --default(…) values in functional @utility definitions (e.g. --default(box alphabetic) no longer becomes boxalphabetic) (#20392)
  • Ensure automatic source detection respects negation-based .gitignore files (e.g. /* followed by !/… patterns) (#20397)
  • Ensure root theme('…') namespace lookups in JavaScript plugins and config files return the full namespace object instead of the value of its DEFAULT key (#20399)
  • Skip ignored directories when generating watch globs instead of walking their contents on every rebuild (#20408)
  • Drop invalid UTF-8 candidates during class detection (#20389)
  • Prevent @tailwindcss/vite from forcing full-page reloads for scanned files that Vite does not handle as modules (e.g. .php files) (#20414)
  • Canonicalization: don't merge utilities that reference different theme variables set to CSS-wide keywords like unset (#20417)
  • Don't generate utilities when a modifier is used that would otherwise be silently ignored (e.g. rounded-sm/[5], shadow-sm/foo, stroke-2/50) (#20419)
  • Preserve and, or, and not inside selectors in supports-[…] variants (e.g. supports-[selector(a:not(.foo))]:flex) (#20420)
  • Don't warn about Angular's ::ng-deep and :host-context() when optimizing CSS (#20434)
  • Don't generate CSS for candidates containing an empty additional modifier (e.g. bg-red-500/50/ and group-hover/foo//bar:flex) (#20466)
  • Ensure min-*, max-*, and container query variants with decimal values are sorted numerically (e.g. min-[40.25rem] before min-[40.5rem]) (#20512)
  • Ensure CSS comments ending with \*/ are closed correctly instead of swallowing the CSS that follows (e.g. /* C:\temp\*/) (#20508)
  • Improve style invalidation performance of group-* and peer-* variants (#20513)
  • Ensure cached compilers release their loadModule and loadStylesheet callbacks after compilation (#20531)
  • Canonicalization: preserve & when moving a pseudo-element into * or ** (e.g. [&_::before]:flex → **:[&::before]:flex) (#20550)
  • Ensure the Set.prototype.intersection polyfill in canonicalizeCandidates(…) returns the intersection instead of the first set on Node.js < 22 (#20562)
  • Canonicalization: ensure inline theme(…) alphas with more than 2 decimals migrate to a percentage modifier with the same opacity (e.g. theme(colors.red.500/.12345) → text-red-500/[12.345%], not text-red-500/[12.345]) (#20563)
  • Canonicalization: preserve inline theme(…) alphas as an arbitrary percentage when a custom --opacity-* theme value would change the opacity (e.g. theme(colors.red.500/50%) → text-red-500/[50%] with --opacity-50: 10%) (#20563)
  • Ensure the @property fallback isn't applied in Safari versions that no longer support margin-trim: inline (#20569)
  • Treat viewport units like dvmin and svi and font-relative units like cap and rex as lengths in arbitrary values (e.g. text-[10dvmin] generates font-size instead of color) (#20516)

... (truncated)

Commits

Updates @testing-library/jest-dom from 7.0.1 to 8.0.0

Release notes

Sourced from @​testing-library/jest-dom's releases.

v8.0.0

8.0.0 (2026-11-19)

Features

BREAKING CHANGES

  • Support for vitest versions lower than 5 has been removed. Consumers must upgrade to a supported version.
Commits

Updates jsdom from 30.1.3 to 31.0.1

Release notes

Sourced from jsdom's releases.

v31.0.1

  • Improved performance of computed style reads, selector matching, CSS variable substitution, CSS shorthand updates, and focus handling on pages with many style rules. (@​scttcper)
  • Improved performance when building detached DOM trees and reading node.isConnected. (@​scttcper)
  • Fixed element.tabIndex handling of invalid and out-of-range tabindex="" values to use the element's default instead of returning zero or wrapping. Values with trailing non-digits now use their leading integer, so tabindex="1e2" yields 1 instead of 100. (@​rome-xi)
  • Fixed CSS ident() results containing spaces or leading digits losing their required escaping during serialization and variable substitution. (@​scttcper)
  • Fixed 'max-lines' values combining an integer and auto to serialize with the integer first, such as 3 auto.

v31.0.0

Breaking changes

  • Changed the optional canvas and image decoding backend from canvas to @napi-rs/canvas. Install @napi-rs/canvas v1.0.13 or later in the v1.x series alongside jsdom; installing canvas alone no longer enables this support. The new backend provides prebuilt Skia binaries on supported platforms, and rendering and encoded image bytes can differ. Projects using native canvas objects or custom font registration should follow the canvas migration guidance. Added WebP serialization through canvas.toDataURL() and canvas.toBlob(). Fixed image loading to wait for decoding before firing load, discard obsolete source requests, avoid refetching when dimensions change, and prevent failed images from drawing stale contents. Fixed canvas context and serialization behavior, including unsupported context types, read-only ctx.canvas, image-drawing exceptions, MIME type and quality normalization, and asynchronous null results from canvas.toBlob() for empty canvases or encoding failures. (@​Brooooooklyn)
  • Changed CSS parsing, selector matching, and computed styles to use a new integrated implementation, with substantially expanded support and faster selector queries and repeated style reads. This includes cascade layers, nesting, @scope, custom-property substitution and registration through @property and CSS.registerProperty(), typed attr(), conditional if(), shadow-tree styling with :host, ::slotted(), and ::part(), pseudo-element computed styles, and constructable stylesheets with document.adoptedStyleSheets and shadowRoot.adoptedStyleSheets. Fixed numerous cascade, shorthand, serialization, and default-style issues; computed declarations now stay live across DOM and stylesheet changes. CSS serialization and computed values can differ from previous releases.
  • Changed HTML and XML parsing to pause at blocking scripts until their required resources are ready. The JSDOM constructor, JSDOM.fromURL(), and JSDOM.fromFile() can now return partially parsed documents. Wait for DOMContentLoaded for the finished tree, or the window's load event for load-delaying resources, checking document.readyState first in case the event has already fired. XML syntax errors encountered after asynchronous parsing resumes are reported through the virtual console as "xml-parsing" errors.

Other changes

  • Added window.reportError(), which dispatches an error event and reports uncanceled errors to the virtual console. (@​sarankumar1325)
  • Added element.ariaBrailleLabel and element.ariaBrailleRoleDescription. (@​Kjubikstronk)
  • Fixed page-completion load events to fire only on the window. Use window.addEventListener("load", ...) or window.onload instead of listening on the document.
  • Fixed document.open(), including implicit calls from document.write(), to clear event listeners and handlers from the document, its descendants, and its window when replacing the input stream.
  • Fixed document.write() to process successive writes through the parser's input stream, preserve insertion points across nested scripts, and make completed text immediately visible. Script-created input streams now remain open until document.close().
  • Fixed dynamically inserted scripts to respect script.async = false execution order, use their source text and document from preparation time, and avoid executing after adoption into another document. Scripts parsed through inert fragment APIs no longer execute when subsequently inserted.
  • Fixed unrelated images, stylesheets, and frames being delayed behind scripts, and resource completion events firing before nested stylesheet imports finish. Cyclic imports no longer prevent completion, and <style> elements in shadow trees now fire load events.
  • Fixed window.stop() to cancel pending subresource and XMLHttpRequest requests in descendant frames and suppress completion events for canceled loads, while allowing subsequent requests to proceed.
  • Fixed repeated document.close() calls replaying readiness and load events, and incorrect iframe load events when reopening documents from event handlers.
  • Fixed memory leaks where pending request interceptor promises retained closed windows, introduced in v28.0.0.
  • Fixed focus remaining on elements that become non-focusable after DOM or style changes. Focus now moves asynchronously to the document's viewport, and element.blur() can release it immediately.
  • Fixed document.hasFocus() returning false before an element is focused or during focus transitions within the document, including inside frames.
  • Fixed \<template> parsing and template.innerHTML serialization in XML documents, including templates with namespace prefixes. (@​b84330808)
  • Fixed rect.toJSON() and performance.toJSON() to create their result objects in the method's realm instead of the host Node.js realm.
Commits
  • b76da26 31.0.1
  • 8a39b93 Track whether each node is connected
  • 463254b Speed up type and relative selector matching
  • afb7299 Fix max-lines serialization order
  • 574765e Fix tabIndex reflection of invalid and out-of-range values
  • 2cdcc44 Skip stylesheets that cannot apply to an element
  • 1ba3b6b Skip fetch cancellation test on affected Node versions
  • 40a0a14 Reduce CSS shorthand mutation overhead
  • 8a68119 Speed up CSS variable substitution
  • da2b11b Index pseudo-element rules apart from element rules
  • Additional commits viewable in compare view

Updates tailwindcss from 4.3.3 to 4.3.5

Release notes

Sourced from tailwindcss's releases.

v4.3.5

Fixed

  • Canonicalization: improve performance in projects with many functional variant values (e.g. a matchVariant plugin with thousands of values) (#20663)
  • Don't crash or create a fallback with the wrong color for a color-mix(…) without a color interpolation method (e.g. color-mix(var(--color-red-500)) or color-mix(currentcolor 50%, transparent)) (#20658, #20666)
  • Ensure @tailwindcss/oxide-wasm32-wasi loads instead of hanging forever (e.g...

    Description has been truncated

Bumps the npm group with 9 updates:

| Package | From | To |
| --- | --- | --- |
| [@nestjs/schedule](https://github.com/nestjs/schedule) | `12.0.2` | `12.0.4` |
| [@nestjs/throttler](https://github.com/nestjs/throttler) | `6.7.1` | `6.8.0` |
| [nestjs-pino](https://github.com/iamolegga/nestjs-pino) | `5.3.1` | `5.3.2` |
| [sanitize-html](https://github.com/apostrophecms/apostrophe/tree/HEAD/packages/sanitize-html) | `2.18.1` | `2.18.2` |
| [next](https://github.com/vercel/next.js) | `16.4.5` | `16.4.6` |
| [@tailwindcss/postcss](https://github.com/tailwindlabs/tailwindcss/tree/HEAD/packages/@tailwindcss-postcss) | `4.3.3` | `4.3.5` |
| [@testing-library/jest-dom](https://github.com/testing-library/jest-dom) | `7.0.1` | `8.0.0` |
| [jsdom](https://github.com/jsdom/jsdom) | `30.1.3` | `31.0.1` |
| [tailwindcss](https://github.com/tailwindlabs/tailwindcss/tree/HEAD/packages/tailwindcss) | `4.3.3` | `4.3.5` |


Updates `@nestjs/schedule` from 12.0.2 to 12.0.4
- [Release notes](https://github.com/nestjs/schedule/releases)
- [Commits](nestjs/schedule@12.0.2...12.0.4)

Updates `@nestjs/throttler` from 6.7.1 to 6.8.0
- [Release notes](https://github.com/nestjs/throttler/releases)
- [Changelog](https://github.com/nestjs/throttler/blob/master/CHANGELOG.md)
- [Commits](nestjs/throttler@v6.7.1...v6.8.0)

Updates `nestjs-pino` from 5.3.1 to 5.3.2
- [Release notes](https://github.com/iamolegga/nestjs-pino/releases)
- [Commits](iamolegga/nestjs-pino@5.3.1...5.3.2)

Updates `sanitize-html` from 2.18.1 to 2.18.2
- [Changelog](https://github.com/apostrophecms/apostrophe/blob/main/packages/sanitize-html/CHANGELOG.md)
- [Commits](https://github.com/apostrophecms/apostrophe/commits/sanitize-html@2.18.2/packages/sanitize-html)

Updates `next` from 16.4.5 to 16.4.6
- [Release notes](https://github.com/vercel/next.js/releases)
- [Commits](vercel/next.js@v16.4.5...v16.4.6)

Updates `@tailwindcss/postcss` from 4.3.3 to 4.3.5
- [Release notes](https://github.com/tailwindlabs/tailwindcss/releases)
- [Changelog](https://github.com/tailwindlabs/tailwindcss/blob/main/CHANGELOG.md)
- [Commits](https://github.com/tailwindlabs/tailwindcss/commits/v4.3.5/packages/@tailwindcss-postcss)

Updates `@testing-library/jest-dom` from 7.0.1 to 8.0.0
- [Release notes](https://github.com/testing-library/jest-dom/releases)
- [Changelog](https://github.com/testing-library/jest-dom/blob/main/CHANGELOG.md)
- [Commits](testing-library/jest-dom@v7.0.1...v8.0.0)

Updates `jsdom` from 30.1.3 to 31.0.1
- [Release notes](https://github.com/jsdom/jsdom/releases)
- [Commits](jsdom/jsdom@v30.1.3...v31.0.1)

Updates `tailwindcss` from 4.3.3 to 4.3.5
- [Release notes](https://github.com/tailwindlabs/tailwindcss/releases)
- [Changelog](https://github.com/tailwindlabs/tailwindcss/blob/main/CHANGELOG.md)
- [Commits](https://github.com/tailwindlabs/tailwindcss/commits/v4.3.5/packages/tailwindcss)

---
updated-dependencies:
- dependency-name: "@nestjs/schedule"
  dependency-version: 12.0.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: npm
- dependency-name: "@nestjs/throttler"
  dependency-version: 6.8.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: npm
- dependency-name: nestjs-pino
  dependency-version: 5.3.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: npm
- dependency-name: sanitize-html
  dependency-version: 2.18.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: npm
- dependency-name: next
  dependency-version: 16.4.6
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: npm
- dependency-name: "@tailwindcss/postcss"
  dependency-version: 4.3.5
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: npm
- dependency-name: "@testing-library/jest-dom"
  dependency-version: 8.0.0
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: npm
- dependency-name: jsdom
  dependency-version: 31.0.1
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: npm
- dependency-name: tailwindcss
  dependency-version: 4.3.5
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: npm
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency npm npm dependency updates labels Nov 22, 2026
@kneshi
kneshi merged commit 4bed47f into main Nov 22, 2026
14 checks passed
@kneshi
kneshi deleted the dependabot/npm_and_yarn/npm-1764b919b6 branch November 22, 2026 17:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency npm npm dependency updates

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant