Bump the nuget-minor-patch group with 6 updates

[dependabot]

Updated AndreGoepel.Marten.Configuration from 1.0.1 to 1.1.0.

Release notes

Sourced from AndreGoepel.Marten.Configuration's releases.

1.1.0

What's Changed

• docs: slim CLAUDE.md to repo-specific content by @​andregoepel in docs: slim CLAUDE.md to repo-specific content marten-configuration#5
• refactor: convention cleanup (AAA tests, XML docs, CancellationToken) by @​andregoepel in refactor: convention cleanup (AAA tests, XML docs, CancellationToken) marten-configuration#7
• chore: enable TreatWarningsAsErrors by @​andregoepel in chore: enable TreatWarningsAsErrors marten-configuration#10
• chore: build/config boilerplate alignment audit by @​andregoepel in chore: build/config boilerplate alignment audit marten-configuration#18
• feat: first-class protected-secret support (DataProtectorExtensions) by @​andregoepel in feat: first-class protected-secret support (DataProtectorExtensions) marten-configuration#17

Full Changelog: andregoepel/marten-configuration@v1.0.1...v1.1.0

Commits viewable in compare view.

Updated bunit from 2.7.2 to 2.8.6.

Release notes

Sourced from bunit's releases.

2.8.6

Added

• New overloads to WaitForHelpers to have async assertions and predicates. Reported by @​radmorecameron in #​1833. Fixed by @​linkdotnet.
• AddAsset to BunitContext to seed the ResourceAssetCollection exposed via ComponentBase.Assets. Reported by LasseHerget in #​1846. Implemented by @​linkdotnet.

Commits viewable in compare view.

Updated Marten from 9.19.0 to 9.21.0.

Release notes

Sourced from Marten's releases.

9.21.0

Highlights

A small, low-risk release: two bug fixes reported against 9.20.x, a LINQ ordering fix, a Newtonsoft serialization fix, and a new health-check overload for Wolverine-managed daemon distribution.

[!NOTE]
There is a change to the mt_quick_append_events PostgreSQL function in this release, and applying it is NOT mandatory or required.

You do not need to patch your database, schedule a migration, or coordinate a deployment window to take 9.21.0. The client-side half of the #​5062 fix ships in the assembly, so upgrading the NuGet package alone is sufficient — 9.21.0 is correct against the function version you already have deployed.

Under the default AutoCreate.CreateOrUpdate the function is simply refreshed the next time Marten ensures event storage exists (a CREATE OR REPLACE FUNCTION, no lock on your event data). If you run AutoCreate.None with db-patch / db-apply, your next patch will contain one extra CREATE OR REPLACE FUNCTION … mt_quick_append_events statement — apply it whenever it suits your normal cadence. See the migration guide for details.

Bug Fixes

mt_quick_append_events returned {NULL} for an empty event array (#​5062, #​5088)

array_length('{}', 1) is NULL in PostgreSQL rather than 0, so calling the bulk append function with no events returned a bigint[] whose single element was NULL. Npgsql could not read that into long[], and the resulting InvalidCastException was thrown from the batch's post-processing loop — where it displaced whatever exception had actually made the append fail. Callers were left with an unrelated, non-retryable error instead of the real one; for the reporter that dead-lettered Wolverine messages which would otherwise have been retried.

Fixed on three fronts:

• The function now COALESCEs the array length, so an empty append means what it says: zero events appended, final version unchanged.
• The append operation no longer reads the returned array when the batch carries no events — this is what makes the fix effective without any database change.
• The one code path in Marten that could reach the function with empty arrays (ProjectionUpdateBatch.WaitForCompletion, for an Append side effect that ended up with no events) no longer issues the call.

OrderBy against a dictionary indexer dropped the key (#​5063, #​5073)

OrderBy(x => x.SomeDictionary["key"]) generated SQL that ignored the indexer key, so the ordering was wrong (or arbitrary) rather than failing loudly.

Lazy LINQ sequences serialized as objects under Newtonsoft (#​5076, #​5080)

A document property holding a deferred-execution sequence (Select(...), Where(...) without a materializing call) was written by Newtonsoft as an iterator object rather than a JSON array, so it would not round-trip. These are now written as plain arrays.

IMessageBatch is called concurrently (#​5065, #​5085)

Not a behavior change, but a documentation fix worth flagging if you implement IMessageBatch yourself: the async daemon raises projection side effects from multiple threads at once (measured at up to 8 concurrent publishers across 10 threads for a single-stream projection catching up). The interface previously said nothing about this. An implementation that appends to an unsynchronized collection will silently drop messages — the same hazard, in a real outbox, that showed up here as a "flaky" test.

New

Provider-aware databaseFilter for the high-water health check (#​5061, #​5089)

AddMartenHighWaterHealthCheck's databaseFilter is captured at registration time, so it cannot resolve services — which makes it unable to express "the databases this node currently owns" when ownership is runtime state. That is precisely the case under Wolverine-managed daemon distribution, where agents are assigned per (database, tenant) and rebalanced over a node's lifetime.

There is now an overload whose filter receives the IServiceProvider and is re-evaluated on every probe:

Services.AddHealthChecks().AddMartenHighWaterHealthCheck(
    (services, database) => services.GetRequiredService<IWolverineRuntime>()
        .Agents.AllLocallyOwnedDatabaseIds()
        .Any(id => id.Name.EqualsIgnoreCase(database.Identifier)),
    staleThreshold: TimeSpan.FromSeconds(30),
    includeExternallyManaged: true);
 ... (truncated)

## 9.20.2

## What's Changed
* Fix NgramIndex to match NgramSearch's unaccent-aware mt_grams_vector expression by @​dat-honguyen in https://github.com/JasperFx/marten/pull/5060

## New Contributors
* @​dat-honguyen made their first contribution in https://github.com/JasperFx/marten/pull/5060

**Full Changelog**: https://github.com/JasperFx/marten/compare/V9.20.1...V9.20.2

## 9.20.1

Two real improvements:
1. Less log noise and faster/cleaner shutdowns at production time
2. Adjustments to the "high water mark" detection to ignore idle transactions from advisory locks in advancing the high water mark. This was a side effect of the extra work we did in 9.18 to try to stop event skipping from slow transactions

## What's Changed
* fix(#​4953): allocation fence keeps idle advisory-lock sessions from holding gap skips forever by @​jeremydmiller in https://github.com/JasperFx/marten/pull/5057
* Adopt JasperFx.Events 2.36.2: clear resolved daemons on coordinator stop, idempotent AddAsyncDaemon by @​jeremydmiller in https://github.com/JasperFx/marten/pull/5058


**Full Changelog**: https://github.com/JasperFx/marten/compare/V9.20.0...V9.20.1

## 9.20.0

Bug fixes around permutations of the natural key usage, new convenience mechanisms for querying for event store data

## What's Changed
* chore(deps-dev): bump find-my-way from 9.5.0 to 9.7.0 by @​dependabot[bot] in https://github.com/JasperFx/marten/pull/5045
* chore(deps-dev): bump postcss from 8.5.14 to 8.5.23 by @​dependabot[bot] in https://github.com/JasperFx/marten/pull/5046
* Retire the previous natural key row when the key changes (#​5041) by @​jeremydmiller in https://github.com/JasperFx/marten/pull/5049
* Add FetchStreamStatePlan + FetchStreamPlan: raw event stream fetches as batchable query plans by @​uniquelau in https://github.com/JasperFx/marten/pull/5043
* StreamEventState + StreamEvents result types for Marten.AspNetCore by @​jeremydmiller in https://github.com/JasperFx/marten/pull/5053
* Natural key table: scope the FK guard, and land the partitioned-FK repro (#​5044) by @​jeremydmiller in https://github.com/JasperFx/marten/pull/5050
* Adopt JasperFx.Events 2.36.0: shard failure classification, drain timeout docs, natural key extraction by @​jeremydmiller in https://github.com/JasperFx/marten/pull/5054


**Full Changelog**: https://github.com/JasperFx/marten/compare/V9.19.0...V9.20.0

Commits viewable in [compare view](https://github.com/JasperFx/marten/compare/V9.19.0...V9.21.0).
</details>

Updated [Marten.AspNetCore](https://github.com/JasperFx/marten) from 9.19.0 to 9.21.0.

<details>
<summary>Release notes</summary>

_Sourced from [Marten.AspNetCore's releases](https://github.com/JasperFx/marten/releases)._

## 9.21.0

## Highlights

A small, low-risk release: two bug fixes reported against 9.20.x, a LINQ ordering fix, a Newtonsoft serialization fix, and a new health-check overload for Wolverine-managed daemon distribution.

> [!NOTE]
> **There is a change to the `mt_quick_append_events` PostgreSQL function in this release, and applying it is _NOT_ mandatory or required.**
>
> You do not need to patch your database, schedule a migration, or coordinate a deployment window to take 9.21.0. The client-side half of the #​5062 fix ships in the assembly, so upgrading the NuGet package alone is sufficient — 9.21.0 is correct against the function version you already have deployed.
>
> Under the default `AutoCreate.CreateOrUpdate` the function is simply refreshed the next time Marten ensures event storage exists (a `CREATE OR REPLACE FUNCTION`, no lock on your event data). If you run `AutoCreate.None` with `db-patch` / `db-apply`, your next patch will contain one extra `CREATE OR REPLACE FUNCTION … mt_quick_append_events` statement — apply it whenever it suits your normal cadence. See the [migration guide](https://martendb.io/migration-guide.html#key-changes-in-9-21-0) for details.

## Bug Fixes

### `mt_quick_append_events` returned `{NULL}` for an empty event array ([#​5062](https://github.com/JasperFx/marten/issues/5062), [#​5088](https://github.com/JasperFx/marten/pull/5088))

`array_length('{}', 1)` is `NULL` in PostgreSQL rather than `0`, so calling the bulk append function with no events returned a `bigint[]` whose single element was `NULL`. Npgsql could not read that into `long[]`, and the resulting `InvalidCastException` was thrown from the batch's post-processing loop — where it **displaced whatever exception had actually made the append fail**. Callers were left with an unrelated, non-retryable error instead of the real one; for the reporter that dead-lettered Wolverine messages which would otherwise have been retried.

Fixed on three fronts:

* The function now `COALESCE`s the array length, so an empty append means what it says: zero events appended, final version unchanged.
* The append operation no longer reads the returned array when the batch carries no events — this is what makes the fix effective without any database change.
* The one code path in Marten that could reach the function with empty arrays (`ProjectionUpdateBatch.WaitForCompletion`, for an `Append` side effect that ended up with no events) no longer issues the call.

### `OrderBy` against a dictionary indexer dropped the key ([#​5063](https://github.com/JasperFx/marten/issues/5063), [#​5073](https://github.com/JasperFx/marten/pull/5073))

`OrderBy(x => x.SomeDictionary["key"])` generated SQL that ignored the indexer key, so the ordering was wrong (or arbitrary) rather than failing loudly.

### Lazy LINQ sequences serialized as objects under Newtonsoft ([#​5076](https://github.com/JasperFx/marten/issues/5076), [#​5080](https://github.com/JasperFx/marten/pull/5080))

A document property holding a deferred-execution sequence (`Select(...)`, `Where(...)` without a materializing call) was written by Newtonsoft as an iterator *object* rather than a JSON array, so it would not round-trip. These are now written as plain arrays.

### `IMessageBatch` is called concurrently ([#​5065](https://github.com/JasperFx/marten/issues/5065), [#​5085](https://github.com/JasperFx/marten/pull/5085))

Not a behavior change, but a documentation fix worth flagging if you implement `IMessageBatch` yourself: the async daemon raises projection side effects from **multiple threads at once** (measured at up to 8 concurrent publishers across 10 threads for a single-stream projection catching up). The interface previously said nothing about this. An implementation that appends to an unsynchronized collection will silently drop messages — the same hazard, in a real outbox, that showed up here as a "flaky" test.

## New

### Provider-aware `databaseFilter` for the high-water health check ([#​5061](https://github.com/JasperFx/marten/issues/5061), [#​5089](https://github.com/JasperFx/marten/pull/5089))

`AddMartenHighWaterHealthCheck`'s `databaseFilter` is captured at registration time, so it cannot resolve services — which makes it unable to express "the databases this node currently owns" when ownership is runtime state. That is precisely the case under Wolverine-managed daemon distribution, where agents are assigned per (database, tenant) and rebalanced over a node's lifetime.

There is now an overload whose filter receives the `IServiceProvider` and is re-evaluated on **every probe**:

```csharp
Services.AddHealthChecks().AddMartenHighWaterHealthCheck(
    (services, database) => services.GetRequiredService<IWolverineRuntime>()
        .Agents.AllLocallyOwnedDatabaseIds()
        .Any(id => id.Name.EqualsIgnoreCase(database.Identifier)),
    staleThreshold: TimeSpan.FromSeconds(30),
    includeExternallyManaged: true);
 ... (truncated)

## 9.20.2

## What's Changed
* Fix NgramIndex to match NgramSearch's unaccent-aware mt_grams_vector expression by @​dat-honguyen in https://github.com/JasperFx/marten/pull/5060

## New Contributors
* @​dat-honguyen made their first contribution in https://github.com/JasperFx/marten/pull/5060

**Full Changelog**: https://github.com/JasperFx/marten/compare/V9.20.1...V9.20.2

## 9.20.1

Two real improvements:
1. Less log noise and faster/cleaner shutdowns at production time
2. Adjustments to the "high water mark" detection to ignore idle transactions from advisory locks in advancing the high water mark. This was a side effect of the extra work we did in 9.18 to try to stop event skipping from slow transactions

## What's Changed
* fix(#​4953): allocation fence keeps idle advisory-lock sessions from holding gap skips forever by @​jeremydmiller in https://github.com/JasperFx/marten/pull/5057
* Adopt JasperFx.Events 2.36.2: clear resolved daemons on coordinator stop, idempotent AddAsyncDaemon by @​jeremydmiller in https://github.com/JasperFx/marten/pull/5058


**Full Changelog**: https://github.com/JasperFx/marten/compare/V9.20.0...V9.20.1

## 9.20.0

Bug fixes around permutations of the natural key usage, new convenience mechanisms for querying for event store data

## What's Changed
* chore(deps-dev): bump find-my-way from 9.5.0 to 9.7.0 by @​dependabot[bot] in https://github.com/JasperFx/marten/pull/5045
* chore(deps-dev): bump postcss from 8.5.14 to 8.5.23 by @​dependabot[bot] in https://github.com/JasperFx/marten/pull/5046
* Retire the previous natural key row when the key changes (#​5041) by @​jeremydmiller in https://github.com/JasperFx/marten/pull/5049
* Add FetchStreamStatePlan + FetchStreamPlan: raw event stream fetches as batchable query plans by @​uniquelau in https://github.com/JasperFx/marten/pull/5043
* StreamEventState + StreamEvents result types for Marten.AspNetCore by @​jeremydmiller in https://github.com/JasperFx/marten/pull/5053
* Natural key table: scope the FK guard, and land the partitioned-FK repro (#​5044) by @​jeremydmiller in https://github.com/JasperFx/marten/pull/5050
* Adopt JasperFx.Events 2.36.0: shard failure classification, drain timeout docs, natural key extraction by @​jeremydmiller in https://github.com/JasperFx/marten/pull/5054


**Full Changelog**: https://github.com/JasperFx/marten/compare/V9.19.0...V9.20.0

Commits viewable in [compare view](https://github.com/JasperFx/marten/compare/V9.19.0...V9.21.0).
</details>

Updated [Quartz.Extensions.Hosting](https://github.com/quartznet/quartznet) from 3.18.2 to 3.19.1.

<details>
<summary>Release notes</summary>

_Sourced from [Quartz.Extensions.Hosting's releases](https://github.com/quartznet/quartznet/releases)._

## 3.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 https://github.com/quartznet/quartznet/pull/3188
* Fix DailyTimeIntervalTrigger infinite fire loop during DST spring-forward (#​332) by @​lahma in https://github.com/quartznet/quartznet/pull/3190


**Full Changelog**: https://github.com/quartznet/quartznet/compare/v3.19.0...v3.19.1


## 3.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 https://github.com/quartznet/quartznet/pull/3137
* Add fluent CronExpressionBuilder for building cron expressions programmatically (3.x) by @​lahma in https://github.com/quartznet/quartznet/pull/3139
* Support for specifying 'L' and 'LW' with other days in day-of-month field by @​lahma in https://github.com/quartznet/quartznet/pull/2759
* Add preferred node (node affinity) for cluster trigger pinning by @​lahma in https://github.com/quartznet/quartznet/pull/3013
* Store auto-pin as a flag column instead of an "auto:" name prefix by @​lahma in https://github.com/quartznet/quartznet/pull/3144
* Clamp misfire handler and cluster manager sleeps after system clock jumps (#​1508) by @​lahma in https://github.com/quartznet/quartznet/pull/3147
* Update packages and cleanup by @​lahma in https://github.com/quartznet/quartznet/pull/3151
* Migrate the build from NUKE to Fallout (3.x) by @​lahma in https://github.com/quartznet/quartznet/pull/3163
* Exclude the build orchestrator from SonarQube analysis (3.x) by @​lahma in https://github.com/quartznet/quartznet/pull/3166
* Prepare v3.19.0 release by @​lahma in https://github.com/quartznet/quartznet/pull/3169


**Full Changelog**: https://github.com/quartznet/quartznet/compare/v3.18.2...v3.19.0


Commits viewable in [compare view](https://github.com/quartznet/quartznet/compare/v3.18.2...v3.19.1).
</details>

Updated [Radzen.Blazor](https://github.com/radzenhq/radzen-blazor) from 11.1.7 to 11.1.9.

<details>
<summary>Release notes</summary>

_Sourced from [Radzen.Blazor's releases](https://github.com/radzenhq/radzen-blazor/releases)._

## 11.1.8

# 11.1.8 - 2026-07-27

### Fixes
- **RadzenTextBox, RadzenTextArea, RadzenMask, RadzenPassword, RadzenAutoComplete** - bound inputs no longer reset their displayed value when used inside a `RenderFragment` created by another component - most commonly inline dialog content passed to `DialogService.OpenAsync`. Such fragments never re-flow parameters, so the component kept a stale value and wiped the typed text from the input on blur while the bound variable kept it. The local value assignment is now unconditional, matching Blazor's own `InputBase` behavior.
- **Popups** - popups no longer get permanently stuck open when the closing animation never runs or is canceled - e.g. app-level CSS such as reduced-motion resets with `animation: none`. Closing now hides the popup immediately when no close animation is actually running, and the `ClosePopup()` API reliably recovers a stuck popup. Fixes #​2601.
- **RadzenDialog** - opening a nested dialog no longer breaks resize and drag handling of the outer dialog. Each dialog now has its own resize observer and titlebar drag handler instead of sharing a single global slot. Thanks to @​I-Info!
- **RadzenUpload** - the `Method` and `Stream` parameters are now honored when uploading via the `Upload()` method with `Auto=false`. The manual upload path always sent a POST multipart request regardless of the configured method.


Commits viewable in [compare view](https://github.com/radzenhq/radzen-blazor/commits).
</details>

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-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

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


</details>

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.