chore(deps): Bump the nuget-dependencies group with 20 updates by dependabot[bot] · Pull Request #58 · JerrettDavis/FlowLedger

New options: line charts accept null data points and either leave a gap or connect across them with ConnectNullPoints. MudDataGrid can filter an enum column by several values with the "is any of" operator. MudDivider takes child content, MudText has Truncate, MudDataGrid has ToolBarWrapContent, MudAutocomplete has OuterClass, and HierarchyColumn applies Class and the Cell* class and style parameters. (#13068, #14056, #13926, #13120, #14046, #13825, #14092)
Server data and search: MudAutocomplete, MudTable and MudDataGrid now keep the results of the newest search or load. Before, they kept whichever finished last. An autocomplete stays closed after you close it, select or clear while a search is running. A grid or table that lands past the last page goes back to the first page and keeps its loading bar until the data arrives. Popovers removed before their first render no longer leak in Interactive Server, so grouped grids with a pager stop collecting orphaned tooltips. (#13944, #14053, #14069, #14070, #14064, #14065, #14068, #13949, #14057, #14063, #14049, #14050)
Date range picker:
- MinDays and MaxDays now apply on both sides of the first clicked date.
- Hovering an earlier date previews the range.
- Changing the limits before the second click takes effect right away.
- Opening an editable picker no longer marks a valid range invalid.
- ResetAsync returns the calendar to its starting month.
(#14052, #14054, #14058, #14059, #13945, #13936)

Upgrading

The "is any of" operator appears on every enum column. Its Value is a collection of enum values. If your ServerData code doesn't handle that operator yet, hide it with Column.FilterOperators. (#14056)
More parameters raise MUD0012 when read through a component reference. This now applies to Title and SecondaryText on MudStep, and to MinDays, MaxDays, MinDate and MaxDate on the date pickers. If you treat warnings as errors, read the step values through IStepContext (for example MudStepper.Steps), or keep the values in your own fields. Setting these parameters in markup is unchanged. (#13939, #14058)
Date range pickers with MinDays set allow earlier dates. A date before the first click can become the range start when the span is within MinDays and MaxDays. A MinDays of 0 or less now behaves like 1. (#14054)

These release notes were initially generated by Nuntia. Learn more

What's Changed

New Features

MudAutocomplete: Add OuterClass parameter by @Computermatronic in MudAutocomplete: Add OuterClass parameter MudBlazor/MudBlazor#13825
MudChart: Support null data points in line charts by @pmorong in MudChart: Support null data points in line charts MudBlazor/MudBlazor#13068
MudText: Add Truncate property by @omarkurtovic in MudText: Add Truncate property MudBlazor/MudBlazor#13120
MudDataGrid: Add ToolBarWrapContent parameter by @abduladnan-mt7 in MudDataGrid: Add ToolBarWrapContent parameter MudBlazor/MudBlazor#14046
MudDataGrid: Add is-any-of filter operator for enum columns by @danielchalmers in MudDataGrid: Add is-any-of filter operator for enum columns MudBlazor/MudBlazor#14056
MudDivider: Allow child content by @Skyron92 in MudDivider: Allow child content MudBlazor/MudBlazor#13926

Bug Fixes

MudSelect: Fix render check states after scrolling with virtualization by @Ptipoi-jf in MudSelect: Fix render check states after scrolling with virtualization MudBlazor/MudBlazor#13561
MudStepper: Refresh header when MudStep Title or SecondaryText changes by @danielchalmers in MudStepper: Refresh header when MudStep Title or SecondaryText changes MudBlazor/MudBlazor#13939
MudSelect: Don't duplicate consumer attributes on the hidden input by @danielchalmers in MudSelect: Don't duplicate consumer attributes on the hidden input MudBlazor/MudBlazor#13938
MudInput: Fix legend overflowing when the label is too long in a MudDialog by @breeky-dev in MudInput: Fix legend overflowing when the label is too long in a MudDialog MudBlazor/MudBlazor#13768
MudDatePicker: Fully reset value and calendar on ResetAsync by @AtakanUk in MudDatePicker: Fully reset value and calendar on ResetAsync MudBlazor/MudBlazor#13936
MudDateRangePicker: Fix conversion error when opening an editable picker by @AtakanUk in MudDateRangePicker: Fix conversion error when opening an editable picker MudBlazor/MudBlazor#13945
MudTreeView: Fix multi-selection checkboxes for items without a value by @AtakanUk in MudTreeView: Fix multi-selection checkboxes for items without a value MudBlazor/MudBlazor#13951
MudNumericField: Keep value on blur under comma-decimal cultures by @danielchalmers in MudNumericField: Keep value on blur under comma-decimal cultures MudBlazor/MudBlazor#13956
Charts: Keep sizes and SVG values valid under comma-decimal cultures by @danielchalmers in Charts: Keep sizes and SVG values valid under comma-decimal cultures MudBlazor/MudBlazor#13957
Icons: Fix Filled.Cases icon missing its case body by @danielchalmers in Icons: Fix Filled.Cases icon missing its case body MudBlazor/MudBlazor#13959
... (truncated)

Commits viewable in compare view.

Updated Quartz from 4.6.0 to 4.6.2.

Release notes

Sourced from Quartz's releases.

4.6.2

One fix for the 4.6 line. There is no public API change, no schema change and no dependency change.

Fixed

Legacy time zone names resolve on a system without tzdata-legacy, such as Ubuntu 26.04. 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. For those seven Windows ids, .NET maps through CLDR to the legacy names, which only tzdata-legacy installs. Quartz now maps a legacy name to its canonical zone through tzdata 2026e's backward links, and resolves it under the id asked for. The id a store writes to TIME_ZONE_ID therefore does not depend on whether the host has tzdata-legacy. (#4180, from #4172)

Behaviour change

With UseTimeZoneConverter on such a host, 4.6.1 stored the canonical name (TimeZoneConverter 7.1.0 answers Europe/Kyiv for FLE Standard Time). 4.6.2 resolves the id before the plugin is asked, so it stores the id asked for. Rows already stored read back either way.

The same fix ships for 3.x in 3.22.9.

What's Changed

TimeZones.FindById resolves the tzdata legacy names, and the Windows ids CLDR maps to them, on a system without tzdata-legacy by @lahma in TimeZones.FindById resolves the tzdata legacy names, and the Windows ids CLDR maps to them, on a system without tzdata-legacy quartznet/quartznet#4180
4.6.2: legacy time zone names resolve without tzdata-legacy by @lahma in 4.6.2: legacy time zone names resolve without tzdata-legacy quartznet/quartznet#4184

Full Changelog: quartznet/quartznet@v4.6.1...v4.6.2

4.6.1

Fixes from 4.7's development for the 4.6 line. There is no public API change and no schema change. Quartz.Plugins.TimeZoneConverter now requires TimeZoneConverter 7.1.0; no other package's dependencies change.

Fixed

A start no longer resets a declared trigger's run state. Creating a scheduler re-applies every AddTrigger and ScheduleJob registration and every scheduling file through RescheduleJob. That reset TimesTriggered, so a finite WithRepeatCount or a recurrence rule's COUNT ran again from the beginning. It also dropped a retry pending at shutdown, and resumed a trigger an operator had paused on its own. While the declared schedule is unchanged, the count and the retry are now kept, and so is the pause, with its record. A changed schedule starts fresh, and an application's own RescheduleJob still ends an individual pause. (#4147, from #4128)
A [DisallowConcurrentExecution] job's completion reads only the triggers that misfired. Each completion read every waiting trigger of the job in full under TRIGGER_ACCESS to find the late ones, so draining a backlog read N rows on each of N completions, and scheduling calls waited behind the lock. A shipped delegate now reads only the job's misfired triggers, with the misfire handler's own predicate. In the #4167 workload on SQL Server (400 queued triggers on one serial job, 50 ms body), the drain went from 138 s with 137 misfire events to 101 s with 37. (#4169, from #4167)
A declared job-data type with a number, a boolean or a nested object reads back. A value of a type declared through AddTypeInfoResolver was stored, and then its job failed to load with Failed to parse JobDataMap from json. It now reads back as a Dictionary<string, string> of its members: a number or a boolean as its JSON text ("3", "true"), a nested object as its JSON, a null as null. A map that 4.6.0 stored loads. (#4161, from #4156)
A recovered firing of an ungrouped trigger is limited under its trigger group. Under UseTriggerGroupWhenUnset, a firing replayed after cluster recovery, a shutdown hand-back or startup recovery was limited under RECOVERING_JOBS, so it ran beside its group's live firings whatever the group's limit. (#4148, from #4142)
Startup recovery of a replay keeps the firing it replays. A replay of a replay named the recovery trigger rather than the original firing, and lost the original group's execution limit. Cluster recovery already kept it. (#4160)
A cron trigger's clone has a job data map of its own. CronTriggerImpl.Clone shared the original's map, so a write through either was seen by both. The other trigger types already copied it. (#4160)
Quartz.Plugins.TimeZoneConverter resolves seven more Windows ids on a system without tzdata-legacy, such as Ubuntu 26.04: FLE, India, Argentina, Greenland, Myanmar, Nepal and US Eastern Standard Time. Their CLDR names are legacy links that only tzdata-legacy installs, and TimeZoneConverter 7.1.0 maps them to the canonical names. Without the plugin those ids still fail on such a system; #4172 tracks that. (#4171)

Behaviour changes

A declared collection, or a declared object with a collection member, is refused when the map is written. The JsonSerializationException names the entry, the type and the member. Such a value used to be stored and then fail to load. (#4161)
The ADO store's completion no longer reports a late IgnoreMisfirePolicy trigger as misfired. This applies to the completion of a [DisallowConcurrentExecution], BufferOne or CancelPrevious firing, which also no longer writes such a trigger back. Acquisition fires it late, as the misfire handler and RAMJobStore already did. (#4169)

The run-state and serial-completion fixes ship for 3.x in 3.22.8.

What's Changed

A start that re-applies declared triggers keeps their run state and an individual pause by @lahma in A start that re-applies declared triggers keeps their run state and an individual pause quartznet/quartznet#4147
A recovered firing of an ungrouped trigger counts against its trigger group's execution limit, not RECOVERING_JOBS by @lahma in A recovered firing of an ungrouped trigger counts against its trigger group's execution limit, not RECOVERING_JOBS quartznet/quartznet#4148
Small 4.7 fixes: a cron trigger clone's data map, a daily trigger's end-after-count zone, recovery markers, and the options table by @lahma in Small 4.7 fixes: a cron trigger clone's data map, a daily trigger's end-after-count zone, recovery markers, and the options table quartznet/quartznet#4160
A job-data value of a declared type reads back as it was written by @lahma in A job-data value of a declared type reads back as it was written quartznet/quartznet#4161
A serial job's completion reads only the triggers that misfired, not its whole backlog by @lahma in A serial job's completion reads only the triggers that misfired, not its whole backlog quartznet/quartznet#4169
The unit tests and the trimming canary run on Ubuntu 26.04: IANA test zones and TimeZoneConverter 7.1.0 by @lahma in The unit tests and the trimming canary run on Ubuntu 26.04: IANA test zones and TimeZoneConverter 7.1.0 quartznet/quartznet#4171
4.6.1: fixes from main for the 4.6 line by @lahma in 4.6.1: fixes from main for the 4.6 line quartznet/quartznet#4177

Full Changelog: quartznet/quartznet@v4.6.0...v4.6.1

Commits viewable in compare view.

Updated Quartz.AspNetCore from 4.6.0 to 4.6.2.

Release notes

Sourced from Quartz.AspNetCore's releases.

4.6.2

One fix for the 4.6 line. There is no public API change, no schema change and no dependency change.

Fixed

Legacy time zone names resolve on a system without tzdata-legacy, such as Ubuntu 26.04. 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. For those seven Windows ids, .NET maps through CLDR to the legacy names, which only tzdata-legacy installs. Quartz now maps a legacy name to its canonical zone through tzdata 2026e's backward links, and resolves it under the id asked for. The id a store writes to TIME_ZONE_ID therefore does not depend on whether the host has tzdata-legacy. (#4180, from #4172)

Behaviour change

With UseTimeZoneConverter on such a host, 4.6.1 stored the canonical name (TimeZoneConverter 7.1.0 answers Europe/Kyiv for FLE Standard Time). 4.6.2 resolves the id before the plugin is asked, so it stores the id asked for. Rows already stored read back either way.

The same fix ships for 3.x in 3.22.9.

What's Changed

TimeZones.FindById resolves the tzdata legacy names, and the Windows ids CLDR maps to them, on a system without tzdata-legacy by @lahma in TimeZones.FindById resolves the tzdata legacy names, and the Windows ids CLDR maps to them, on a system without tzdata-legacy quartznet/quartznet#4180
4.6.2: legacy time zone names resolve without tzdata-legacy by @lahma in 4.6.2: legacy time zone names resolve without tzdata-legacy quartznet/quartznet#4184

Full Changelog: quartznet/quartznet@v4.6.1...v4.6.2

4.6.1

Fixes from 4.7's development for the 4.6 line. There is no public API change and no schema change. Quartz.Plugins.TimeZoneConverter now requires TimeZoneConverter 7.1.0; no other package's dependencies change.

Fixed

A start no longer resets a declared trigger's run state. Creating a scheduler re-applies every AddTrigger and ScheduleJob registration and every scheduling file through RescheduleJob. That reset TimesTriggered, so a finite WithRepeatCount or a recurrence rule's COUNT ran again from the beginning. It also dropped a retry pending at shutdown, and resumed a trigger an operator had paused on its own. While the declared schedule is unchanged, the count and the retry are now kept, and so is the pause, with its record. A changed schedule starts fresh, and an application's own RescheduleJob still ends an individual pause. (#4147, from #4128)
A [DisallowConcurrentExecution] job's completion reads only the triggers that misfired. Each completion read every waiting trigger of the job in full under TRIGGER_ACCESS to find the late ones, so draining a backlog read N rows on each of N completions, and scheduling calls waited behind the lock. A shipped delegate now reads only the job's misfired triggers, with the misfire handler's own predicate. In the #4167 workload on SQL Server (400 queued triggers on one serial job, 50 ms body), the drain went from 138 s with 137 misfire events to 101 s with 37. (#4169, from #4167)
A declared job-data type with a number, a boolean or a nested object reads back. A value of a type declared through AddTypeInfoResolver was stored, and then its job failed to load with Failed to parse JobDataMap from json. It now reads back as a Dictionary<string, string> of its members: a number or a boolean as its JSON text ("3", "true"), a nested object as its JSON, a null as null. A map that 4.6.0 stored loads. (#4161, from #4156)
A recovered firing of an ungrouped trigger is limited under its trigger group. Under UseTriggerGroupWhenUnset, a firing replayed after cluster recovery, a shutdown hand-back or startup recovery was limited under RECOVERING_JOBS, so it ran beside its group's live firings whatever the group's limit. (#4148, from #4142)
Startup recovery of a replay keeps the firing it replays. A replay of a replay named the recovery trigger rather than the original firing, and lost the original group's execution limit. Cluster recovery already kept it. (#4160)
A cron trigger's clone has a job data map of its own. CronTriggerImpl.Clone shared the original's map, so a write through either was seen by both. The other trigger types already copied it. (#4160)
Quartz.Plugins.TimeZoneConverter resolves seven more Windows ids on a system without tzdata-legacy, such as Ubuntu 26.04: FLE, India, Argentina, Greenland, Myanmar, Nepal and US Eastern Standard Time. Their CLDR names are legacy links that only tzdata-legacy installs, and TimeZoneConverter 7.1.0 maps them to the canonical names. Without the plugin those ids still fail on such a system; #4172 tracks that. (#4171)

Behaviour changes

A declared collection, or a declared object with a collection member, is refused when the map is written. The JsonSerializationException names the entry, the type and the member. Such a value used to be stored and then fail to load. (#4161)
The ADO store's completion no longer reports a late IgnoreMisfirePolicy trigger as misfired. This applies to the completion of a [DisallowConcurrentExecution], BufferOne or CancelPrevious firing, which also no longer writes such a trigger back. Acquisition fires it late, as the misfire handler and RAMJobStore already did. (#4169)

The run-state and serial-completion fixes ship for 3.x in 3.22.8.

What's Changed

A start that re-applies declared triggers keeps their run state and an individual pause by @lahma in A start that re-applies declared triggers keeps their run state and an individual pause quartznet/quartznet#4147
A recovered firing of an ungrouped trigger counts against its trigger group's execution limit, not RECOVERING_JOBS by @lahma in A recovered firing of an ungrouped trigger counts against its trigger group's execution limit, not RECOVERING_JOBS quartznet/quartznet#4148
Small 4.7 fixes: a cron trigger clone's data map, a daily trigger's end-after-count zone, recovery markers, and the options table by @lahma in Small 4.7 fixes: a cron trigger clone's data map, a daily trigger's end-after-count zone, recovery markers, and the options table quartznet/quartznet#4160
A job-data value of a declared type reads back as it was written by @lahma in A job-data value of a declared type reads back as it was written quartznet/quartznet#4161
A serial job's completion reads only the triggers that misfired, not its whole backlog by @lahma in A serial job's completion reads only the triggers that misfired, not its whole backlog quartznet/quartznet#4169
The unit tests and the trimming canary run on Ubuntu 26.04: IANA test zones and TimeZoneConverter 7.1.0 by @lahma in The unit tests and the trimming canary run on Ubuntu 26.04: IANA test zones and TimeZoneConverter 7.1.0 quartznet/quartznet#4171
4.6.1: fixes from main for the 4.6 line by @lahma in 4.6.1: fixes from main for the 4.6 line quartznet/quartznet#4177

Full Changelog: quartznet/quartznet@v4.6.0...v4.6.1

Commits viewable in compare view.

Updated TinyBDD from 0.19.46 to 0.19.47.

Release notes

Sourced from TinyBDD's releases.

0.19.47 What's Changed

chore(deps): bump github/codeql-action from 4.39.0 to 4.39.1 in the github-actions-dependencies group by @dependabot[bot] in chore(deps): bump github/codeql-action from 4.39.0 to 4.39.1 in the github-actions-dependencies group TinyBDD#111

Full Changelog: JerrettDavis/TinyBDD@v0.19.46...v0.19.47

Commits viewable in compare view.

Updated TinyBDD.Xunit from 0.19.46 to 0.19.47.

Release notes

Sourced from TinyBDD.Xunit's releases.

0.19.47 What's Changed

chore(deps): bump github/codeql-action from 4.39.0 to 4.39.1 in the github-actions-dependencies group by @dependabot[bot] in chore(deps): bump github/codeql-action from 4.39.0 to 4.39.1 in the github-actions-dependencies group TinyBDD#111

Full Changelog: JerrettDavis/TinyBDD@v0.19.46...v0.19.47

Commits viewable in compare view.

Updated WireMock.Net from 2.20.0 to 2.21.0.

Release notes

Sourced from WireMock.Net's releases.

2.21.0 What's Changed

Update Scriban to 7.5.3 by @StefH in Update Scriban to 7.5.3 wiremock/WireMock.Net#1526

Full Changelog: wiremock/WireMock.Net@2.20.0...2.21.0

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

Bumps Microsoft.AspNetCore.Components.WebAssembly from 10.0.13 to 10.0.14 Bumps Microsoft.AspNetCore.Components.WebAssembly.Server from 10.0.13 to 10.0.14 Bumps Microsoft.AspNetCore.Identity.EntityFrameworkCore from 10.0.13 to 10.0.14 Bumps Microsoft.AspNetCore.Mvc.Testing from 10.0.13 to 10.0.14 Bumps Microsoft.AspNetCore.OpenApi from 10.0.13 to 10.0.14 Bumps Microsoft.EntityFrameworkCore from 10.0.13 to 10.0.14 Bumps Microsoft.EntityFrameworkCore.Design from 10.0.13 to 10.0.14 Bumps Microsoft.EntityFrameworkCore.Relational from 10.0.13 to 10.0.14 Bumps Microsoft.Extensions.Configuration.Abstractions from 10.0.13 to 10.0.14 Bumps Microsoft.Extensions.DependencyInjection.Abstractions from 10.0.13 to 10.0.14 Bumps Microsoft.Extensions.Hosting from 10.0.13 to 10.0.14 Bumps Microsoft.Extensions.Logging from 10.0.13 to 10.0.14 Bumps Microsoft.Extensions.Options from 10.0.13 to 10.0.14 Bumps Microsoft.Extensions.Options.ConfigurationExtensions from 10.0.13 to 10.0.14 Bumps MudBlazor from 9.11.0 to 9.12.0 Bumps Quartz from 4.6.0 to 4.6.2 Bumps Quartz.AspNetCore from 4.6.0 to 4.6.2 Bumps TinyBDD from 0.19.46 to 0.19.47 Bumps TinyBDD.Xunit from 0.19.46 to 0.19.47 Bumps WireMock.Net from 2.20.0 to 2.21.0 --- updated-dependencies: - dependency-name: Microsoft.AspNetCore.Components.WebAssembly dependency-version: 10.0.14 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-dependencies - dependency-name: Microsoft.AspNetCore.Components.WebAssembly.Server dependency-version: 10.0.14 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-dependencies - dependency-name: Microsoft.AspNetCore.Identity.EntityFrameworkCore dependency-version: 10.0.14 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-dependencies - dependency-name: Microsoft.EntityFrameworkCore dependency-version: 10.0.14 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-dependencies - dependency-name: Microsoft.EntityFrameworkCore.Relational dependency-version: 10.0.14 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-dependencies - dependency-name: Microsoft.AspNetCore.Mvc.Testing dependency-version: 10.0.14 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-dependencies - dependency-name: Microsoft.AspNetCore.OpenApi dependency-version: 10.0.14 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-dependencies - dependency-name: Microsoft.EntityFrameworkCore.Design dependency-version: 10.0.14 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-dependencies - dependency-name: Microsoft.Extensions.Configuration.Abstractions dependency-version: 10.0.14 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-dependencies - dependency-name: Microsoft.Extensions.DependencyInjection.Abstractions dependency-version: 10.0.14 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-dependencies - dependency-name: Microsoft.Extensions.Hosting dependency-version: 10.0.14 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-dependencies - dependency-name: Microsoft.Extensions.Logging dependency-version: 10.0.14 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-dependencies - dependency-name: Microsoft.Extensions.Options dependency-version: 10.0.14 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-dependencies - dependency-name: Microsoft.Extensions.Options.ConfigurationExtensions dependency-version: 10.0.14 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-dependencies - dependency-name: MudBlazor dependency-version: 9.12.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-dependencies - dependency-name: Quartz dependency-version: 4.6.2 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-dependencies - dependency-name: Quartz.AspNetCore dependency-version: 4.6.2 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-dependencies - dependency-name: TinyBDD dependency-version: 0.19.47 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-dependencies - dependency-name: TinyBDD.Xunit dependency-version: 0.19.47 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-dependencies - dependency-name: WireMock.Net dependency-version: 2.21.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-dependencies ... Signed-off-by: dependabot[bot] <support@github.com>

dependabot Bot added the dependencies label Nov 2, 2026

github-actions Bot enabled auto-merge (squash) November 2, 2026 12:26

github-actions Bot merged commit 4a9f53e into master Nov 2, 2026
14 checks passed

dependabot Bot deleted the dependabot/nuget/nuget-dependencies-11be08409b branch November 2, 2026 12:35

Navigation Menu

Repository navigation

chore(deps): Bump the nuget-dependencies group with 20 updates - #58

chore(deps): Bump the nuget-dependencies group with 20 updates#58
github-actions[bot] merged 1 commit into
masterfrom
dependabot/nuget/nuget-dependencies-11be08409b

dependabot Bot commented on behalf of github Nov 2, 2026

Uh oh!

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Conversation

dependabot Bot commented on behalf of github Nov 2, 2026

9.12.0

Highlights

Upgrading

What's Changed

New Features

Bug Fixes

4.6.2

Fixed

Behaviour change

What's Changed

4.6.1

Fixed

Behaviour changes

What's Changed

4.6.2

Fixed

Behaviour change

What's Changed

4.6.1

Fixed

Behaviour changes

What's Changed

0.19.47

What's Changed

0.19.47

What's Changed

2.21.0

What's Changed

Uh oh!

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants