Skip to content

Update all non-major dependencies - #59

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/all-non-major-dependencies
Open

renovate[bot] wants to merge 1 commit into
masterfrom
renovate/all-non-major-dependencies

Conversation

@renovate

@renovate renovate Bot commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence Type Update Pending
@react-router/dev (source) 8.5.0 → 8.5.1 age confidence devDependencies patch
@react-router/node (source) 8.5.0 → 8.5.1 age confidence dependencies patch
@react-router/serve (source) 8.5.0 → 8.5.1 age confidence dependencies patch
Aspire.AppHost.Sdk 13.6.3 → 13.6.5 age confidence msbuild-sdk patch
Aspire.Hosting.AppHost 13.6.3 → 13.6.5 age confidence nuget patch
Aspire.Hosting.JavaScript 13.6.3 → 13.6.5 age confidence nuget patch
Aspire.Hosting.Testing 13.6.3 → 13.6.5 age confidence nuget patch
Microsoft.AspNetCore.Authentication.OpenIdConnect (source) 10.0.13 → 10.0.15 age confidence nuget patch
Microsoft.Extensions.Hosting.Systemd (source) 10.0.13 → 10.0.15 age confidence nuget patch
Microsoft.NET.Test.Sdk 18.11.0 → 18.12.0 age confidence nuget minor
OpenIddict.Server.AspNetCore (source) 7.7.2 → 7.8.0 age confidence nuget minor 7.9.0
Polly 8.8.0 → 8.9.1 age confidence nuget minor
Quartz (source) 3.22.7 → 3.22.10 age confidence nuget patch
Quartz.Extensions.DependencyInjection (source) 3.22.7 → 3.22.10 age confidence nuget patch
Quartz.Extensions.Hosting (source) 3.22.7 → 3.22.10 age confidence nuget patch
dotnet-sdk 10.0.402 → 10.0.404 age confidence dotnet-sdk patch
react-router (source) 8.5.0 → 8.5.1 age confidence dependencies patch
vite (source) 8.3.5 → 8.3.8 age confidence devDependencies patch

Release Notes

remix-run/react-router (@​react-router/dev)

v8.5.1

Compare Source

Patch Changes
  • Use resolved Vite environment output directories when reading and writing build artifacts (#​15480)
    • Finalize server-bundle manifest paths after asynchronous Vite configuration hooks complete
    • Preserve output-directory overrides applied when creating a Vite build environment
  • Run prerendering after other Vite plugins finish their application build hooks (#​15481)
    • Close React Router's build resources when another plugin's application build hook fails during react-router build
  • Updated dependencies:
remix-run/react-router (@​react-router/node)

v8.5.1

Compare Source

Patch Changes
remix-run/react-router (@​react-router/serve)

v8.5.1

Compare Source

Patch Changes
microsoft/aspire (Aspire.AppHost.Sdk)

v13.6.5: Aspire 13.6.5

What's New in Aspire 13.6.5

Patch release for Aspire 13.6 with dashboard and CLI security hardening and .NET runtime servicing updates.

🐛 Fixes
  • 🖥️ Dashboard authentication is enforced on missing and unauthorized routes — Secured dashboards now check authorization before rendering the main layout for missing routes or denied access. In browser-token mode, unauthenticated users are redirected to login with the original route preserved. Additional authentication checks protect layout, dialog, interaction, and standalone terminal-window initialization; unsecured mode is unchanged. (#​22071, 0b6bfe2, @​jamesnk)

  • 🔒 Container telemetry no longer implicitly exposes the dashboard frontend — When the Aspire container tunnel is enabled, automatic dashboard tunneling exposes only the OTLP gRPC and HTTP endpoints. Explicit references to other dashboard endpoints remain supported, and tunneling for ordinary host-resource dependencies is unchanged. (#​22071, f017f66, @​karolz-ms)

  • 🔒 CLI-generated builds and SDK working directories are isolated — Generated AppHost server and integration builds now ignore automatic MSBuild response files without changing user-authored builds or support for explicitly supplied response files. The aspire sdk generate, aspire sdk dump, and aspire sdk export commands use isolated working directories under <ASPIRE_HOME>/tmp/sdk/<unique-id>, with owner-only Unix permissions, local configuration isolation, and cleanup when the command finishes. Normal AppHost caches are unchanged. (#​22071, 1ecd7cc, @​sebastienros)

  • 🔒 Agent setup no longer writes configuration content to a shared temporary log — aspire agent init stops writing agent configuration paths, configuration content, and scan diagnostics to aspire-deprecated-scan.log in the operating system's temporary directory. Deprecated MCP command detection, migration prompts, configuration updates, and existing structured debug logging are preserved. Previously written temporary log files are not removed by this update. (#​22071, c408ec5, @​mitchdenny)

  • 🛠️ Updated .NET runtimes and dependencies for startup reliability — Refreshes bundled runtimes and .NET servicing dependencies, including .NET 10.0.14, 9.0.22, and 8.0.33, to pick up servicing fixes relevant to Native AOT process startup. (#​21348, @​joperezr)


Full Changelog: v13.6.4...v13.6.5

Full commit: b33d222049f1ecc3bc7257ec07b622fe550b2580

v13.6.4: Aspire 13.6.4

What's New in Aspire 13.6.4

Patch release for Aspire 13.6 that improves resource startup reliability, fixes Azure publishing with parameterized enum properties in TypeScript AppHosts, and tightens CLI diagnostic log permissions on Unix.

🐛 Fixes
  • 🖥️ Resources could fail to start after a DCP create request timed out — AppHost now checks whether a resource was created before retrying a timed-out or HTTP 504 request, avoiding a premature FailedToStart state when DCP completed the operation. API operations default to a 40-second timeout with an additional 20-second allowance before the first successful operation, and resource creation has a two-minute recovery budget. These limits can be configured through DcpPublisher:KubernetesApiTimeout, DcpPublisher:KubernetesInitializationAdditionalTimeout, and DcpPublisher:KubernetesCreateRecoveryTimeout. Established watch and log streams are not limited by these operation timeouts. Addresses startup timeouts reported in 13.6. Fixes #​20691. (#​20868, backport of #​20752, @​danegsta)

  • ☁️ TypeScript AppHosts could fail to publish parameterized Azure enum properties — Assigning a bicep().parameter(...) expression to an enum-valued provisioning property, such as an Azure Storage SKU name, now works instead of failing with a type-assignment error. Type checking for literal values and incompatible expression types is preserved. Fixes a scenario introduced with the Azure provisioning proxy feature in 13.6. (#​20767, backport of #​20557, @​sebastienros)

  • 🔒 CLI diagnostic logs now use owner-only permissions on Unix — Log files are restricted to owner read/write access (0600), including reused files, and the dedicated Aspire logs directory uses owner-only access (0700), repairing existing permissions when needed. Newly created custom log directories also use 0700; existing custom parent directories and Windows permission behavior are unchanged. Diagnostic logs can contain sensitive data, including dashboard login URLs, so review them before sharing. (#​21282, backport of #​21276, @​mitchdenny)


Full Changelog: v13.6.3...v13.6.4

Full commit: c89352703f78ae46de90fbf751ed8b52b77b89bf

dotnet/dotnet (Microsoft.AspNetCore.Authentication.OpenIdConnect)

v10.0.15

v10.0.14

microsoft/vstest (Microsoft.NET.Test.Sdk)

v18.12.0

Security fix

This release includes the fix for CVE-2026-105544, an elevation of privilege vulnerability in the VSTest artifact post-processor. The post-processor could consume a forged executionComplete.json written by another local user, and then run attacker-controlled output handling.

Affected: Microsoft.TestPlatform.CLI 18.11.0 and earlier. Every version from 18.11.1 on is fixed, including 18.12.0.

Microsoft.TestPlatform.CLI is the VSTest build that we ship into the .NET SDK. The recommended way to get this fix is to update your .NET SDK to the latest patched version, see the advisory for the SDK versions.

The fix is also released in the Microsoft.TestPlatform.CLI package, for completeness. That package is rarely used directly. It is not a dependency of Microsoft.NET.Test.Sdk or Microsoft.TestPlatform, so those packages do not bring it in.

Details: #​16654 and dotnet/announcements#517

Using custom Docker images or Nano Server? See #​16652

What's Changed

Full Changelog: microsoft/vstest@v18.11.0...v18.12.0

v18.11.1

Security fix

This release fixes CVE-2026-105544, an elevation of privilege vulnerability in the VSTest artifact post-processor. The post-processor could consume a forged executionComplete.json written by another local user, and then run attacker-controlled output handling.

Affected: Microsoft.TestPlatform.CLI 18.11.0.
Fixed in: Microsoft.TestPlatform.CLI 18.11.1.

Microsoft.TestPlatform.CLI is the VSTest build that we ship into the .NET SDK. The recommended way to get this fix is to update your .NET SDK to the latest patched version, see the advisory for the SDK versions.

The fix is also released in the Microsoft.TestPlatform.CLI package, for completeness. That package is rarely used directly. It is not a dependency of Microsoft.NET.Test.Sdk or Microsoft.TestPlatform, so those packages do not bring it in.

Details: #​16654 and dotnet/announcements#517

Using custom Docker images or Nano Server? See #​16652

What's Changed

  • Security fix for CVE-2026-105544, see #​16654
  • Ship Microsoft.Diagnostics.NETCore.Client in Microsoft.TestPlatform and Portable packages by @​nohwnd in #​16632
  • Fix localized resource paths in CLI source-build packages by @​nohwnd in #​16643

Full Changelog: microsoft/vstest@v18.11.0...v18.11.1

openiddict/openiddict-core (OpenIddict.Server.AspNetCore)

v7.8.0

Compare Source

This release introduces the following changes:

  • A new SetAllowedDecompressionMethods() API was introduced in the System.Net.Http integration packages to limit the decompression methods they can use when extracting HTTP responses. While not recommended, this new option can be used to mitigate the recent CVE-2026-111497 vulnerability. See #​2568 for more information (thanks @​m3nax! ❤️)

  • HTTP response payloads are no longer logged by default when encountering an error. A new EnableSensitivePayloadLogging() API was added to opt out this new behavior. See #​2558 for more information (thanks @​zengqinglei and @​m3nax! ❤️)

  • All the .NET and third-party dependencies have been updated to their latest version.

App-vNext/Polly (Polly)

v8.9.1

Compare Source

v8.9.0

Compare Source

v8.8.1

Compare Source

quartznet/quartznet (Quartz)

v3.22.10

11 fixes for the 3.x line. There is no public API change and no schema change.

Fixed

  • The dashboard's Save schedule reports an invalid cron expression as invalid. Saving an expression that does not parse replaced the trigger page with Failed to parse ITrigger from json and a Retry button. It now shows Invalid cron expression: …, the reason the preview already gave, and leaves the page and the trigger as they were. Thanks @​EnesKartal. (#​4190, closes #​4188)
  • Saving a cron schedule from the dashboard keeps the trigger on its schedule. Save schedule sent the trigger's original start back, so for a trigger that had been scheduled a while the next fire came out in the past. The scheduler treated the trigger as misfired and ran it once off its schedule. A start that has passed now moves to the whole second after the save, and the Upcoming cron fires preview follows the same rule. Thanks @​mkokkerametla for the report and @​EnesKartal for the analysis. (#​4256, closes #​4187)
  • A CronTriggerImpl clone has a job data map of its own. It used MemberwiseClone rather than the base clone that every other trigger type uses, so the clone shared the original's JobDataMap. RAMJobStore stores and hands out clones, so a write to a retrieved cron trigger's map reached the stored trigger. (#​4205)
  • Recovery of a replay keeps the firing it replays. When a recovery firing was itself recovered, startup recovery and cluster recovery overwrote the FailedJobOriginalTrigger* markers. IJobExecutionContext.RecoveringTriggerKey then named the spent recovery trigger (RECOVERING_JOBS.recover_…) instead of the original trigger, and the fire-time markers named the first replay's times. Both paths now keep the markers the recovery trigger already carries. (#​4205)
  • On .NET 11, a trigger's decimal property keeps its value. .NET 11 converts a double to the decimal nearest its exact binary value. So when a driver returns the DEC_PROP_1/2 columns as a double, as SQLite's does, 12.34 came back as 12.339999999999999857891452848. Quartz now rounds to 15 (double) or 7 (float) significant digits, as every earlier runtime did. (#​4219, from #​4210)
  • NativeJob passes its parameters to the shell on Linux. The command and its parameters were joined into one Arguments string that .NET splits on whitespace, so the parameters never reached the command. (#​4220, from #​4212)
  • Cancelling a waiting NativeJob kills the process tree, and the job ends as cancelled rather than with Error launching native command. (#​4220)
  • NativeJob reads output without foreground threads, so a child that holds its pipes open no longer keeps the host alive after shutdown. All output is still logged before the job completes, unless a process the command started holds the streams open more than 5 seconds after it exits. (#​4220)
  • NativeJob runs the system directory's cmd.exe on Windows, never one that PATH or the working directory finds first. (#​4220)
  • A dashboard at a custom path loads in a Debug build made with the .NET 11 SDK. The SDK adds a hot-reload JS initializer to every Debug build of a Blazor host. The dashboard's <base href> sent it under the dashboard path, where only blazor.web.js and opaque-redirect were mirrored. So it failed, and the Blazor circuit never started. The dashboard now serves the whole _framework tree under its path. Thanks to the Marten Studio maintainers for the report. (#​4227, from #​4224)
  • On PostgreSQL, a failed commit is reported as itself. Npgsql throws ObjectDisposedException when asked for the connection of a transaction its broken connector disposed. The store's disconnected-transaction check let that escape in place of the real error, from rollbacks, row-lock retries and the enlisted-transaction checks. A failed fire-batch or check-in commit now goes through its validator and retry as it does on other databases, and the cluster manager no longer logs Error managing cluster: NpgsqlTransaction. Thanks @​mrreddevil2412. (#​4261, from #​4255)

Packaging

Quartz.Jobs gains a net8.0 build, which .NET 8 and later now pick up instead of netstandard2.0. The Linux parameter fix and the process-tree kill need APIs only that build has. The netstandard2.0 and .NET Framework builds keep their old Linux command line, and leave a cancelled job's process running as before. They do get the other NativeJob changes.

Compatibility

On Linux with .NET 8 or later, a NativeJob command that wrapped itself in quotes to work around the old whitespace split now passes those quotes to the shell. Remove the quotes, or move the arguments to parameters.

The integration tests move to MySqlConnector 2.6.1, the first version fixed for GHSA-473q-m89c-ghf8 (#​4198). No 3.x package references the driver.

What's Changed

Fixes
  • Saving a cron schedule from the dashboard moves a start that has passed to the whole second after now (3.x) by @​lahma in #​4256
  • A transaction its driver has disposed counts as ended, so a failed commit on Npgsql is reported as itself rather than as ObjectDisposedException (3.x) by @​lahma in #​4261
Other changes
  • The integration tests use MySqlConnector 2.6.1, the version that fixed GHSA-473q-m89c-ghf8 (3.x) by @​lahma in #​4198
  • Dashboard: show an error for an invalid cron expression on save (3.x) by @​EnesKartal in #​4190
  • A cron trigger's clone has a job data map of its own, and startup and cluster recovery of a replay keep the firing it replays (3.x) by @​lahma in #​4205
  • On .NET 11, a job-data double or float read as a decimal comes back as the number that was written (3.x) by @​lahma in #​4219
  • NativeJob passes its parameters to the shell on Linux, kills the process tree when cancelled, and reads output without foreground threads (3.x) by @​lahma in #​4220
  • A dashboard at a custom path serves the whole _framework tree under its path, so the .NET 11 SDK's hot-reload initializer loads in a Debug build (3.x) by @​lahma in #​4227
  • pr-tests-unit-net11 runs the unit tests on the .NET 11 runtime (3.x) by @​lahma in #​4233

New Contributors

Full Changelog: quartznet/quartznet@v3.22.9...v3.22.10

v3.22.9

Two fixes for the 3.x line. There is no public API change and no schema change.

Fixed
  • Legacy time zone names resolve on a system without tzdata-legacy, such as Ubuntu 26.04. On .NET 8 and later, without the TimeZoneConverter plugin, seven Windows ids (FLE, India, Argentina, Greenland, Myanmar, Nepal and US Eastern Standard Time) and tzdata's legacy IANA names, such as Asia/Calcutta and Europe/Kiev, threw TimeZoneNotFoundException there. Quartz now maps a legacy name to its canonical zone through tzdata 2026e's backward links, and resolves it under the id asked for, so the id a store writes does not depend on the host. (#​4181, from #​4172)
  • A serial job's late trigger is not left BLOCKED by a custom driver delegate. With a delegate that implements IDriverDelegate but does not derive from StdAdoDelegate, the completion of a [DisallowConcurrentExecution] job could store a late trigger it let go of as BLOCKED. If that was the job's only trigger, it never fired again. Every delegate Quartz ships was unaffected. (#​4182, from #​4175)
Behaviour change
  • With the TimeZoneConverter plugin on such a host, 3.22.8 stored the canonical name (Europe/Kyiv for FLE Standard Time). 3.22.9 resolves the id before the plugin is asked, so it stores the id asked for. Rows already stored read back either way.
What's Changed
  • A serial job's completion stores a late trigger it lets go of WAITING through a delegate that does not derive from StdAdoDelegate by @​lahma in #​4182
  • TimeZoneUtil.FindTimeZoneById resolves the tzdata legacy names, and the Windows ids CLDR maps to them, on a system without tzdata-legacy (3.x) by @​lahma in #​4181

Full Changelog: quartznet/quartznet@v3.22.8...v3.22.9

v3.22.8

Fixes for the 3.x line, including a regression in 3.22.7 that made TriggerJob slower the more triggers its job had stored. There is no public API change and no schema change.

Fixed
  • TriggerJob no longer slows down as its job's backlog grows (regression in 3.22.7). 3.22.7 gave a manual firing the execution group its job's triggers share (#​4110), and found that group by loading every stored trigger of the job, three statements per trigger. A queued manual firing is a stored trigger too, so each call cost more than the one before. The group is now read with one statement. (#​4170, from #​4167)
  • A [DisallowConcurrentExecution] job's completion reads only the triggers that misfired (since 3.17.0). Each completion loaded every remaining trigger of the job under TRIGGER_ACCESS to apply the misfire policy to the late ones, so draining a backlog was quadratic in statements, and ScheduleJob and TriggerJob waited behind the lock. The completion now asks the database only for the job's misfired triggers, with the misfire handler's predicate. (#​4168, from #​4167)
  • A restart keeps a declared trigger's fire count and an individual pause. A start re-applies every AddTrigger and ScheduleJob registration and every scheduling file through RescheduleJob. That reset TimesTriggered, so a finite WithRepeatCount ran again from the beginning, and it resumed a trigger an operator had paused on its own. Both are now kept while the declared schedule is unchanged; a changed schedule starts fresh. An application's own RescheduleJob still ends an individual pause. (#​4149, from #​4128)

The #​4167 workload on SQL Server: 400 queued triggers on one serial job with a 50 ms body, which would drain in 20 s with no scheduler overhead.

Version Drain time Misfire events TriggerJob median
3.16.1 58 s 0 58 ms
3.22.7 212 s 137 1.4 s
3.22.8 50 s 0 58 ms

Against a remote database every one of those statements is a round trip, so the difference grows with latency.

Behaviour changes
  • A serial job's completion no longer reports a late IgnoreMisfirePolicy trigger to ITriggerListener.TriggerMisfired, and no longer writes it back unchanged. Acquisition fires it, as the misfire handler and RAMJobStore already did. (#​4168)
  • The completion no longer calls the protected virtual JobStoreSupport.GetTriggersForJob(conn, …) and UpdateMisfiredTrigger(conn, key, …). A subclass that overrode either to change what a completion does is bypassed there; ResumeTrigger still calls UpdateMisfiredTrigger. (#​4168)

Thanks to @​kostekk88 for the report and the repro in #​4167.

What's Changed
Other changes
  • A start that re-applies declared triggers keeps their run state and an individual pause (3.x) by @​lahma in #​4149
  • A serial job's completion reads only the misfired triggers it lets go of, not the job's whole backlog (3.x) by @​lahma in #​4168
  • A manual firing reads the execution group its job's triggers share in one statement, not by loading every trigger of the job (3.x) by @​lahma in #​4170

Full Changelog: quartznet/quartznet@v3.22.7...v3.22.8

dotnet/sdk (dotnet-sdk)

v10.0.404: .NET 10.0.15

Compare Source

Release

What's Changed

Full Changelog: dotnet/sdk@v10.0.402...v10.0.404

v10.0.403: .NET 10.0.14

Compare Source

Release

What's Changed

[!IMPORTANT]
✂ PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Between 12:00 AM and 06:59 AM, only on Tuesday (* 0-6 * * 2)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot added the automation label Nov 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants