Bump the nuget group with 26 updates by dependabot[bot] · Pull Request #241 · KaliCZ/DemoPage

dependabot · 2026-07-21T13:52:50Z

Updated Kalicz.StrongTypes from 1.2.0 to 2.0.1.

Release notes

Sourced from Kalicz.StrongTypes's releases.

2.0.1

A patch release: DataAnnotations range validation now sees through the numeric wrappers, WinForms two-way binding is verified end-to-end, and the Roslyn components got a structural hardening.

`[Range]` works on numeric wrappers (#126)

The numeric types and Digit now implement IConvertible. Therefore:

[Range(1, 100)] public Positive<int>? Quantity { get; set; }   // this now works
[Range(typeof(Positive<int>), "1", "100")] public Positive<int>? Quantity { get; set; }   // this has always worked

Small improvements

Full E2E suite for WinForms to validate the parsing and two-way binding. (#127)
Bump to Roslyn 5.0.0, because we target dotnet 10 anyway. (#128)
The code-fix providers moved into separate project so the analyzer DLL no longer references Microsoft.CodeAnalysis.Workspaces. No change for users - still part of the core package (#128)

Skill

The Claude / Codex skill ships as strongtypes-skill.tar.gz below:

mkdir -p .claude/skills/strongtypes
curl -L https://github.com/KaliCZ/StrongTypes/releases/download/v2.0.1/strongtypes-skill.tar.gz | tar -xz -C .claude/skills/strongtypes

Full changelog: KaliCZ/StrongTypes@v2.0.0...v2.0.1

2.0.0

Strong types now carry their TypeConverter on the type itself, which makes two integration surfaces work with zero setup — and retires a package.

Breaking changes

Kalicz.StrongTypes.Wpf is retired. The types now carry [TypeConverter], so binding works out-of-the-box.
PartitionMatch parameter names are now successes / errors instead of success/error. The callbacks receive whole partitions.

Configuration binding — the invariant is the validation rule

A wrapper sits directly on an options class; ConfigurationBinder converts through the type's own TypeConverter, so a bad value fails with the config path, the value, and the broken invariant — no [Range], no custom validator. Add ValidateOnStart() to fail at startup instead of on the first request.

New package: `Kalicz.StrongTypes.Configuration`

BindStrongTypes() closes the gap validation cannot see: the key that isn't there. It fails startup when any property declared non-nullable — wrapper or plain string — is still null after binding, at every depth (nested options, collection elements, dictionary values), reading the intent from your nullable annotations instead of per-property [Required]:

builder.Services.AddOptions<ClientOptions>()
    .BindStrongTypes(builder.Configuration.GetSection("Client"))
    .ValidateOnStart();

New analyzer: ST0004

A plain Bind / Configure that would leave a non-nullable wrapper unchecked now gets a warning, with a code fix that rewrites Bind → BindStrongTypes (and names the package to add when it isn't referenced yet). Ships inside the core package.

Also

Numeric wrappers implement IFormattable, ISpanFormattable, and ISpanParsable<T>.
The Claude / Codex skill was reworked for v2 (including a new Email reference) and ships as strongtypes-skill.tar.gz below:

mkdir -p .claude/skills/strongtypes
curl -L https://github.com/KaliCZ/StrongTypes/releases/download/v2.0.0/strongtypes-skill.tar.gz | tar -xz -C .claude/skills/strongtypes

Full changelog: KaliCZ/StrongTypes@v1.2.0...v2.0.0

Commits viewable in compare view.

Updated Kalicz.StrongTypes.OpenApi.Swashbuckle from 1.2.0 to 2.0.1.

Release notes

Sourced from Kalicz.StrongTypes.OpenApi.Swashbuckle's releases.

2.0.1

A patch release: DataAnnotations range validation now sees through the numeric wrappers, WinForms two-way binding is verified end-to-end, and the Roslyn components got a structural hardening.

`[Range]` works on numeric wrappers (#126)

The numeric types and Digit now implement IConvertible. Therefore:

[Range(1, 100)] public Positive<int>? Quantity { get; set; }   // this now works
[Range(typeof(Positive<int>), "1", "100")] public Positive<int>? Quantity { get; set; }   // this has always worked

Small improvements

Full E2E suite for WinForms to validate the parsing and two-way binding. (#127)
Bump to Roslyn 5.0.0, because we target dotnet 10 anyway. (#128)
The code-fix providers moved into separate project so the analyzer DLL no longer references Microsoft.CodeAnalysis.Workspaces. No change for users - still part of the core package (#128)

Skill

The Claude / Codex skill ships as strongtypes-skill.tar.gz below:

mkdir -p .claude/skills/strongtypes
curl -L https://github.com/KaliCZ/StrongTypes/releases/download/v2.0.1/strongtypes-skill.tar.gz | tar -xz -C .claude/skills/strongtypes

Full changelog: KaliCZ/StrongTypes@v2.0.0...v2.0.1

2.0.0

Strong types now carry their TypeConverter on the type itself, which makes two integration surfaces work with zero setup — and retires a package.

Breaking changes

Kalicz.StrongTypes.Wpf is retired. The types now carry [TypeConverter], so binding works out-of-the-box.
PartitionMatch parameter names are now successes / errors instead of success/error. The callbacks receive whole partitions.

Configuration binding — the invariant is the validation rule

A wrapper sits directly on an options class; ConfigurationBinder converts through the type's own TypeConverter, so a bad value fails with the config path, the value, and the broken invariant — no [Range], no custom validator. Add ValidateOnStart() to fail at startup instead of on the first request.

New package: `Kalicz.StrongTypes.Configuration`

BindStrongTypes() closes the gap validation cannot see: the key that isn't there. It fails startup when any property declared non-nullable — wrapper or plain string — is still null after binding, at every depth (nested options, collection elements, dictionary values), reading the intent from your nullable annotations instead of per-property [Required]:

builder.Services.AddOptions<ClientOptions>()
    .BindStrongTypes(builder.Configuration.GetSection("Client"))
    .ValidateOnStart();

New analyzer: ST0004

A plain Bind / Configure that would leave a non-nullable wrapper unchecked now gets a warning, with a code fix that rewrites Bind → BindStrongTypes (and names the package to add when it isn't referenced yet). Ships inside the core package.

Also

Numeric wrappers implement IFormattable, ISpanFormattable, and ISpanParsable<T>.
The Claude / Codex skill was reworked for v2 (including a new Email reference) and ships as strongtypes-skill.tar.gz below:

mkdir -p .claude/skills/strongtypes
curl -L https://github.com/KaliCZ/StrongTypes/releases/download/v2.0.0/strongtypes-skill.tar.gz | tar -xz -C .claude/skills/strongtypes

Full changelog: KaliCZ/StrongTypes@v1.2.0...v2.0.0

Commits viewable in compare view.

Updated Marten from 9.15.3 to 9.17.1.

Release notes

Sourced from Marten's releases.

9.17.0 High-water health check: opt-in `autoRestart` + heartbeat primary signal (#4986)

Builds on the detection-only check from 9.16 (#4984). Requires JasperFx 2.32.0 (jasperfx#539), which this release rolls up to (#4987).

Opt-in autoRestart — AddMartenHighWaterHealthCheck(TimeSpan? staleThreshold = null, long minimumGap = 1, bool autoRestart = false). When the check is Unhealthy and autoRestart is on, it asks the local projection coordinator's daemon to restart the high-water agent's poll loop only — the mark is never advanced — capped to once per staleness window per database. The cycle is still reported Unhealthy so an alert still fires. Intended for Solo / leader nodes.
Heartbeat is now the primary staleness signal — when EnableExtendedProgressionTracking is on, the high-water agent stamps a liveness heartbeat on the HighWaterMark row every poll cycle. Heartbeat age proves the loop is cycling independent of whether the mark advances, so a quiet store is never a false positive, and a dead agent is caught even when projections are fully caught up (the exact #4961 blind spot). The original sequence-gap heuristic is retained as the ExtendedProgression-off fallback.

Full changelog: JasperFx/marten@V9.16.1...V9.17.0

9.16.1

Async daemon data-safety release: the high water detection can no longer advance past "outstanding" event sequence numbers — sequences reserved by transactions that are still in flight — which could silently skip those events in async projections under concurrent append load (bulk imports being the classic case). Root-caused and fixed from discussion #4953.

The four closed mechanisms:

The GapDetector command batched three statements, each reading its own READ COMMITTED snapshot — commits landing mid-command could defeat every gap check and silently advance the mark over an in-flight append, regardless of StaleSequenceThreshold. Detection is now a single statement / single snapshot.
Projection rebuilds and forced catch-up looped the gap-skipping detection toward the reserved sequence last_value, mowing through in-flight gaps. CheckNowAsync (JasperFx.Events 2.29.1) now targets the highest committed sequence and simply waits for in-flight appends to land.
The stale fallback could teleport the mark to reserved last_value - 32 across thousands of in-flight reservations on an idle-then-suddenly-busy store, because its gate measured staleness against mt_event_progression.last_updated. The threshold is now measured from when each specific gap was first observed.
Wall-clock stale skipping could not tell a slow transaction from a rolled-back one. Before skipping any stale gap, Marten now checks PostgreSQL for evidence that a transaction which could still fill the gap is alive (pg_locks on the mt_events tables, open transactions in pg_stat_activity, in-progress write xids from pg_current_snapshot()), and holds while any exists — by default Marten never knowingly skips past a live appender. Only provably-dead gaps (rolled-back appends) are skipped, bounded to the sequence ceiling observed with the gap, and every skip is logged at Warning with its exact range.

New knobs on StoreOptions.Projections: UseTransactionEvidenceForGapSkipping (default true; false restores the previous wall-clock behavior) and SkipStaleGapsDespiteLiveTransactionsAfter (default null = never skip a live appender; PostgreSQL's idle_in_transaction_session_timeout is the recommended backstop against leaked sessions).

What's Changed

fix(#4953): high water detection never crosses outstanding event sequences by @jeremydmiller in fix(#4953): high water detection never crosses outstanding event sequences JasperFx/marten#4977
Consumes JasperFx.Events 2.29.1 (fix(marten#4953): CheckNowAsync targets the committed ceiling, time-bounded JasperFx/jasperfx#530)

Full Changelog: JasperFx/marten@V9.16.0...V9.16.1

9.16.0

Lot of CritterWatch, couple bug fixes too

What's Changed

Fix AdvancedSql/raw-SQL scalar queries for reference-typed columns (byte[], IPAddress, etc.) by @mdissel in Fix AdvancedSql/raw-SQL scalar queries for reference-typed columns (byte[], IPAddress, etc.) JasperFx/marten#4960
fix(#4961): PostgresqlListenWakeup falls back to a timeout wait when the DB is unreachable by @jeremydmiller in fix(#4961): PostgresqlListenWakeup falls back to a timeout wait when the DB is unreachable JasperFx/marten#4965
Bump JasperFx to 2.28.0; declare EventProjection doc types for rebuild teardown (#4685 COPY) by @jeremydmiller in Bump JasperFx to 2.28.0; declare EventProjection doc types for rebuild teardown (#4685 COPY) JasperFx/marten#4969
fix(#4966): update natural key on projection rebuild (JasperFx 2.28.1) by @jeremydmiller in fix(#4966): update natural key on projection rebuild (JasperFx 2.28.1) JasperFx/marten#4970
test(#4963): verify + document the blue/green side-effect gate by @jeremydmiller in test(#4963): verify + document the blue/green side-effect gate JasperFx/marten#4971
fix(#4964): hold the Normal high-water mark before a leading sequence gap by @jeremydmiller in fix(#4964): hold the Normal high-water mark before a leading sequence gap JasperFx/marten#4972
refactor(#4968): route stream archive through the shared Weasel event-store seam by @jeremydmiller in refactor(#4968): route stream archive through the shared Weasel event-store seam JasperFx/marten#4973
feat(#4962): targeted per-cell ReadProjectionProgressAsync on MartenDatabase by @jeremydmiller in feat(#4962): targeted per-cell ReadProjectionProgressAsync on MartenDatabase JasperFx/marten#4974
feat(#4975): exact ReadProjectionProgressAsync(ShardName) override + JasperFx 2.29.0 by @jeremydmiller in feat(#4975): exact ReadProjectionProgressAsync(ShardName) override + JasperFx 2.29.0 JasperFx/marten#4976

Full Changelog: JasperFx/marten@v9.15.4...V9.16.0

9.15.4 What's Changed

Support Where Any on collections when using strongly typed Ids by @ximon in Support Where Any on collections when using strongly typed Ids JasperFx/marten#4957
Bump ws from 8.19.0 to 8.21.1 by @dependabot[bot] in Bump ws from 8.19.0 to 8.21.1 JasperFx/marten#4955
#4956 — lock down ForTenant() conjoined-document tenant isolation by @jeremydmiller in #4956 — lock down ForTenant() conjoined-document tenant isolation JasperFx/marten#4958

New Contributors

@ximon made their first contribution in Support Where Any on collections when using strongly typed Ids JasperFx/marten#4957

Full Changelog: JasperFx/marten@v9.15.3...v9.15.4

Commits viewable in compare view.

Updated Microsoft.AspNetCore.Authentication.JwtBearer from 10.0.9 to 10.0.10.

Release notes

Sourced from Microsoft.AspNetCore.Authentication.JwtBearer's releases.