Bump the nuget-minor-patch group with 8 updates

[dependabot]

Updated AngleSharp from 1.8.3 to 1.8.4.

Release notes

Sourced from AngleSharp's releases.

1.8.4

Released on Wednesday, October 7 2026

What's Changed

• Improved selection when parsing <select> (#​1364) @​PrzemyslawKlys
• Updated constraint validation eligibility of fieldset and output elements (breaking behavior change) (#​1373) @​PrzemyslawKlys
• Fixed change of <select> value (IsSelected) (#​1365) @​PrzemyslawKlys
• Fixed indeterminate input state when cloning (#​1367) @​PrzemyslawKlys
• Fixed <select> form submission including unselected options and options in disabled groups (#​1366) @​PrzemyslawKlys
• Fixed option indexes inside option groups (#​1368) @​PrzemyslawKlys
• Fixed selecting an option leaving other single-select options selected (#​1372) @​PrzemyslawKlys
• Fixed validity checks for controls excluded from validation (#​1370) @​PrzemyslawKlys
• Fixed template content document when adopting a subtree (#​1374) @​PrzemyslawKlys
• Fixed checking a radio leaving other group members checked (#​1371) @​PrzemyslawKlys
• Fixed parsed radio checkedness depending on attribute order @​PrzemyslawKlys
• Fixed SVG annotation-xml elements being treated as HTML integration points @​NotAFlightRisk
• Fixed required radio validation across group members (#​1369) @​PrzemyslawKlys
• Released 1.8.4 by @​FlorianRappl in Release 1.8.4 AngleSharp/AngleSharp#1377

New Contributors

• @​NotAFlightRisk made their first contribution in Don't treat an SVG annotation-xml as an HTML integration point AngleSharp/AngleSharp#1376

Full Changelog: AngleSharp/AngleSharp@v1.8.3...v1.8.4

Commits viewable in compare view.

Updated Aspire.Hosting.AppHost from 13.6.0 to 13.6.1.

Release notes

Sourced from Aspire.Hosting.AppHost'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.PostgreSQL from 13.6.0 to 13.6.1.

Release notes

Sourced from Aspire.Hosting.PostgreSQL'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 Marten from 9.45.0 to 9.48.0.

Release notes

Sourced from Marten's releases.

9.48.0

Document diagnostics: filter and order by document properties (jasperfx#​869, #​5631)

IDocumentStoreDiagnostics.QueryDocumentsAsync now applies DocumentQueryOptions.Where / OrderBy / Arguments instead of refusing them. The text goes onto Query<T>() through JasperFx 2.84.0's Dynamic LINQ helper, so member casing, enum storage, duplicated fields, conjoined tenancy, soft deletes and hierarchies are Marten's own; only the SELECT list is swapped for the diagnostics read's columns, so the JSON comes back byte-exact with its metadata, and the total counts the filtered rows. Operator text is never spliced into SQL, and the read issues no DDL.

Measured against a LINQ-to-objects oracle over 83 shapes and three storage configurations; every shape is either right or refused:

• Refused: range comparisons on, and ordering by, an enum stored as its name (string serializer storage or a varchar duplicated field), and <> / a negated comparison on a nullable member unless the text says what null should do (JasperFx's SqlNullSemantics). Date-part members and inline in (…) lists are refused honestly by the provider.
• Fixed rather than refused: criteria orderings put nulls first ascending, as .NET does (PostgreSQL defaults to last), and DateTime arguments compare correctly against timestamp without time zone locators.
• String ordering follows the database's collation (note: Alpine images use musl and sort bytewise).
• Under Native AOT, criteria are refused.

Fixes

• Grouped projections translate Count / LongCount predicates through the Where parser, with null semantics and bound parameters (#​5625).
• A quick-mode StartStream that loses a race for the same stream id now throws ExistingStreamIdCollisionException instead of a raw 23505, so QuickWithServerTimestamps behaves like Rich and Quick (#​5628).

Dependencies

JasperFx 2.84.0

9.47.0

The FetchForWriting / FetchLatest consistency release, plus a bounded async-daemon shutdown.

Read the behaviour changes before upgrading. Two of them can change how your projections and
subscriptions behave on every deployment, and two more refuse a batch shape that used to be accepted.

⚠️ Behaviour changes

Subscription and projection drains are now bounded by StopAndDrainTimeout ([#​5610])

Via JasperFx 2.81.0 (jasperfx#​953 and jasperfx#​983). When a shard stops — host shutdown, or reassignment
to another node — the page in flight finishes, pages still queued are skipped and resumed by the next
owner from committed progression, and a page still running at Projections.StopAndDrainTimeout
(default 5 seconds) is cancelled with its transaction rolled back.

This fixes a real failure: a node that loses a shard's lock no longer keeps applying its backlog
alongside the new owner, an overlap that could end in ProgressionProgressOutOfOrderException and a
Stopped shard. Graceful shutdown is also bounded now, rather than waiting out the whole backlog and
potentially overrunning a Kubernetes termination grace period.

If your projection or subscription pages take longer than 5 seconds, raise the timeout:

opts.Projections.StopAndDrainTimeout = 30.Seconds();

Otherwise those pages are cancelled and re-processed on every shutdown and rebalance. Delivery was
always at-least-once, so no guarantee changed, but duplicates become much more likely — and side effects
performed outside the Marten session (HTTP calls, sends that bypass the transactional outbox) are not
rolled back with the page. Note this applies to async projections as well as subscriptions; the upstream
note covers only subscriptions and is out of date.

A batched FetchLatest or expected-version FetchForWriting must be first in its batch ([#​5604])

For an aggregate projected with ProjectionLifecycle.Async only. Both now bracket their reads in
begin transaction isolation level repeatable read read only … end so those reads share one snapshot,
and PostgreSQL accepts that only as a transaction's first statement. So:

• batch.Events.FetchLatest<T>(id) and batch.Events.FetchForWriting<T>(id, version) have to be the
  first operation in their batch, and
• neither can share a batch with a FetchForExclusiveWriting.

Both are refused at the enlisting call, naming the call to move, rather than surfacing later as a bare
25001. Inline and Live aggregates are unaffected, and inside a caller-owned transaction no bracket is
emitted so neither rule applies. If you batch a FetchLatest behind a Load, move it to the front.

New SnapshotRaceException from a batched exclusive fetch ([#​5613])

A batched FetchForExclusiveWriting on an Async aggregate now throws Marten.Exceptions.SnapshotRaceException
in the rare case where the daemon commits a snapshot between that batch's two reads. Retry the batch, or
fetch outside a batch — outside a batch Marten retries for you and you will never see it.
... (truncated)

9.46.0

Mostly a resiliency and Native AOT release. Five behaviour changes — the retry ones are the most likely to be noticed, because Marten now surfaces failures it used to absorb.

Behaviour changes

A command timeout is no longer retried on reads (#​5566, #​5580). An attempt that timed out has already spent the whole CommandTimeout, so retrying it three times held the caller for four timeouts instead of one. This covers both shapes: Npgsql's client-side CommandTimeout, and a server-side statement_timeout, which arrives as 57014 query_canceled with no TimeoutException anywhere in the exception. Connection-pool exhaustion arrives in the same shape and so is no longer retried either — a deliberate trade, documented in the resiliency guide along with what to do instead.

Sticky, ambient and external session lifetimes now fail loudly (#​5582, #​5598), via the new SessionTransactionUnusableException. Two things used to go wrong silently. A broken connection reported ConnectionState.Closed, so Marten reopened it — onto a different backend — and handed the command the stale transaction, which Npgsql accepts; a Serializable session then quietly answered from a newer snapshot. And a command timeout inside a transaction aborted it, after which every later call returned a bare 25P02 naming neither the timeout nor the way out. For caller-owned transactions Marten records the cause and reports it but rolls nothing back — the scope is still yours.

The async serializable session builders now produce a serializable session (#​5594). OpenSerializableSessionAsync(new SessionOptions()) previously returned a session that was neither serializable nor auto-closing: it held one connection open for its lifetime with no transaction. These two methods now pin IsolationLevel to Serializable and begin the transaction eagerly. A non-Serializable level passed to them is overridden rather than silently honoured.

The async daemon spends one retry budget instead of two (#​5593). ResilientEventLoader and the QuerySession inside it were both given the same pipeline, so a handled failure ran up to sixteen times.

A retried write no longer accumulates exceptions across attempts (#​5591). The exception list was shared, and ExecuteBatchPagesAsync branches on its count — so one operation failing twice turned a rethrow into an AggregateException, making the caller's exception type depend on how many retries happened.

Native AOT

Strong-typed document ids now work (#​5589, #​5579), with one registration per document type:

opts.Schema.For<Invoice>();
opts.RegisterValueTypeId<Invoice, InvoiceId, Guid>();

Previously a single strong-typed id anywhere in the store killed the application while the first document's mapping was built. The identity path closes a chain of generics over your id type, and a native image has no instantiation for them unless something roots it; naming all three types is what roots them. Under a JIT the call does nothing — unregistered types still take the reflective path. Not yet covered: F# single-case discriminated-union ids, and .IsOneOf over a strong-typed id. The intent is for Marten.SourceGenerator to emit these registrations so the call becomes unnecessary.

Also AOT: a decimal comparison in a LINQ filter is documented with a tested workaround (#​5597) — it is the BCL expression-tree factory rather than Marten, but it only shows up from a native binary. Marten's AOT runtime gate now covers strong-typed ids and decimals, so these stay pinned.

Fixes

• PrefixSearch quotes each word as a tsquery lexeme (#​5571, #​5568), so a search box containing &, |, !, (, : or a tab no longer produces 42601: syntax error in tsquery. Not an injection — the term was already a parameter — but the documented contract says each word is treated as a prefix, and raw input has to be escaped to honour that.
• A quick append nulls every DCB tag slot, not just the tagged ones (#​5570).
• AdvisoryLock shutdown release is bounded, and the vendored copy moves back to Weasel (#​5572, #​5576).
• Three catch-and-Console.WriteLine-and-rethrow blocks removed (#​5584) — they bypassed IMartenSessionLogger and any configured ILogger, and one of them also closed a connection on the line above the one that opened it.

Dependencies

JasperFx 2.80.2 (#​5590) and Weasel 9.41.0 (#​5596, #​5576). Both carry Native AOT work of their own on the identity path — JasperFx's ValueTypeInfo wrappers and aggregate identity sources, Weasel's non-generic IIdentification facade.

🤖 Generated with Claude Code

https://claude.ai/code/session_01481eiEZg1Bv6pu4DrgPRg3

Commits viewable in compare view.

Updated Radzen.Blazor from 12.0.5 to 12.0.8.

Release notes

Sourced from Radzen.Blazor's releases.

12.0.8

12.0.8 - 2026-10-10

Improvements

• TileLayout gets an AllowOverlap parameter. When it is false a move or resize that would place a tile over another visible tile is blocked: the tile first tries the free axis alone so a diagonal drag slides along the neighbor, otherwise it stays at its last valid cell. Tiles that already overlap when the drag starts are ignored so they can still be pulled apart. The default stays true.

Fixes

• DataGrid keeps expanded rows consistent across Reload when KeyProperty is set. The row toggler icon resolved the expanded state by key while the detail row and CollapseItem resolved it by object reference, so after Reload returned fresh objects with the same keys the icon stayed expanded, the detail disappeared and clicking the icon could not remove the stale entry. The row template now uses IsRowExpanded, CollapseItem removes the stored key that matches by KeyProperty, Single expand mode compares with ItemEquals and the hierarchy view re-keys the child data to the fresh parent object so expanded children survive a reload (#​2752).
• AutoComplete keeps Value when it is declared before Data in the markup. Blazor assigns parameters in markup order and the Data setter resets the stored value whenever Data changes, so a Value declared before Data was lost on the first render and again every time Data was replaced. The Value parameter is now captured before the first await and re-applied after the base call when the Data setter has reset it (#​2754).
• DataGrid filtering a collection column translates to SQL again when Data is an EF Core IQueryable. The null guard added around Any/All and IsEmpty/IsNotEmpty collection filters protects in-memory data with null collections, but EF Core cannot translate a null comparison of a projected collection such as c.Orders.Select(o => o.Number).ToList() and failed the whole query with "could not be translated". The guard is now emitted only for in-memory sources, so database providers get a plain Any/All as in 11.1.6 (#​2755).

12.0.7

12.0.7 - 2026-10-08

Fixes

• Chart adopts the ViewStart and ViewEnd a ViewChange handler assigns during a mouse wheel zoom or scrollbar pan. The callbacks fired while the internal zoom guard was active, so a handler that re-anchored the bound range, for example to keep the latest data in view, updated the parent state while the chart kept rendering the cursor-centered range until the next unrelated render. After ViewStartChanged, ViewEndChanged and ViewChange complete the chart now takes the range it received, clamps it and raises ZoomChanged again if the zoom level moved.
• DatePicker with ShowDays="false" is usable again with the drill-down navigation. The month and year grids were rendered inside the same ShowDays block as the day table, so a month or year picker showed only the header: the title cycled through the month and year views with nothing drawn, the year-range view had no way back and its arrows moved the current date by twelve years. The grids are now rendered regardless of ShowDays and only the day table is gated by it. With ShowDays false the calendar opens in the month grid, the title drills up to the year grid, a year cell returns to the month grid and a month cell stays there with the picked month highlighted and focused. Picking a month changes CurrentDate and raises CurrentDateChanged as the v11 header dropdowns did; the bound Value is not committed, so existing handlers keep working. DropDown navigation with ShowDays false still renders only the header dropdowns.
• Spreadsheet loads workbooks whose formulas reference large, mutually overlapping ranges without overflowing the stack, and computes them like Excel. Each referenced cell was evaluated recursively and every range expanded eagerly, so INDEX($W$7:$W$521,...) in column V and INDEX($V$31:$V$521,...) in column W recursed through the whole block and crashed with a stack overflow in WebAssembly. Recalculation now follows a calculation chain: only the cells dirtied by a change are recalculated, every other formula cell is read from its stored value, and a formula that reads a dirty precedent not yet calculated is re-queued after it, so stack depth is bounded by formula nesting instead of data size and cycles are detected at calculation time. Cell and range expressions evaluate to references that are dereferenced only where values are needed, so INDEX, ROW, COLUMN, ROWS, COLUMNS, VLOOKUP, HLOOKUP and XLOOKUP read only the cells they use, and IF, IFERROR, IFNA, IFS, SWITCH and CHOOSE evaluate only the branch they take, so ROW(A5) in A5 is 5 instead of #CIRCULAR and CHOOSE(1,5,1/0) is 5. An error criterion in COUNTIF, SUMIF, AVERAGEIF and the *IFS functions matches cells holding the same error instead of failing the formula. The dependency graph stores each distinct range once with the formulas that read it, which cut building it for the reported workbook from 23.8 s to 0.3 s. All formula cells of the three attached workbooks match the values Excel saved (#​2750).
• Spreadsheet loads large formula workbooks faster. During a recalculation the values of a range are read once and later reads get a copy, unless the range holds a cell that is still pending or a self or circular read, so the 2,333 range reads made while loading the workbook from #​2750 no longer read 3.8 million cells. The formula lexer allocates trivia lists only for tokens that have trivia, shared formulas reuse the parsed master formula instead of parsing it again for every cell, and unpopulated cells share a single empty instance. Worksheets are read with a streaming XmlReader instead of loading each sheet part into an XDocument, so the cell elements are never materialized as XElement and XAttribute objects. Loading that workbook in WebAssembly allocates 244 MB instead of 535 MB and takes 10.7 s instead of 20.4 s.

12.0.6

12.0.6 - 2026-10-06

Improvements

• Spreadsheet Worksheet.RightToLeft displays a sheet right to left, with column A on the right. XlsxWriter writes it as rightToLeft="1" on the sheet view and XlsxReader reads it back, so Arabic and Hebrew workbooks no longer open left to right. The RadzenDataGrid Excel export follows the computed direction of the rendered grid, and the new DataGridExcelExportOptions.RightToLeft overrides it (#​2748).

Fixes

• Chart panning and zooming stay responsive with large datasets. Dragging the scrollbar, panning by touch, spinning the wheel or pinching sent one interop call per native event, so a short drag over a 20000 item column series queued 60 OnPan calls that each re-rendered every column and took over two minutes to settle. The zoom and pan interop is now serialized, with the newest pan position and the accumulated wheel steps sent in one call, RadzenColumnSeries and RadzenBarSeries skip the items outside the zoomed plot area, and RadzenLineSeries and RadzenAreaSeries build their path from the points that reach it plus the neighbors the curve needs, unless AnimateDataUpdates is set. A zoomed chart with 20000 columns now settles 40 ms after the last scrollbar move (#​2749).
• Chart value axis with both Min and Max and no Step always labels Max. The tick step divides the pinned range evenly instead of rounding up to a whole number, which pushed the last tick past Max and dropped it whenever the range was not a multiple of the tick count, for example Min="0" Max="100" ended at 68. Axes with Step, with a single bound or with neither are unchanged.
• Gantt Day and Month zoom headers follow Culture and HeaderDateFormat instead of a hard-coded M/d. The day labels of the Day zoom and the week range labels of the Month zoom use HeaderDateFormat when it is set, and otherwise the short date pattern of the Gantt culture without its year part (M/d for en-US, dd/MM for en-GB, dd.MM for de-DE). The Gantt passes its Culture and UICulture to the inner scheduler, and the zoom buttons carry a class per view (rz-gantt-view-day, -week, -month, -year, -years) so an application can hide a zoom by class instead of by position (#​2745).
• Spreadsheet no longer raises "There was an exception invoking 'OnResize'" when it is disposed, for example when a dialog that hosts it closes or the page navigates away. The virtual grid's ResizeObserver fired once more with a 0x0 size for the detached scroll container and called OnResize on an already disposed DotNetObjectReference. The observer now disconnects itself when the scroller is no longer connected, and the call is guarded like the other resize observers (#​2746).
• Spreadsheet xlsx export no longer writes applyQuotePrefix on the cell style of a quote-prefixed cell. The attribute is not part of CT_Xf in ECMA-376, so strict readers such as openpyxl refused the file with "unexpected keyword argument 'applyQuotePrefix'". Only quotePrefix="1" is written now (#​2747).

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.

Updated xunit.v3 from 4.0.1 to 4.0.2.

Release notes

Sourced from xunit.v3's releases.

No release notes found for this version range.

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