chore(deps): bump the all group with 10 updates

[dependabot]

Bumps the all group with 10 updates:

Package	From	To
@asciidoctor/core	4.0.0	4.0.8
@modelcontextprotocol/sdk	1.29.0	1.30.0
js-yaml	4.1.1	5.2.3
@types/node	22.19.17	26.2.0
@vitest/coverage-v8	2.1.9	4.1.10
jsdom	29.0.2	30.0.1
playwright	1.59.1	1.62.1
tsx	4.21.0	4.23.12
typescript	5.9.3	7.0.2
vitest	2.1.9	4.1.10

Updates @asciidoctor/core from 4.0.0 to 4.0.8

Release notes

Sourced from @​asciidoctor/core's releases.

v4.0.8

Summary

Release meta

Released on: 2026-08-06 Released by: ggrossetie Published by: GitHub

Logs: full diff

Changelog

Improvements

• Export Severity ({ DEBUG, INFO, WARN, ERROR, FATAL, UNKNOWN }) from @asciidoctor/core’s public API (index.jsandbrowser.js). Previously the constant existed only inside logging.jsand was not re-exported, so a custom logger built withLoggerManager.newLogger(name, { add })had no way to compare the (already-numeric)severity` argument against named levels without redeclaring the map by hand
• Wire up the pipe constructor option on Logger (new Logger({ pipe })), mirroring Ruby’s Logger.new(logdev). It previously had no effect — _writeln() always wrote to process.stderr/console.error regardless of the option. pipe now accepts anything with a write(line) method, or a function called as (line, severity) — the numeric severity lets a function-style pipe route by level (e.g. console.error for ERROR+, console.warn for WARN) without subclassing Logger, overriding add(), or touching the internal _writeln() method

Infrastructure

• Add compile-only type tests (test/types/logging.test-d.ts) covering the Logger constructor’s pipe option (both the object {write} form and the severity-aware (line, severity) function form, plus a negative @ts-expect-error case for an invalid pipe value) and LoggerManager.newLogger()’s add/postConstruct` override shape

v4.0.7

Summary

Release meta

Released on: 2026-07-31 Released by: ggrossetie Published by: GitHub

Logs: full diff

Changelog

Bug Fixes

• Fix PathResolver#partitionPath()/#expandPath() dropping a slash from file:/// (and other triple-slash) URIs, turning file:///Users/guillaume/foo.png into file://Users/guillaume/foo.png — a malformed URL whose "host" (Users) browsers reject as Not allowed to load local resource. UriSniffRx only ever matches up to 2 slashes after the scheme, so for a triple-slash URI the 3rd slash is left in the remainder to partition into segments; partitionPath() unconditionally filtered out all empty segments (including that leading one), silently discarding the information needed to reconstruct the slash on joinPath(). It now mirrors Ruby’s String#split('/') semantics and drops only trailing empty segments, keeping leading ones intact

v4.0.6

Summary

Release meta

Released on: 2026-07-26 Released by: ggrossetie Published by: GitHub

... (truncated)

Changelog

Sourced from @​asciidoctor/core's changelog.

== v4.0.8 (2026-08-06)

Improvements::

• Export Severity ({ DEBUG, INFO, WARN, ERROR, FATAL, UNKNOWN }) from @asciidoctor/core's public API (index.js and browser.js). Previously the constant existed only inside logging.js and was not re-exported, so a custom logger built with LoggerManager.newLogger(name, { add }) had no way to compare the (already-numeric) severity argument against named levels without redeclaring the map by hand
• Wire up the pipe constructor option on Logger (new Logger({ pipe })), mirroring Ruby's Logger.new(logdev). It previously had no effect — _writeln() always wrote to process.stderr/console.error regardless of the option. pipe now accepts anything with a write(line) method, or a function called as (line, severity) — the numeric severity lets a function-style pipe route by level (e.g. console.error for ERROR+, console.warn for WARN) without subclassing Logger, overriding add(), or touching the internal _writeln() method

Infrastructure::

• Add compile-only type tests (test/types/logging.test-d.ts) covering the Logger constructor's pipe option (both the object {write} form and the severity-aware (line, severity) function form, plus a negative @ts-expect-error case for an invalid pipe value) and LoggerManager.newLogger()'s add/postConstruct override shape

== v4.0.7 (2026-07-31)

Bug Fixes::

• Fix PathResolver#partitionPath()/#expandPath() dropping a slash from file:/// (and other triple-slash) URIs, turning file:///Users/guillaume/foo.png into file://Users/guillaume/foo.png — a malformed URL whose "host" (Users) browsers reject as Not allowed to load local resource. UriSniffRx only ever matches up to 2 slashes after the scheme, so for a triple-slash URI the 3rd slash is left in the remainder to partition into segments; partitionPath() unconditionally filtered out all empty segments (including that leading one), silently discarding the information needed to reconstruct the slash on joinPath(). It now mirrors Ruby's String#split('/') semantics and drops only trailing empty segments, keeping leading ones intact

== v4.0.6 (2026-07-26)

Bug Fixes::

• Fix AbstractNode#imageUri() no longer percent-encoding spaces in a data: URI image target (e.g. image::data:image/svg+xml,<svg ...><text>a b</text></svg>[]), a regression from the data URI image target support added for inline SVG embedding. That change short-circuited imageUri() for any data: target by returning it unchanged, bypassing the space-encoding that normalizeWebPath() still applies for every other URI-ish target — and that upstream Asciidoctor (Ruby) also applies, since image_uri has no data:-specific early return at all. imageUri() now runs data: targets through encodeSpacesInUri() before returning them, matching Ruby's output byte-for-byte, while still avoiding the spurious could not retrieve image data from URI warning the earlier fix was meant to prevent
• Fix tasks/changelog.js notes (used to generate GitHub release notes) leaving AsciiDoc attribute references such as {uri-repo}/issues/1857[#1857](https://github.com/asciidoctor/asciidoctor.js/issues/1857) unresolved in the generated Markdown. extractReleaseNotes used to extract the raw AsciiDoc section for a release and convert only that fragment to Markdown, losing the :uri-repo: attribute definition from the changelog header in the process. The whole changelog is now converted to Markdown once, and the release section is extracted from the resulting Markdown instead, so attribute references resolve correctly
• Type Logger#warn()/#debug()/#info()/#error()/#fatal()/#unknown()/#log() (and the matching MemoryLogger methods) with an optional progname/pn parameter instead of a required one. The generated .d.ts previously declared both arguments as mandatory, so calling doc.getLogger().warn(doc.messageWithContext(...)) with a single argument — the documented pattern for logging from an extension — was flagged by editors as "expected 2 arguments" even though it is valid at runtime; the error surfaced because getLogger() resolves to the LoggerLike union (Logger | MemoryLogger | NullLogger | Console) and TypeScript requires a call to satisfy every member's signature
• Type messageWithContext()/createLogMessage() on Document, ConverterBase, PathResolver, and Table.ParserContext (and the static equivalents on Parser). These are installed at runtime by the applyLogging() mixin (logging.js) after the class body closes, so tsc's JSDoc-based declaration emit never picked them up — doc.messageWithContext(...), the pattern shown in the extensions guide, previously had no type at all on the public API surface

Infrastructure::

• Add compile-only type tests for the Logger/MemoryLogger/NullLogger API and the LoggerLike union (test/types/logging.test-d.ts, run by npm run test:types), covering every shorthand log method across single- and two-argument call forms, the applyLogging() consumers listed above, and negative @ts-expect-error checks (e.g. fatal()/unknown() are intentionally unavailable on the raw LoggerLike union because Console has neither, but resolve once narrowed away from Console)

== v4.0.5 (2026-07-21)

Bug Fixes::

• Fix Document#getLogger() (and getLogger() on any prototype augmented by applyLogging(): Converter, Parser, PathResolver, Table.ParserContext) silently ignoring a per-instance override of the logger getter, even though its own JSDoc describes it as "a method alias for the logger getter". applyLogging() (logging.js) installed getLogger as a fixed arrow function with no this binding, so it always fell back to the global LoggerManager.logger instead of resolving through this.logger — breaking the logger option to convert()/load() once the async-local-storage scope from load() had closed (i.e. during doc.convert(), when most block/inline converters and extensions run). Extensions/converters that follow the documented doc.getLogger() pattern (e.g. to log a warning with messageWithContext()) would have those messages silently escape a caller-supplied logger such as a MemoryLogger
• Fix inline macro extensions ignoring the contentModel/positionalAttrs (or the DSL contentModel()/positionalAttributes()/resolveAttributes() setters) configuration, so the macro's bracket content was never parsed into named/positional attributes and always ended up as a raw string in attributes.text instead — e.g. registry.inlineMacro(function () { this.named('emoji'); this.positionalAttributes('size'); this.process(...) }) produced { text: '2x' } instead of { '1': '2x', size: '2x' } for emoji:smile[2x]. Substitutors#subMacros (the inline macro substitution path in substitutors.js) read the extension config with keys that were never populated by the DSL/static config ({uri-repo}/issues/1857#1857)

Improvements::

• Extension Processor config keys (contentModel, positionalAttrs, defaultAttrs) now use camelCase consistently across every registration style — the DSL setters, class-based static config, and the block/inline macro substitution code that reads them. The legacy Ruby-style snake_case keys (content_model, positional_attrs, pos_attrs, default_attrs) are still accepted for backward compatibility when a processor class declares its config directly (static config = { content_model: 'attributes' } or MyProcessor.config = { content_model: 'attributes' }). Processor.config also gained a static setter, so assigning a static config object after the class declaration (as shown in the BlockMacroProcessor/InlineMacroProcessor JSDoc examples) no longer throws a TypeError
• Type AbstractNode#logger/#getLogger() and Reader/PreprocessorReader#logger/#getLogger()/#createLogMessage() with the new LoggerLike union (Logger | MemoryLogger | NullLogger | Console, exported from logging.js) instead of a bare object. In reader.js, fields and helper methods that are only ever touched within the class that declares them (Reader's cursor mark, PreprocessorReader's include/conditional-directive bookkeeping) are now real JS #private members instead of _-prefixed by convention; the remaining _-prefixed fields that PreprocessorReader must read/reassign (_dir, _document, _lines, …) are annotated @internal so they're stripped from the generated public .d.ts without changing runtime access

== v4.0.4 (2026-07-15)

Improvements::

• Declare the instance form ("style 3") of the Registry extension registration methods in the TypeScript typings. The runtime has always accepted an already-constructed processor (registry.includeProcessor(new MyIncludeProcessor())) in addition to the class and registration-function forms, but the 4.0 typings only declared the latter two, forcing consumers such as the VS Code AsciiDoc extension to augment the module by hand. preprocessor, treeProcessor, postprocessor, includeProcessor, docinfoProcessor, block, blockMacro and inlineMacro now expose an overload accepting a processor instance (the syntax processor methods also accept the optional explicit name), and the compile-only type tests cover the instance form
• Type the filter callback accepted by AbstractBlock#findBy (and its query alias) as (node: AbstractBlock) => boolean | string instead of the bare Function, so the candidate node passed to the callback resolves as an AbstractBlock without casts — both in the two-argument form and in the findBy(callback) shorthand
• Type the reader received by preprocessor and include processor callbacks as PreprocessorReader instead of Reader, and export PreprocessorReader from the package root. Preprocessor#process, IncludeProcessor#process and the matching DSL process(fn) callbacks actually receive a PreprocessorReader at runtime, so its members (pushInclude, getIncludeDepth, …) now resolve without casts or manual module augmentation

... (truncated)

Commits

• 576027b 4.0.8
• b4d778f test(core): add type tests for Logger pipe/newLogger overrides; document _wri...
• db99033 fix(core): forward severity to function-style Logger pipe
• 9336a50 feat(core): export Severity and wire up Logger pipe option
• b533033 chore: use union merge driver for CHANGELOG.adoc
• de80861 4.0.7
• fae3271 fix(core): preserve leading slash when partitioning triple-slash URIs
• 4c53894 4.0.6
• 8dc9784 fix(core): encode spaces in data: URI image targets
• f1c93e5 fix(core): type Logger progname as optional, close applyLogging() type gaps
• Additional commits viewable in compare view

Updates @modelcontextprotocol/sdk from 1.29.0 to 1.30.0

Release notes

Sourced from @​modelcontextprotocol/sdk's releases.

1.30.0

What's Changed

• fix(server): prioritize zod issues and format them by @​mozmo15 in modelcontextprotocol/typescript-sdk#1503
• chore(ci): switch publish to OIDC trusted publishing by @​felixweinberger in modelcontextprotocol/typescript-sdk#1839
• Add end-to-end test suite by @​felixweinberger in modelcontextprotocol/typescript-sdk#2167
• v1 stdio buffer limit by @​KKonstantinov in modelcontextprotocol/typescript-sdk#2239
• fix: support Zod 3.25 method literals by @​mattzcarey in modelcontextprotocol/typescript-sdk#2368
• Validate Content-Type by parsed media type instead of substring match (v1.x) by @​felixweinberger in modelcontextprotocol/typescript-sdk#2444
• fix: send SSE keep-alive comment frames from Streamable HTTP server transport (v1.x) by @​mattzcarey in modelcontextprotocol/typescript-sdk#2538
• fix(deps): widen @​hono/node-server past GHSA-frvp-7c67-39w9 by @​arimu1 in modelcontextprotocol/typescript-sdk#2549
• Fix SSE keep-alive timer lifecycle in Streamable HTTP server transport (v1.x) by @​felixweinberger in modelcontextprotocol/typescript-sdk#2547
• chore: bump version to 1.30.0 by @​felixweinberger in modelcontextprotocol/typescript-sdk#2563

New Contributors

• @​mozmo15 made their first contribution in modelcontextprotocol/typescript-sdk#1503
• @​arimu1 made their first contribution in modelcontextprotocol/typescript-sdk#2549

Full Changelog: modelcontextprotocol/typescript-sdk@v1.29.0...1.30.0

Commits

• 2d889f2 chore: bump version to 1.30.0 (#2563)
• e3f3daa Fix SSE keep-alive timer lifecycle in Streamable HTTP server transport (v1.x)...
• bb5a718 fix(deps): widen @​hono/node-server past GHSA-frvp-7c67-39w9 (#2549)
• 1dad263 fix: send SSE keep-alive comment frames from Streamable HTTP server transport...
• 69749aa Validate Content-Type by parsed media type instead of substring match (v1.x) ...
• 369513d fix: support Zod 3.25 method literals (#2368)
• e7ee57c v1 stdio buffer limit (#2239)
• c36e1ef Add end-to-end test suite (#2167)
• bf1e022 chore(ci): switch publish to OIDC trusted publishing (#1839)
• 9edbab7 fix(server): prioritize zod issues and format them (#1503)
• See full diff in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​modelcontextprotocol/sdk since your current version.

Updates js-yaml from 4.1.1 to 5.2.3

Changelog

Sourced from js-yaml's changelog.

[5.2.3] - 2026-08-01

Fixed

• Prevent prototype fallback when resolving tags and mapping entries, #782.
• Resolve !!timestamp years 0000-0099 correctly, #775.
• Preserve implicit null mapping values before document markers and reject unpaired mapping event streams, #784.
• Preserve folded scalar values with tab-indented lines when round-tripping a parsed AST through present(); dump() and loading are unaffected, #780.

[5.2.2] - 2026-07-24

Fixed

• Quote flow scalars where a colon precedes a flow indicator, #773.

Security

• Avoid exponential parsing time for nested flow sequence pairs.

[5.2.1] - 2026-07-02

Fixed

• Add Map support to !!omap (should work when realMapTag used)

Security

• Remove quadratic complexity from !!omap addItem. Regression from v5 (usually not critical, because YAML11_SCHEMA is not default anymore).

4.3.0, 3.15.0 - 2026-06-27

Security

• Backported maxTotalMergeKeys option.

[5.2.0] - 2026-06-26

Added

• Added maxTotalMergeKeys (10000) loader option to limit the total number of keys processed by YAML merge (<<) across one load() / loadAll() call.
• Added maxAliases (-1) loader option to limit the number of YAML aliases per document.

Removed

• maxMergeSeqLength replaced with maxTotalMergeKeys for limiting YAML merge processing.

Fixed

• Round-trip of integers with exponential form (>= 1e21)

[5.1.0] - 2026-06-23

... (truncated)

Commits

• 6740445 5.2.3 released
• 94e766d Update changelog
• c3bd7ca Polish previous commit, #780
• 00209b6 presenter: treat a tab-indented line in a folded scalar as more-indented (#780)
• 40fcb4f Fix missing mapping values before document markers and reject unpaired mappin...
• 49280f3 Fix !!timestamp resolution for years 0000-0099, #775
• 355dc96 fix: prevent prototype fallback in tag and harden object lookups, #782 (than...
• d524f83 docs: add contributing guidelines
• 3c29559 5.2.2 released
• 3e5240f parser: avoid reparsing flow sequence pair keys
• Additional commits viewable in compare view

Updates @types/node from 22.19.17 to 26.2.0

Commits

• See full diff in compare view

Updates @vitest/coverage-v8 from 2.1.9 to 4.1.10

Release notes

Sourced from @​vitest/coverage-v8's releases.

v4.1.10

   🐞 Bug Fixes

• browser: Check fs access in builtin commands [backport to v4]  -  by @​hi-ogawa, Hiroshi Ogawa and OpenCode (claude-opus-4-8) in vitest-dev/vitest#10680 (5c18d)
• vm: Fix external module resolve error with deps optimizer query for encoded URI [backport to v4]  -  by @​SveLil and @​hi-ogawa in vitest-dev/vitest#10661 (bae52)

    View changes on GitHub

v4.1.9

🐞 Bug Fixes

• Fix importOriginal with optimizer and query import [backport to v4] - by Hiroshi Ogawa, David Harris, Codexand Vladimir in vitest-dev/vitest#10546 (a5180)
• browser:
  • Wait for orchestrator readiness before resolving browser sessions [backport to v4] - by Vladimir and Séamus O'Connor in vitest-dev/vitest#10555 (7fb29)
  • Wait for iframe tester readiness before preparing [backport to v4] - by Vladimir and Séamus O'Connor in vitest-dev/vitest#10497 and vitest-dev/vitest#10556 (fbc62)
• mocker:
  • Hoist vi.mock() for vite-plus/test imports [backport to v4] - by Hiroshi Ogawa, LongYinan, Claude Opus 4.8 and Vladimir in vitest-dev/vitest#10548 (2c955)
• pool:
  • Prevent test run hang on worker crash [backport to v4] - by Ari Perkkiö and Jattioui Ismail in vitest-dev/vitest#10543 and vitest-dev/vitest#10564 (934b0)

View changes on GitHub

v4.1.8

   🐞 Bug Fixes

• browser:
  • Disable client cdp API when allowWrite/allowExec: false [backport to v4]  -  by @​hi-ogawa and Codex in vitest-dev/vitest#10450 (e4067)
  • Remove orphaned Playwright route when same module is mocked via multiple ids [backport to v4]  -  by @​toxik and @​Zelys-DFKH in vitest-dev/vitest#10474 (675b4)

    View changes on GitHub

v4.1.7

   🐞 Bug Fixes

• runner: Limit concurrency per task branch in addition to per leaf callbacks (backport)  -  by @​hi-ogawa in vitest-dev/vitest#10384 (4f0f2)

    View changes on GitHub

v4.1.6

   🐞 Bug Fixes

• browser: Provide project reference in ToMatchScreenshotResolvePath  -  by @​macarie and @​sheremet-va in vitest-dev/vitest#10138 (31882)
• Global sequence.concurrent: true with top-level test(..., { concurrent: false }) + depreacte sequential test API and options  -  by @​hi-ogawa, Codex and @​sheremet-va in vitest-dev/vitest#10196 (2847d)
• browser: Simplify orchestrator otel carrier  -  by @​hi-ogawa in vitest-dev/vitest#10285 (18af9)

   🏎 Performance

• Stringify diff objects only once  -  by @​sheremet-va in vitest-dev/vitest#10276 (9f7b1)

    View changes on GitHub

... (truncated)

Commits

• db616d2 chore: release v4.1.10 (#10718)
• a7a61e7 chore: release v4.1.9 (#10598)
• e61f2dd chore: release v4.1.8
• e4067b3 fix(browser): disable client cdp API when allowWrite/allowExec: false [ba...
• a09d472 chore: release v4.1.7
• a8fd24c chore: release v4.1.6
• e399846 chore: release v4.1.5
• ac04bac chore: release v4.1.4
• 2dc0d62 chore: release v4.1.3
• fc6f482 chore: release v4.1.2
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​vitest/coverage-v8 since your current version.

Updates jsdom from 29.0.2 to 30.0.1

Release notes

Sourced from jsdom's releases.

v30.0.1

• Fixed getComputedStyle() with calc() and other functions throwing an exception, which regressed in v30.0.0. (@​asamuzaK)
• Sped up up range operations on large documents (@​leonidaz)

v30.0.0

Breaking changes:

• Node.js minimum version raised to ^22.22.2 || ^24.15.0 || >=26.0.0.

Other changes:

• Added CSS.escape() and CSS.supports() functions. (@​asamuzaK)
• Added 'background-position-x' and 'background-position-y' CSS properties. (@​olagokemills)
• Fixed getComputedStyle() to convert length values into pixels. (@​asamuzaK)
• Fixed CSS function serialization, e.g., in the return value of getPropertyValue(). (@​asamuzaK)
• Fixed the type of error thrown by document.evaluate() (@​dokson)

v29.1.1

• Fixed 'border-radius' computed style serialization. (@​asamuzaK)
• Fixed computed style computation when using 'background-origin' and 'background-clip' CSS properties. (@​asamuzaK)
• Significantly optimized initial calls to getComputedStyle(), before the cache warms up. (@​asamuzaK)

v29.1.0

• Added basic support for the ratio CSS type. (@​asamuzaK)
• Fixed getComputedStyle() sometimes returning outdated results after CSS was modified. (@​asamuzaK)

Commits

• 6584485 30.0.1
• 0c51df6 Update dependencies and dev dependencies
• 32adb34 Bump @​asamuzakjp/dom-selector
• 70f014a Speed up range operations on large documents
• 250d7ee Partially fix getComputedStyle with calc()
• 20a01fc 30.0.0
• 8c8e583 Precompute WPT expectation matches
• f32245c Bump Node.js floor and dependencies
• 03ef23b Add background-position longhands
• ded056f Test CSS.escape() with numeric IDs
• Additional commits viewable in compare view

Updates playwright from 1.59.1 to 1.62.1

Release notes

Sourced from playwright's releases.

v1.62.1

Bug Fixes

• #41989 [Regression]: tsconfig "extends" bare specifier isn't resolved via node_modules walk-up like tsc (fatal since 1.62)
• #41998 [Regression]: directory-form tsconfig project references ("path": "../pkg") fail to resolve (fatal since 1.62)
• #41985 Accessibility snapshot drops button name when text is nested inside spans with aria-hidden SVG
• #42000 [Regression]: page.evaluate() arg of a branded primitive type (string & { brand }) no longer type-checks since 1.62
• #42013 [BUG]Image-type actionable elements are not presented in the snapshot.

v1.62.0

🧱 New component testing model

Component testing moves to a stories and galleries model. A story wraps your component in one specific scenario — hard-coded props, mock data, providers — and a gallery page that you serve renders stories on demand. The new fixtures.mount() fixture navigates to the gallery, mounts a story by id, and returns a Locator scoped to the story's root element:

test('click should expand', async ({ mount }) => {
  const component = await mount('components/Expandable/Stateful');
  await component.getByRole('button').click();
  await expect(component.getByTestId('expanded')).toHaveValue('true');
});

Pass a story type as a template argument to type-check its props, and use update(props) / unmount() on the returned locator to re-render or tear down within a test.

🛑 Cancel operations with AbortSignal

Most operations and web-first assertions now accept a signal option that takes an AbortSignal, letting you cancel long-running actions, navigations, waits, and assertions:

const controller = new AbortController();
setTimeout(() => controller.abort(), 1000);
await page.getByRole('button', { name: 'Submit' }).click({ signal: controller.signal });
await expect(page.getByText('Done')).toBeVisible({ signal: controller.signal });

Providing a signal does not disable the default timeout; pass timeout: 0 to disable it.

🖼️ WebP screenshots

expect(page).toHaveScreenshot() and expect(locator).toHaveScreenshot() can now store snapshots in the WebP format — just give the snapshot a .webp name:

// Visual comparisons store the golden snapshot as lossless WebP.
await expect(page).toHaveScreenshot('homepage.webp');
// Standalone screenshots can trade quality for size with lossy WebP.
await page.screenshot({ path: 'homepage.webp', quality: 50 });
</tr></table>

... (truncated)

Commits

• 26a9e47 cherry-pick(#42043): docs: release notes for v1.62 Python, Java, and .NET (#4...
• 0a81d5d cherry-pick(#42040): docs(release-notes): mention the isolated headless clipb...
• 8376826 cherry-pick(#42034): fix(aria): keep icon-only clickable elements in ai snaps...
• 66c5cc9 chore: mark v1.62.1 (#42020)
• 9672bc3 cherry-pick(#42009): fix(types): support branded primitives in evaluate argum...
• 4325804 cherry-pick(#41988): fix(aria): preserve names from collapsed text contributors
• 9632f8e cherry-pick(#42005): fix(tsconfig): do not throw when "extends"/"references" ...
• e3950d9 chore: mark v1.62.0 (#41981)
• f07e0f7 cherry-pick(#41940): docs: release notes for v1.62 (#41967)
• 05a306c cherry-pick(#41964): Revert "feat(routeFromHar): add interceptAPIRequests opt...
• Additional commits viewable in compare view

Updates tsx from 4.21.0 to 4.23.12

Release notes

Sourced from tsx's releases.

v4.23.12

4.23.12 (2026-08-10)

Bug Fixes

• shim import.meta when tokens are split by comments or newlines (#829) (ed9d330), closes #828

---

This release is also available on:

• npm package (@​latest dist-tag)

v4.23.11

4.23.11 (2026-08-07)

Bug Fixes

• preserve async ESM require fallback (55cbece)

---

This release is also available on:

• npm package (@​latest dist-tag)

v4.23.10

4.23.10 (2026-08-07)

Bug Fixes

• support nyc coverage discovery (#710) (ec1bcd5)

---

This release is also available on:

• npm package (@​latest dist-tag)

v4.23.9

4.23.9 (2026-08-06)

Bug Fixes

• map Node test locations (2f55884)
• support data URLs in tsImport (b94f46f)

---

This release is also available on:

• npm package (@​latest dist-tag)

v4.23.8

... (truncated)

Commits

• ed9d330 fix: shim import.meta when tokens are split by comments or newlines (#829)
• 651f5be test: cover CommonJS TypeScript import.meta paths
• bd3bc64 test: cover CommonJS loader source fallback
• 55cbece fix: preserve async ESM require fallback
• 6c5ba85 docs: document CommonJS default interop
• ec1bcd5 fix: support nyc coverage discovery (#710)
• b6e5b48 docs: clarify CommonJS default imports
• 2f55884 fix: map Node test locations
• de935d5 docs: document Node source-map stack formatting
• b94f46f fix: support data URLs in tsImport
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for tsx since your current version.

Updates typescript from 5.9.3 to 7.0.2

Release notes

Sourced from typescript's releases.

TypeScript 6.0.3

For release notes, check out the release announcement blog post.

• fixed issues query for TypeScript 6.0.0 (Beta).
• fixed issues query for TypeScript 6.0.1 (RC).
• fixed issues query for TypeScript 6.0.2 (Stable).
• fixed issues query for TypeScript 6.0.3 (Stable).

Downloads are available on:

• npm

TypeScript 6.0

For release notes, check out the release announcement blog post.

• fixed issues query for TypeScript 6.0.0 (Beta).
• fixed issues query for TypeScript 6.0.1 (RC).
• fixed issues query for TypeScript 6.0.2 (Stable).

Downloads are available on:

• npm

TypeScript 6.0.1 RC

For release notes, check out the release announcement blog post.

• fixed issues query for TypeScript 6.0.0 (Beta).
• fixed issues query for TypeScript 6.0.1 (RC).

Downloads are available on:

• npm

TypeScript 6.0 Beta

For release notes, check out the release announcement.

• fixed issues query for Typescript 6.0.0 (Beta).

Downloads are available on:

• npm

Commits

• See full diff in compare view

Maintainer changes

This version was pushed to npm by microsoft1es, a new releaser for typescript since your current version.

Updates vitest from 2.1.9 to 4.1.10

Release notes

Sourced from vitest's releases.

v4.1.10

   🐞 Bug Fixes

• browser: Check fs access in builtin commands [backport to v4]  -  by @​hi-ogawa, Hiroshi Ogawa and OpenCode (claude-opus-4-8) in vitest-dev/vitest#10680 (5c18d)
• vm: Fix external module resolve error with deps optimizer query for encoded URI [backport to v4]  -  by @​SveLil and @​hi-ogawa in vitest-dev/vitest#10661 (bae52)

    View changes on GitHub

v4.1.9

🐞 Bug Fixes

• Fix importOriginal with optimizer and query import [backport to v4] - by Hiroshi Ogawa, David Harris, Codexand Vladimir in vitest-dev/vitest#10546 (a5180)
• browser:
  • Wait for orchestrator readiness before resolving browser sessions [backport to v4] - by Vladimir and Séamus O'Connor in vitest-dev/vitest#10555 (7fb29)
  • Wait for iframe tester readiness before preparing [backport to v4] - by Vladimir and Séamus O'Connor in vitest-dev/vitest#10497 and vitest-dev/vitest#10556 (fbc62)
• mocker:
  • Hoist vi.mock() for vite-plus/test imports [backport to v4] - by Hiroshi Ogawa, LongYinan, Claude Opus 4.8 and Vladimir in vitest-dev/vitest#10548 (2c955)
• pool:
  • Prevent test run hang on worker crash [backport to v4] - by Ari Perkkiö and Jattioui Ismail in vitest-dev/vitest#10543 and vitest-dev/vitest#10564 (934b0)

View changes on GitHub

v4.1.8

   🐞 Bug Fixes

• browser:
  • Disable client cdp API when allowWrite/allowExec: false [backport to v4]  -  by @​hi-ogawa and Codex in vitest-dev/vitest#10450 (e4067)
  • Remove orphaned Playwright route when same module is mocked via multiple i...

    Description has been truncated