Bump the everything-else group with 11 updates

[dependabot]

⚠️ Dependabot is rebasing this PR ⚠️

Rebasing might not happen immediately, so don't worry if this takes some time.

Note: if you make any changes to this PR yourself, they will take precedence over the rebase.

---

Updated Aspire.Hosting.Azure.Storage from 13.6.0 to 13.6.1.

Release notes

Sourced from Aspire.Hosting.Azure.Storage's releases.

13.6.1

What's New in Aspire 13.6.1

Patch release for Aspire 13.6 that reduces dashboard CPU usage during sustained metric ingestion, restores scrolling in the Metrics tree, improves dashboard navigation, fixes container exec watch failures, and ensures session-scoped containers are cleaned up when stopping .NET AppHosts on Windows.

🐛 Fixes

• 📊 Dashboard CPU usage could increase during long-running metric ingestion — Metric retention repeatedly scanned retained history on every insertion, causing steadily increasing CPU usage even with a fixed workload. Cleanup now skips dimensions below capacity and removes only the oldest surplus points when needed. Existing retention limits and exemplar behavior are unchanged, and no configuration changes are required. Regression introduced in 13.6. Fixes #​20725. (#​20747, backport of #​20736, @​JamesNK)

• 📈 The Metrics tree could not be scrolled — The meter and instrument tree now scrolls when it exceeds the viewport, allowing you to reach and select instruments below the fold. Regression introduced in 13.6. Fixes #​20728. (#​20762, backport of #​20758, @​heyysiri)

• 🧭 Dashboard navigation could fail after a browser disconnect — Pending page-state updates now persist session state before navigating and skip navigation when the browser has disconnected, avoiding an unhandled navigation failure. The navigation rail's overflow button also has consistent sizing, icon alignment, and hover styling in expanded and collapsed layouts and both light and dark themes. (#​20545, backport of #​20527, @​JamesNK)

