Repository navigation
Update all non-major dependencies - #59
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
8.5.0→8.5.18.5.0→8.5.18.5.0→8.5.113.6.3→13.6.513.6.3→13.6.513.6.3→13.6.513.6.3→13.6.510.0.13→10.0.1510.0.13→10.0.1518.11.0→18.12.07.7.2→7.8.07.9.08.8.0→8.9.13.22.7→3.22.103.22.7→3.22.103.22.7→3.22.1010.0.402→10.0.4048.5.0→8.5.18.3.5→8.3.8Release Notes
remix-run/react-router (@react-router/dev)
v8.5.1Compare Source
Patch Changes
react-router buildreact-router@8.5.1@react-router/node@8.5.1@react-router/serve@8.5.1remix-run/react-router (@react-router/node)
v8.5.1Compare Source
Patch Changes
react-router@8.5.1remix-run/react-router (@react-router/serve)
v8.5.1Compare Source
Patch Changes
react-router@8.5.1@react-router/express@8.5.1@react-router/node@8.5.1microsoft/aspire (Aspire.AppHost.Sdk)
v13.6.5: Aspire 13.6.5What'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, andaspire sdk exportcommands 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 initstops writing agent configuration paths, configuration content, and scan diagnostics toaspire-deprecated-scan.login 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.4What'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
FailedToStartstate 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 throughDcpPublisher:KubernetesApiTimeout,DcpPublisher:KubernetesInitializationAdditionalTimeout, andDcpPublisher: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 use0700; 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.15v10.0.14microsoft/vstest (Microsoft.NET.Test.Sdk)
v18.12.0Security 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.jsonwritten by another local user, and then run attacker-controlled output handling.Affected:
Microsoft.TestPlatform.CLI18.11.0 and earlier. Every version from 18.11.1 on is fixed, including 18.12.0.Microsoft.TestPlatform.CLIis 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.CLIpackage, for completeness. That package is rarely used directly. It is not a dependency ofMicrosoft.NET.Test.SdkorMicrosoft.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.1Security 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.jsonwritten by another local user, and then run attacker-controlled output handling.Affected:
Microsoft.TestPlatform.CLI18.11.0.Fixed in:
Microsoft.TestPlatform.CLI18.11.1.Microsoft.TestPlatform.CLIis 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.CLIpackage, for completeness. That package is rarely used directly. It is not a dependency ofMicrosoft.NET.Test.SdkorMicrosoft.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.11.1
openiddict/openiddict-core (OpenIddict.Server.AspNetCore)
v7.8.0Compare Source
This release introduces the following changes:
A new
SetAllowedDecompressionMethods()API was introduced in theSystem.Net.Httpintegration 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.1Compare Source
v8.9.0Compare Source
net10.0plusnet8.0forPollyby @martincostello in #3292v8.8.1Compare Source
quartznet/quartznet (Quartz)
v3.22.1011 fixes for the 3.x line. There is no public API change and no schema change.
Fixed
Invalid cron expression: …, the reason the preview already gave, and leaves the page and the trigger as they were. Thanks @EnesKartal. (#4190, closes #4188)CronTriggerImplclone has a job data map of its own. It usedMemberwiseClonerather than the base clone that every other trigger type uses, so the clone shared the original'sJobDataMap.RAMJobStorestores and hands out clones, so a write to a retrieved cron trigger's map reached the stored trigger. (#4205)FailedJobOriginalTrigger*markers.IJobExecutionContext.RecoveringTriggerKeythen 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)doubleto thedecimalnearest its exact binary value. So when a driver returns theDEC_PROP_1/2columns as adouble, as SQLite's does,12.34came back as12.339999999999999857891452848. Quartz now rounds to 15 (double) or 7 (float) significant digits, as every earlier runtime did. (#4219, from #4210)NativeJobpasses its parameters to the shell on Linux. The command and its parameters were joined into oneArgumentsstring that .NET splits on whitespace, so the parameters never reached the command. (#4220, from #4212)NativeJobkills the process tree, and the job ends as cancelled rather than withError launching native command. (#4220)NativeJobreads 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)NativeJobruns the system directory'scmd.exeon Windows, never one thatPATHor the working directory finds first. (#4220)<base href>sent it under the dashboard path, where onlyblazor.web.jsandopaque-redirectwere mirrored. So it failed, and the Blazor circuit never started. The dashboard now serves the whole_frameworktree under its path. Thanks to the Marten Studio maintainers for the report. (#4227, from #4224)ObjectDisposedExceptionwhen 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 logsError managing cluster: NpgsqlTransaction. Thanks @mrreddevil2412. (#4261, from #4255)Packaging
Quartz.Jobsgains anet8.0build, which .NET 8 and later now pick up instead ofnetstandard2.0. The Linux parameter fix and the process-tree kill need APIs only that build has. Thenetstandard2.0and .NET Framework builds keep their old Linux command line, and leave a cancelled job's process running as before. They do get the otherNativeJobchanges.Compatibility
On Linux with .NET 8 or later, a
NativeJobcommand 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 toparameters.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
Other changes
New Contributors
Full Changelog: quartznet/quartznet@v3.22.9...v3.22.10
v3.22.9Two fixes for the 3.x line. There is no public API change and no schema change.
Fixed
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 asAsia/CalcuttaandEurope/Kiev, threwTimeZoneNotFoundExceptionthere. Quartz now maps a legacy name to its canonical zone through tzdata 2026e'sbackwardlinks, and resolves it under the id asked for, so the id a store writes does not depend on the host. (#4181, from #4172)BLOCKEDby a custom driver delegate. With a delegate that implementsIDriverDelegatebut does not derive fromStdAdoDelegate, the completion of a[DisallowConcurrentExecution]job could store a late trigger it let go of asBLOCKED. If that was the job's only trigger, it never fired again. Every delegate Quartz ships was unaffected. (#4182, from #4175)Behaviour change
Europe/KyivforFLE 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
Full Changelog: quartznet/quartznet@v3.22.8...v3.22.9
v3.22.8Fixes for the 3.x line, including a regression in 3.22.7 that made
TriggerJobslower the more triggers its job had stored. There is no public API change and no schema change.Fixed
TriggerJobno 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)[DisallowConcurrentExecution]job's completion reads only the triggers that misfired (since 3.17.0). Each completion loaded every remaining trigger of the job underTRIGGER_ACCESSto apply the misfire policy to the late ones, so draining a backlog was quadratic in statements, andScheduleJobandTriggerJobwaited 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)AddTriggerandScheduleJobregistration and every scheduling file throughRescheduleJob. That resetTimesTriggered, so a finiteWithRepeatCountran 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 ownRescheduleJobstill 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.
TriggerJobmedianAgainst a remote database every one of those statements is a round trip, so the difference grows with latency.
Behaviour changes
IgnoreMisfirePolicytrigger toITriggerListener.TriggerMisfired, and no longer writes it back unchanged. Acquisition fires it, as the misfire handler andRAMJobStorealready did. (#4168)protected virtualJobStoreSupport.GetTriggersForJob(conn, …)andUpdateMisfiredTrigger(conn, key, …). A subclass that overrode either to change what a completion does is bypassed there;ResumeTriggerstill callsUpdateMisfiredTrigger. (#4168)Thanks to @kostekk88 for the report and the repro in #4167.
What's Changed
Other changes
Full Changelog: quartznet/quartznet@v3.22.7...v3.22.8
dotnet/sdk (dotnet-sdk)
v10.0.404: .NET 10.0.15Compare Source
Release
What's Changed
Full Changelog: dotnet/sdk@v10.0.402...v10.0.404
v10.0.403: .NET 10.0.14Compare Source
Release
What's Changed
Configuration
📅 Schedule: (UTC)
* 0-6 * * 2)🚦 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.
This PR was generated by Mend Renovate. View the repository job log.