Update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@react-router/dev (source)	8.2.0 → 8.3.0
@react-router/node (source)	8.2.0 → 8.3.0
@react-router/serve (source)	8.2.0 → 8.3.0
Quartz (source)	3.18.2 → 3.19.1
Quartz.Extensions.DependencyInjection (source)	3.18.2 → 3.19.1
Quartz.Extensions.Hosting (source)	3.18.2 → 3.19.1
SQLitePCLRaw.bundle_e_sqlite3	3.0.3 → 3.0.5
react (source)	19.2.7 → 19.2.8
react-dom (source)	19.2.7 → 19.2.8
vite (source)	8.1.4 → 8.1.5

---

Release Notes

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

v8.3.0

Compare Source

Minor Changes

• Restart react-router dev with --conditions=development when not already configured (#​15291)

Patch Changes

• Allow typescript@7 to be used (#​15317)

Unstable Changes

⚠️ Unstable features are not recommended for production use

• Add unstable_rsc/client-version client build version virtual module (#​15318)

• Support the subResourceIntegrity config option in RSC Framework Mode (#​15321)

Migration guide

No changes are required when using the default RSC SSR entry. If you maintain a custom app/entry.ssr.tsx, import the new virtual module and pass its hashes to React's importMap render option:

+import subResourceIntegrity from "virtual:react-router/unstable_rsc/subresource-integrity";

return renderToReadableStream(<RSCStaticRouter getPayload={getPayload} />, {
  ...options,
  bootstrapScriptContent,
  formState,
+ importMap: subResourceIntegrity
+   ? { integrity: subResourceIntegrity }
+   : undefined,
  signal: request.signal,
});

• Updated dependencies:
  • react-router@8.3.0
  • @react-router/node@8.3.0
  • @react-router/serve@8.3.0

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

v8.3.0

Compare Source

Patch Changes

• Allow typescript@7 to be used (#​15317)
• Updated dependencies:
  • react-router@8.3.0

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

v8.3.0

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@8.3.0
  • @react-router/express@8.3.0
  • @react-router/node@8.3.0

quartznet/quartznet (Quartz)

v3.19.1

Quartz.NET 3.19.1 is a small bug fix release with two targeted fixes: DailyTimeIntervalTrigger no longer gets stuck in an infinite fire loop on DST spring-forward days, and StdSchedulerFactory.GetScheduler(schedName) now creates the scheduler when the name asked for is its own. There are no API or schema changes, so it is a drop-in upgrade from 3.19.0.

Highlights

• DailyTimeIntervalTrigger no longer spins on DST transition days — GetFireTimeAfter could return a time at or before the one it was given, which makes QuartzSchedulerThread fire the trigger, compute the same next fire time, and fire again — pinning a CPU core and flooding the log. Two independent causes, both on a spring-forward day: the DST correction added for #​1114 was applied to every interval size and in either direction (so every interval of an hour or less was affected, in every DST time zone), and the daily rollover to StartTimeOfDay reused whatever UTC offset the previous fire time carried (so in time zones that move the clock at midnight, such as Chile, StartTimeOfDay 00:00 resolved to an instant before the transition — the same instant that was passed in). Verified across 3024 combinations of 12 time zones, both transitions, 21 intervals and 6 start times: 468 combinations produced non-advancing fire times before, none do now. (#​3190, fixes #​332)
  • Behavior change worth noting: the same fix stops sub-hour triggers silently dropping the last hour of a fall-back day. A 5-minute trigger now fires 300 times through the 25-hour day, ending at 23:55 local, instead of 288 times ending at 22:55.
• StdSchedulerFactory.GetScheduler(schedName) creates its own scheduler — asking a factory for the scheduler it is configured to produce returned null until somebody had called GetScheduler() first. It now creates it. Any other name stays a pure lookup, so probing for a scheduler somebody else owns still has no side effects, and the name comparison is case-insensitive to match how SchedulerRepository indexes names. The DI factory has behaved this way since #​2845; this brings the property-configured factory in line. (#​3188, reported in #​2786, originally proposed in #​360)

What's Changed

• Create the scheduler when it is looked up by its own name (#​360) by @​lahma in #​3188
• Fix DailyTimeIntervalTrigger infinite fire loop during DST spring-forward (#​332) by @​lahma in #​3190

Full Changelog: quartznet/quartznet@v3.19.0...v3.19.1

v3.19.0

Quartz.NET 3.19.0 is a feature release: it adds node affinity for clustered scheduling, a fluent cron-expression builder, and richer L/LW day-of-month expressions, plus clock-jump resilience and a modernized build and publishing pipeline. The public API is unchanged (all additions are additive), so it is a drop-in upgrade — with two things to note: the new node-affinity columns are an optional schema migration (the feature degrades gracefully without them), and a handful of previously-broken L/LW/W cron expressions now fire correctly (see below).

Highlights

• Node affinity for clustered trigger pinning — pin a trigger to a preferred node with TriggerBuilder.WithPreferredNode(...); the node is preferred for acquisition but the trigger is still stolen on failover so it is never stranded if that node goes down. Adds optional PREFERRED_NODE / PREFERRED_NODE_AUTO columns for ADO.NET job stores (database/schema_30_add_preferred_node.sql); when the columns are absent the scheduler logs a warning and behaves exactly as before. (#​3013, #​3144)
• Fluent CronExpressionBuilder — compose cron expressions programmatically, one field at a time, instead of hand-writing the string — handy when a schedule is assembled from user input such as a scheduling UI. (#​3139)
• L and LW combinable with other day-of-month values — the day-of-month field now accepts expressions such as 1,15,L and the new LW-n / L-nW grammar. This also corrects several previously-buggy edge cases: 29W/31W no longer silently skip short months, L-30W no longer throws mid-schedule, and 1,15W now applies W to each day rather than only the first. These corrections change the fire times of a few expressions that were previously broken — review any stored L/LW/W day-of-month expressions. (#​2759)
• Resilience to system clock jumps — the misfire handler and cluster manager now clamp their sleep intervals after the system clock jumps forward or backward, so a clock step no longer causes a busy-spin or an absurdly long sleep. (#​3147, fixes #​1508)
• Modernized build & publishing — the build orchestrator moved from the unmaintained NUKE to Fallout (#​3163), and packages now publish to nuget.org via GitHub OIDC trusted publishing rather than a stored API key. Dependencies were also refreshed (#​3151).

Note for CronScheduleBuilder users: AtHourAndMinuteOnGivenDaysOfWeek / WeeklyOnDayAndHourAndMinute now emit textual day-of-week names (e.g. MON,WED rather than 2,4). The schedules are identical, but the generated CRON_EXPRESSION string differs — relevant only if you compare stored cron strings byte-for-byte.

What's Changed

• Serve Blazor plumbing under custom DashboardPath for prefix-forwarding reverse proxies (3.x) (#​3134) by @​lahma in #​3137
• Add fluent CronExpressionBuilder for building cron expressions programmatically (3.x) by @​lahma in #​3139
• Support for specifying 'L' and 'LW' with other days in day-of-month field by @​lahma in #​2759
• Add preferred node (node affinity) for cluster trigger pinning by @​lahma in #​3013
• Store auto-pin as a flag column instead of an "auto:" name prefix by @​lahma in #​3144
• Clamp misfire handler and cluster manager sleeps after system clock jumps (#​1508) by @​lahma in #​3147
• Update packages and cleanup by @​lahma in #​3151
• Migrate the build from NUKE to Fallout (3.x) by @​lahma in #​3163
• Exclude the build orchestrator from SonarQube analysis (3.x) by @​lahma in #​3166
• Prepare v3.19.0 release by @​lahma in #​3169

Full Changelog: quartznet/quartznet@v3.18.2...v3.19.0

ericsink/SQLitePCL.raw (SQLitePCLRaw.bundle_e_sqlite3)

v3.0.5

Update the lib dependency for SQLitePCLRaw.bundle_e_sqlite3 to package ID SQLite version 3.53.4.

v3.0.4

Update SQLitePCLRaw.bundle_e_sqlite3 to reference SourceGear.sqlite3 version 3.53.3.

react/react (react)

v19.2.8

Compare Source

react/react (react-dom)

v19.2.8

Compare Source

vitejs/vite (vite)

v8.1.5

Compare Source

Please refer to CHANGELOG.md for details.

---

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 becomes conflicted, 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.

[not-adam]

Mira PR Walkthrough

🔍 Reviewing this PR…

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: src/MPlusKeybot.Web/package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: undefined@undefined
npm error Found: react-router@8.2.0
npm error node_modules/react-router
npm error   react-router@"8.2.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer react-router@"8.3.0" from @react-router/node@8.3.0
npm error node_modules/@react-router/node
npm error   @react-router/node@"8.3.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-08-01T18_28_24_671Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-08-01T18_28_24_671Z-debug-0.log

[not-adam]

Mira Review Summary

The PR updates @react-router/node, @react-router/serve, and @react-router/dev from 8.2.0 to 8.3.0 in src/MPlusKeybot.Web/package.json, but leaves react-router pinned at 8.2.0 on line 15. This monorepo version mismatch can cause runtime and build failures, and must be resolved before merging.

Key Issues

	Issue	Location
🔴	react-router is pinned at 8.2.0 while sibling @react-router/* packages were updated to 8.3.0 — this is a monorepo version mismatch that can cause runtime and build failures.	src/MPlusKeybot.Web/package.json:15

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.