• 🖥️ Container exec watches could terminate shortly after AppHost startup — A stalled DCP watch connection could produce a critical Watch task over Kubernetes ContainerExec resources terminated unexpectedly error and stop subsequent terminal state and log updates from being observed. Watch connection attempts now retry after timeouts, and periodic restarts correctly recreate connections without swallowing unrelated cancellation. Regression introduced in 13.6.0. (#​20664, backport of #​20466, @​radical)

• 🪟 Session-scoped containers could remain running after stopping a .NET AppHost on Windows — AppHosts launched through dotnet run or dotnet watch now allow DCP to finish resource cleanup during shutdown, including existing Ctrl+C and aspire stop flows. Persistent resources remain unaffected, while direct .NET launches and TypeScript/polyglot AppHosts retain their existing process protection. Fixes #​20495. (#​20514, backport of #​20494, @​danegsta)

---

Full Changelog: v13.6.0...v13.6.1

Full commit: 3751e615ad660621f2a7aa4c390ef48e08a0eed8

Commits viewable in compare view.

Updated Aspire.Hosting.RabbitMQ from 13.6.0 to 13.6.1.

Release notes

Sourced from Aspire.Hosting.RabbitMQ's releases.

13.6.1

What's New in Aspire 13.6.1

Patch release for Aspire 13.6 that reduces dashboard CPU usage during sustained metric ingestion, restores scrolling in the Metrics tree, improves dashboard navigation, fixes container exec watch failures, and ensures session-scoped containers are cleaned up when stopping .NET AppHosts on Windows.

🐛 Fixes

• 📊 Dashboard CPU usage could increase during long-running metric ingestion — Metric retention repeatedly scanned retained history on every insertion, causing steadily increasing CPU usage even with a fixed workload. Cleanup now skips dimensions below capacity and removes only the oldest surplus points when needed. Existing retention limits and exemplar behavior are unchanged, and no configuration changes are required. Regression introduced in 13.6. Fixes #​20725. (#​20747, backport of #​20736, @​JamesNK)

• 📈 The Metrics tree could not be scrolled — The meter and instrument tree now scrolls when it exceeds the viewport, allowing you to reach and select instruments below the fold. Regression introduced in 13.6. Fixes #​20728. (#​20762, backport of #​20758, @​heyysiri)

• 🧭 Dashboard navigation could fail after a browser disconnect — Pending page-state updates now persist session state before navigating and skip navigation when the browser has disconnected, avoiding an unhandled navigation failure. The navigation rail's overflow button also has consistent sizing, icon alignment, and hover styling in expanded and collapsed layouts and both light and dark themes. (#​20545, backport of #​20527, @​JamesNK)

• 🖥️ Container exec watches could terminate shortly after AppHost startup — A stalled DCP watch connection could produce a critical Watch task over Kubernetes ContainerExec resources terminated unexpectedly error and stop subsequent terminal state and log updates from being observed. Watch connection attempts now retry after timeouts, and periodic restarts correctly recreate connections without swallowing unrelated cancellation. Regression introduced in 13.6.0. (#​20664, backport of #​20466, @​radical)

• 🪟 Session-scoped containers could remain running after stopping a .NET AppHost on Windows — AppHosts launched through dotnet run or dotnet watch now allow DCP to finish resource cleanup during shutdown, including existing Ctrl+C and aspire stop flows. Persistent resources remain unaffected, while direct .NET launches and TypeScript/polyglot AppHosts retain their existing process protection. Fixes #​20495. (#​20514, backport of #​20494, @​danegsta)

---

Full Changelog: v13.6.0...v13.6.1

Full commit: 3751e615ad660621f2a7aa4c390ef48e08a0eed8

Commits viewable in compare view.

Updated Aspire.Hosting.SqlServer from 13.6.0 to 13.6.1.

Release notes

Sourced from Aspire.Hosting.SqlServer's releases.

13.6.1

What's New in Aspire 13.6.1

Patch release for Aspire 13.6 that reduces dashboard CPU usage during sustained metric ingestion, restores scrolling in the Metrics tree, improves dashboard navigation, fixes container exec watch failures, and ensures session-scoped containers are cleaned up when stopping .NET AppHosts on Windows.

🐛 Fixes

• 📊 Dashboard CPU usage could increase during long-running metric ingestion — Metric retention repeatedly scanned retained history on every insertion, causing steadily increasing CPU usage even with a fixed workload. Cleanup now skips dimensions below capacity and removes only the oldest surplus points when needed. Existing retention limits and exemplar behavior are unchanged, and no configuration changes are required. Regression introduced in 13.6. Fixes #​20725. (#​20747, backport of #​20736, @​JamesNK)

• 📈 The Metrics tree could not be scrolled — The meter and instrument tree now scrolls when it exceeds the viewport, allowing you to reach and select instruments below the fold. Regression introduced in 13.6. Fixes #​20728. (#​20762, backport of #​20758, @​heyysiri)

• 🧭 Dashboard navigation could fail after a browser disconnect — Pending page-state updates now persist session state before navigating and skip navigation when the browser has disconnected, avoiding an unhandled navigation failure. The navigation rail's overflow button also has consistent sizing, icon alignment, and hover styling in expanded and collapsed layouts and both light and dark themes. (#​20545, backport of #​20527, @​JamesNK)

• 🖥️ Container exec watches could terminate shortly after AppHost startup — A stalled DCP watch connection could produce a critical Watch task over Kubernetes ContainerExec resources terminated unexpectedly error and stop subsequent terminal state and log updates from being observed. Watch connection attempts now retry after timeouts, and periodic restarts correctly recreate connections without swallowing unrelated cancellation. Regression introduced in 13.6.0. (#​20664, backport of #​20466, @​radical)

• 🪟 Session-scoped containers could remain running after stopping a .NET AppHost on Windows — AppHosts launched through dotnet run or dotnet watch now allow DCP to finish resource cleanup during shutdown, including existing Ctrl+C and aspire stop flows. Persistent resources remain unaffected, while direct .NET launches and TypeScript/polyglot AppHosts retain their existing process protection. Fixes #​20495. (#​20514, backport of #​20494, @​danegsta)

---

Full Changelog: v13.6.0...v13.6.1

Full commit: 3751e615ad660621f2a7aa4c390ef48e08a0eed8

Commits viewable in compare view.

Updated Aspire.Hosting.Testing from 13.6.0 to 13.6.1.

Release notes

Sourced from Aspire.Hosting.Testing's releases.

13.6.1

What's New in Aspire 13.6.1

Patch release for Aspire 13.6 that reduces dashboard CPU usage during sustained metric ingestion, restores scrolling in the Metrics tree, improves dashboard navigation, fixes container exec watch failures, and ensures session-scoped containers are cleaned up when stopping .NET AppHosts on Windows.

🐛 Fixes

• 📊 Dashboard CPU usage could increase during long-running metric ingestion — Metric retention repeatedly scanned retained history on every insertion, causing steadily increasing CPU usage even with a fixed workload. Cleanup now skips dimensions below capacity and removes only the oldest surplus points when needed. Existing retention limits and exemplar behavior are unchanged, and no configuration changes are required. Regression introduced in 13.6. Fixes #​20725. (#​20747, backport of #​20736, @​JamesNK)

• 📈 The Metrics tree could not be scrolled — The meter and instrument tree now scrolls when it exceeds the viewport, allowing you to reach and select instruments below the fold. Regression introduced in 13.6. Fixes #​20728. (#​20762, backport of #​20758, @​heyysiri)

• 🧭 Dashboard navigation could fail after a browser disconnect — Pending page-state updates now persist session state before navigating and skip navigation when the browser has disconnected, avoiding an unhandled navigation failure. The navigation rail's overflow button also has consistent sizing, icon alignment, and hover styling in expanded and collapsed layouts and both light and dark themes. (#​20545, backport of #​20527, @​JamesNK)

• 🖥️ Container exec watches could terminate shortly after AppHost startup — A stalled DCP watch connection could produce a critical Watch task over Kubernetes ContainerExec resources terminated unexpectedly error and stop subsequent terminal state and log updates from being observed. Watch connection attempts now retry after timeouts, and periodic restarts correctly recreate connections without swallowing unrelated cancellation. Regression introduced in 13.6.0. (#​20664, backport of #​20466, @​radical)

• 🪟 Session-scoped containers could remain running after stopping a .NET AppHost on Windows — AppHosts launched through dotnet run or dotnet watch now allow DCP to finish resource cleanup during shutdown, including existing Ctrl+C and aspire stop flows. Persistent resources remain unaffected, while direct .NET launches and TypeScript/polyglot AppHosts retain their existing process protection. Fixes #​20495. (#​20514, backport of #​20494, @​danegsta)

---

Full Changelog: v13.6.0...v13.6.1

Full commit: 3751e615ad660621f2a7aa4c390ef48e08a0eed8

Commits viewable in compare view.

Updated Azure.Monitor.OpenTelemetry.Exporter from 1.9.0 to 1.10.0.

Release notes

Sourced from Azure.Monitor.OpenTelemetry.Exporter's releases.

1.10.0

1.10.0 (2026-10-05)

Features Added

• Added the Azure.Monitor.OpenTelemetry.Exporter.StorageSubDirectory AppContext value, settable with AppContext.SetData or a runtimeconfig.json configProperty, so that the processes or entry points of one application can share a persistent storage directory. By default the directory name is derived from the process name and AppContext.BaseDirectory, which splits storage when components of one application differ in either, and a component that runs rarely never drains its backlog. When set, the value replaces those two inputs; the instrumentation key and user name still contribute, so different users and resources stay isolated. Behaviour is unchanged when the value is not set.
  (#​62997)

Bugs Fixed

• SDK statistics sent to the Microsoft OpenTelemetry distro's configured ingestion endpoint (the Azure.Monitor.OpenTelemetry.Exporter.RouteSdkStatsToDistroEndpoint AppContext switch) now carry the same region-matched SDK statistics instrumentation key as the existing SDK statistics endpoint, instead of an all-zero placeholder. Only the destination differs on the distro path.
  (#​63342)

1.10.0-beta.1

1.10.0-beta.1 (2026-09-16)

Features Added

• Enable AOT compatibility validation for Azure Monitor OpenTelemetry Exporter
  (#​62850)

• Multi-endpoint routing now maps the microsoft.multi_endpoint_cloud_role attribute to ai.cloud.role for traces and logs. Missing or invalid values use unknown_service, while ai.cloud.roleInstance remains host-derived. The attribute is read from Activity tags for traces and LogRecord.Attributes for logs, and only affects cloud role when multi-endpoint routing is enabled.
  (#​62909)

• Added multi-endpoint routing for traces, off by default and enabled with the Azure.Monitor.OpenTelemetry.EnableMultiEndpointRouting AppContext switch. When enabled, an Activity carrying the microsoft.instrumentation_key and microsoft.ingestion_endpoint attributes is sent to that endpoint instead of the exporter's own; Activities without both attributes are dropped. Live Metrics is disabled while the switch is on, and sampling defaults to fixed-rate rather than rate-limited because a per-process rate limit would be shared across every destination the process carries. The switch cannot be combined with Microsoft Entra ID authentication, because the credential is scoped to the exporter's own audience and would be sent to endpoints supplied by telemetry.
  (#​62707)

• Extended multi-endpoint routing to logs, off by default and enabled with the same Azure.Monitor.OpenTelemetry.EnableMultiEndpointRouting AppContext switch used for traces. When enabled, a LogRecord carrying the microsoft.instrumentation_key and microsoft.ingestion_endpoint attributes is sent to that endpoint instead of the exporter's own; log records without both attributes are dropped. The two routing attributes are consumed for routing and are not emitted as custom properties. Routing reads only LogRecord.Attributes, not logging scopes. Live Metrics disablement and the Microsoft Entra ID restriction that apply to multi-endpoint traces apply to logs as well, since both are enforced on the shared transmitter.
  (#​62885)

• Extended multi-endpoint routing to metrics, off by default and enabled with the same Azure.Monitor.OpenTelemetry.EnableMultiEndpointRouting AppContext switch used for traces and logs. A measurement carrying the microsoft.instrumentation_key and microsoft.ingestion_endpoint dimensions is sent to that endpoint instead of the exporter's own; measurements without both are dropped. Unlike traces and logs, the routing values are supplied as dimensions at measurement time rather than stamped afterwards, because a metric's dimensions are part of its aggregation key: each destination becomes its own time series, and one instrument can feed several endpoints. Routing is applied per MetricPoint, the three routing dimensions are consumed rather than emitted as custom properties, and microsoft.multi_endpoint_cloud_role sets ai.cloud.role as it does for traces and logs. Standard metrics and performance counters are not collected while the switch is on: routed destinations are not sent standard metrics, and a process-scoped performance counter has no single owner among the destinations a routed process carries.
  (#​62957)

• A connection string is no longer required when multi-endpoint routing is enabled. Routing takes every destination from the telemetry itself, so a process that only routes has no component of its own to name, and previously had to nominate one that received nothing. Telemetry carrying valid routing attributes is still sent to the endpoint it names; telemetry without them is dropped, as it already was. SDK statistics are not collected in this configuration, because they identify a component by instrumentation key and select their region from its ingestion endpoint, neither of which exists without a connection string. Behaviour is unchanged when a connection string is configured, and unchanged when the switch is off: a missing connection string is still an error.
  (#​63004)

Other Changes

• Added self-diagnostics for multi-endpoint routing, including rejected telemetry, endpoint delivery, partition limits, and storage eviction.
  (#​62925)

Commits viewable in compare view.

Updated Azure.Storage.Blobs from 12.30.0 to 12.30.1.

Release notes

Sourced from Azure.Storage.Blobs's releases.

12.30.1

12.30.1 (2026-10-05)

Bugs Fixed

• Fixed AuthenticatedRegionCryptoStream.Dispose() to be idempotent and thread-safe, so the buffer it rents is no longer returned to the shared ArrayPool<byte> more than once when the stream is disposed repeatedly or concurrently. Returning the same array twice allowed unrelated callers to rent the same array instance and corrupt each other's data.

Commits viewable in compare view.

Updated Microsoft.NET.Test.Sdk from 18.10.1 to 18.11.0.

Release notes

Sourced from Microsoft.NET.Test.Sdk's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.Playwright from 1.56.0 to 1.63.0.

Release notes

Sourced from Microsoft.Playwright's releases.

1.63.0

🪟 Locate across frames

Page.FrameLocator() and Frame.FrameLocator() called without a selector search in any frame of the
subtree, so you no longer need to locate the iframe first:

// Finds the button in any frame on the page.
await Page.FrameLocator().GetByRole(AriaRole.Button).ClickAsync();

The rest of the locator resolves inside a single frame, just like a regular locator, and an error is thrown when it
matches elements in several frames.

👁️ Visible-only locators

New Locator.Visible returns a locator that matches only visible elements. It is the recommended
replacement for the :visible CSS pseudo-class:

await Page.Locator("button").Visible.ClickAsync();

🖼️ Aria and screen snapshots in traces

New AriaSnapshots and ScreenSnapshots options of Tracing.StartAsync() capture an aria snapshot and a screenshot of the page on every action:

await context.Tracing.StartAsync(new()
{
  Snapshots = true,
  AriaSnapshots = true,
  ScreenSnapshots = true
});

With aria and screen snapshots recorded, the new Display Aria mode in the trace viewer shows the action screenshot
side by side with the aria snapshot, and hovering an aria node highlights it on the screenshot.

New APIs

Browser and Context

• HttpCredentialsList now also accepts an array of credentials. The first entry matching the request origin is used, and entries without an origin match any request.
• New option Opfs includes the origin private file system in the storage state, so it can be persisted and restored into later contexts.
• New events Page. DialogClosed and BrowserContext. DialogClosed are emitted when a JavaScript dialog is accepted, dismissed or closed by the user.

Command line

• pwsh bin/Debug/netX/playwright.ps1 install --no-remove keeps the browsers of other Playwright installations instead of removing them.
• pwsh bin/Debug/netX/playwright.ps1 codegen --http-credentials records against pages behind HTTP authentication.

Announcements

... (truncated)

1.62.0

🖼️ WebP screenshots

page.screenshot() and locator.screenshot() can now capture screenshots in the WebP format — Playwright infers the format from a .webp file extension, or you can set the type explicitly. Quality 100 (the default) is lossless, while lower values use lossy compression:

await Page.ScreenshotAsync(new() { Path = "homepage.webp", Quality = 50 });

New APIs

• New Scroll option (Auto | None) on actions to opt out of Playwright's automatic scroll-into-view.
• New Locator.WaitForFunctionAsync() waits until a function — called with the matching element — returns a truthy value.
• New APIResponse.TimingAsync() returns resource timing information for an API response.

Announcements

• 📋 The clipboard is now isolated from the operating system in headless mode, so tests that use navigator.clipboard no longer read or overwrite the clipboard of the machine running them.
• ⚠️ Debian 11 is not supported anymore.

Browser Versions

• Chromium 151.0.7922.34
• Mozilla Firefox 153.0
• WebKit 26.5

This version was also tested against the following stable channels:

• Google Chrome 151
• Microsoft Edge 151

1.61.0

🔑 WebAuthn passkeys

New Credentials virtual authenticator, available via BrowserContext.Credentials, lets tests register passkeys and answer navigator.credentials.create() / navigator.credentials.get() ceremonies in the page — no real hardware key required, works in all browsers:

var context = await browser.NewContextAsync();

// Seed a passkey your backend provisioned for a test user.
await context.Credentials.CreateAsync("example.com", new()
{
    Id = credentialId,
    UserHandle = userHandle,
    PrivateKey = privateKey,
    PublicKey = publicKey,
});
await context.Credentials.InstallAsync();

var page = await context.NewPageAsync();
await page.GotoAsync("https://example.com/login");
// The page's navigator.credentials.get() is answered with the seeded passkey.

You can also let the app register a passkey once in a setup test, read it back with Credentials.GetAsync(), and seed it into later tests — see Credentials for details.

🗃️ Web Storage

New WebStorage API, available via Page.LocalStorage and Page.SessionStorage, reads and writes the page's storage for the current origin:

await page.LocalStorage.SetItemAsync("token", "abc");
var token = await page.LocalStorage.GetItemAsync("token");
var items = await page.SessionStorage.ItemsAsync();

New APIs

• APIResponse.SecurityDetailsAsync() and APIResponse.ServerAddrAsync() mirror the browser-side Response.SecurityDetailsAsync() and Response.ServerAddrAsync().
• New option ArtifactsDir in BrowserType.ConnectOverCDPAsync() controls where artifacts such as traces and downloads are stored when attached to an existing browser.
• New option Cursor in Screencast.ShowActionsAsync() controls the cursor decoration rendered for pointer actions.
• The OnFrame callback in Screencast.StartAsync() now receives a Timestamp of when the frame was presented by the browser.

🛠️ Other improvements

• Playwright now supports Ubuntu 26.04.
• HAR and trace recordings now include WebSocket requests.

Browser Versions

• Chromium 149.0.7827.55
• Mozilla Firefox 151.0
• WebKit 26.5

This version was also tested against the following stable channels:
... (truncated)

1.60.0

💬 Custom assertion messages

Expect() overloads now accept a custom message that is prepended to any failure, giving extra context in test reports:

await Expect(page.Locator("#status"), "Should be logged in").ToBeVisibleAsync();

When the assertion fails, the message is prefixed:

Should be logged in
Locator expected to be visible

🌐 HAR recording on Tracing

Tracing.StartHarAsync() / Tracing.StopHarAsync() expose HAR recording as a first-class tracing API, with the same Content, Mode and UrlFilter options as RecordHar:

await context.Tracing.StartHarAsync("trace.har");
var page = await context.NewPageAsync();
await page.GotoAsync("https://playwright.dev");
await context.Tracing.StopHarAsync();

🪝 Drop API

New Locator.DropAsync() simulates an external drag-and-drop of files or clipboard-like data onto an element. Playwright dispatches dragenter, dragover, and drop with a synthetic [DataTransfer] in the page context — works cross-browser and is great for testing upload zones:

await page.Locator("#dropzone").DropAsync(new() {
    Files = new FilePayload() {
        Name = "note.txt",
        MimeType = "text/plain",
        Buffer = Encoding.UTF8.GetBytes("hello"),
    },
});

await page.Locator("#dropzone").DropAsync(new() {
    Data = new Dictionary<string, string> {
        ["text/plain"] = "hello world",
        ["text/uri-list"] = "https://example.com",
    },
});

🎯 Aria snapshots

• Expect(page).ToMatchAriaSnapshotAsync() now works on a Page, in addition to a Locator — equivalent to asserting against Page.Locator("body").
• New Boxes option on Locator.AriaSnapshotAsync() / Page.AriaSnapshotAsync() appends each element's bounding box as [box=x,y,width,height], useful for AI consumption.
  ... (truncated)

1.59.0

🎬 Screencast

New Page.Screencast API provides a unified interface for capturing page content with:

• Screencast recordings
• Action annotations
• Visual overlays
• Real-time frame capture
• Agentic video receipts

Screencast recording — record video with precise start/stop control, as an alternative to the recordVideoDir option:

await page.Screencast.StartAsync(new() { Path = "video.webm" });
// ... perform actions ...
await page.Screencast.StopAsync();

Action annotations — enable built-in visual annotations that highlight interacted elements and display action titles during recording:

await page.Screencast.ShowActionsAsync(new() { Position = "top-right" });

ShowActionsAsync accepts Position ("top-left", "top", "top-right", "bottom-left", "bottom", "bottom-right"), Duration (ms per annotation), and FontSize (px). Returns a disposable to stop showing actions.

Visual overlays — add chapter titles and custom HTML overlays on top of the page for richer narration:

await page.Screencast.ShowChapterAsync("Adding TODOs", new() {
    Description = "Type and press enter for each TODO",
    Duration = 1000,
});

await page.Screencast.ShowOverlayAsync("<div style=\"color: red\">Recording</div>");

Real-time frame capture — stream JPEG-encoded frames for custom processing like thumbnails, live previews, AI vision, and more:

await page.Screencast.StartAsync(new() {
    OnFrame = frame => SendToVisionModel(frame.Data),
});

... (truncated)

1.58.0

Trace Viewer Improvements

• New 'system' theme option follows your OS dark/light mode preference
• Search functionality (Cmd/Ctrl+F) is now available in code editors
• Network details panel has been reorganized for better usability
• JSON responses are now automatically formatted for readability

Thanks to @​cpAdm for contributing these improvements!

Miscellaneous

BrowserType.ConnectOverCDPAsync() now accepts an IsLocal option. When set to true, it tells Playwright that it runs on the same host as the CDP server, enabling file system optimizations.

Breaking Changes ⚠️

• Removed _react and _vue selectors. See locators guide for alternatives.
• Removed :light selector engine suffix. Use standard CSS selectors instead.
• Option Devtools from BrowserType.LaunchAsync() has been removed. Use Args = new[] { "--auto-open-devtools-for-tabs" } instead.
• Removed macOS 13 support for WebKit.

Browser Versions

• Chromium 145.0.7632.6
• Mozilla Firefox 146.0.1
• WebKit 26.0

1.57.0

Chrome for Testing

Starting with this release, Playwright switches from Chromium, to using Chrome for Testing builds. Both headed and headless browsers are subject to this. Your tests should still be passing after upgrading to Playwright 1.57.

We're expecting no functional changes to come from this switch. The biggest change is the new icon and title in your toolbar.

If you still see an unexpected behaviour change, please file an issue.

On Arm64 Linux, Playwright continues to use Chromium.

Breaking Change

After 3 years of being deprecated, we removed Page.Accessibility from our API. Please use other libraries such as Axe if you need to test page accessibility. See our Node.js guide for integration with Axe.

New APIs

• Worker.Console event is emitted when JavaScript within the worker calls one of console API methods, e.g. console.log or console.dir.
• Locator.Description returns locator description previously set with Locator.Describe().
• New option Steps in Locator.ClickAsync() and Locator.DragToAsync() that configures the number of mousemove events emitted while moving the mouse pointer to the target element.

Browser Versions

• Chromium 143.0.7499.4
• Mozilla Firefox 144.0.2
• WebKit 26.0

Commits viewable in compare view.

Updated QRCoder from 1.8.0 to 1.8.1.

Release notes

Sourced from QRCoder's releases.

1.8.1

What's Changed

• a couple places where ArtQRCode creates a short lived Bitmap but neve… by @​danFbach in a couple places where ArtQRCode creates a short lived Bitmap but neve… Shane32/QRCoder#695
• Minor performance improvement in BitmapByteQRCode + clarify padding calculation by @​KrisVandermotten in Minor performance improvement in BitmapByteQRCode + clarify padding calculation Shane32/QRCoder#698
• Cleanup and optimize CalculateGeneratorPolynom by @​KrisVandermotten in Cleanup and optimize CalculateGeneratorPolynom Shane32/QRCoder#702
• Optimize AlignmentPatterns by @​KrisVandermotten in Optimize AlignmentPatterns Shane32/QRCoder#699
• Some cleanup (and minor optimizations) in BitmapByteQRCode by @​KrisVandermotten in Some cleanup (and minor optimizations) in BitmapByteQRCode Shane32/QRCoder#703
• Optimizations in mask patterns by @​KrisVandermotten in Optimizations in mask patterns Shane32/QRCoder#706

New Contributors

• @​danFbach made their first contribution in a couple places where ArtQRCode creates a short lived Bitmap but neve… Shane32/QRCoder#695
• @​KrisVandermotten made their first contribution in Minor performance improvement in BitmapByteQRCode + clarify padding calculation Shane32/QRCoder#698

Full Changelog: Shane32/QRCoder@v1.8.0...v1.8.1

Commits viewable in compare view.

Updated Swashbuckle.AspNetCore from 10.2.3 to 10.3.0.

Release notes

Sourced from Swashbuckle.AspNetCore's releases.

10.3.0

What's Changed

• Change nullability handling for schemas with anyOf, allOf, oneOf or type = null by @​ldeluigi in Change nullability handling for schemas with anyOf, allOf, oneOf or type = null domaindrivendev/Swashbuckle.AspNetCore#3976
• Handle leading slash on route prefix during index.html GET by @​superstator in Handle leading slash on route prefix during index.html GET domaindrivendev/Swashbuckle.AspNetCore#4084
• Move NRT handling to DataContractResolver by @​desjoerd in Move NRT handling to DataContractResolver domaindrivendev/Swashbuckle.AspNetCore#3998
• Clarify nullable behaviour by @​martincostello in Clarify nullable behaviour domaindrivendev/Swashbuckle.AspNetCore#4094
• Fix review issues for caching and encoding by @​martincostello in Fix review issues for caching and encoding domaindrivendev/Swashbuckle.AspNetCore#4093
• Support multiple response types per status code by @​DeagleGross in Support multiple response types per status code domaindrivendev/Swashbuckle.AspNetCore#4100
• Add coverage for AddServer across multiple documents by @​RaphaelFakhri in Add coverage for AddServer across multiple documents domaindrivendev/Swashbuckle.AspNetCore#4115
• Fix Swagger sort key fallback for empty endpoint tags metadata by @​AleksaMCode in Fix Swagger sort key fallback for empty endpoint tags metadata domaindrivendev/Swashbuckle.AspNetCore#4125
• Fix parameter matching to consider location when names collide by @​nonsoikem in Fix parameter matching to consider location when names collide domaindrivendev/Swashbuckle.AspNetCore#4126
• Emit form encoding for properties of a complex form parameter by @​RaphaelFakhri in Fix #3169: emit form encoding for properties of a complex form parameter domaindrivendev/Swashbuckle.AspNetCore#4128
• Keep a property's own summary when comments come from several XML files by @​RaphaelFakhri in Fix #3240: keep a property's own summary when comments come from several XML files domaindrivendev/Swashbuckle.AspNetCore#4129
• Strip query string from relative document URLs in Swagger UI by @​GabeSilvaDev in Strip query string from relative document URLs in Swagger UI domaindrivendev/Swashbuckle.AspNetCore#4152
• Document that System.Text.Json ignores [EnumMember] by @​RaphaelFakhri in Document that System.Text.Json ignores [EnumMember] domaindrivendev/Swashbuckle.AspNetCore#4127
• Drop the regex route constraint from the default Swagger route by @​RaphaelFakhri in Fix #2951: drop the regex route constraint from the default Swagger route domaindrivendev/Swashbuckle.AspNetCore#4130
• Serialize custom values in the UI ConfigObject.AdditionalItems by @​RaphaelFakhri in Fix #3153: serialize custom values in the UI ConfigObject AdditionalItems domaindrivendev/Swashbuckle.AspNetCore#4132
• Use Minimal APIs JSON options when MVC is not registered by @​RaphaelFakhri in Use Minimal APIs JSON options when MVC is not registered domaindrivendev/Swashbuckle.AspNetCore#4116
• Resolve enum contracts against the underlying type under source generation by @​RaphaelFakhri in Fix #3217: resolve enum contracts against the underlying type under source generation domaindrivendev/Swashbuckle.AspNetCore#4131

New Contributors

• @​ldeluigi made their first contribution in Change nullability handling for schemas with anyOf, allOf, oneOf or type = null domaindrivendev/Swashbuckle.AspNetCore#3976
• @​superstator made their first contribution in Handle leading slash on route prefix during index.html GET domaindrivendev/Swashbuckle.AspNetCore#4084
• @​desjoerd made their first contribution in Move NRT handling to DataContractResolver domaindrivendev/Swashbuckle.AspNetCore#3998
• @​RaphaelFakhri made their first contribution in Add coverage for AddServer across multiple documents domaindrivendev/Swashbuckle.AspNetCore#4115
• @​AleksaMCode made their first contribution in Fix Swagger sort key fallback for empty endpoint tags metadata domaindrivendev/Swashbuckle.AspNetCore#4125
• @​nonsoikem made their first contribution in Fix parameter matching to consider location when names collide domaindrivendev/Swashbuckle.AspNetCore#4126
• @​GabeSilvaDev made their first contribution in Strip query string from relative document URLs in Swagger UI domaindrivendev/Swashbuckle.AspNetCore#4152
• @​JulianThoms made their first contribution in Add regression tests for nullable dynamic properties domaindrivendev/Swashbuckle.AspNetCore#4182

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.2.3...v10.3.0

Commits viewable in compare view.

Updated xunit.runner.visualstudio from 4.0.0 to 4.0.1.

Release notes

Sourced from xunit.runner.visualstudio's releases.

4.0.1

Release notes: https://xunit.net/releases/visualstudio/4.0.1

Commits viewable in compare view.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions