Bump the nuget group with 6 updates

[dependabot]

Updated Kalicz.StrongTypes from 1.1.1 to 1.2.0.

Release notes

Sourced from Kalicz.StrongTypes's releases.

1.2.0

StrongTypes v1.2.0

Adds interval strong types — a full family of range types with JSON, EF Core, and OpenAPI support — plus EF Core support for Email and for non-public strong-type properties.

✨ Interval strong types (#​77 + #​119)

Four range types over any struct, IComparable<T> (int, DateOnly, DateTime, decimal, …):

• FiniteInterval<T> — both ends required
• Interval<T> — both ends optional (one must be provided)
• IntervalFrom<T> / IntervalUntil<T> — one end bounded

Highlights:

• Always correct - start never after end.
• Supports any IComparable.
• Set operations: Contains, Overlaps, GetOverlap; implicit widening and explicit narrowing between the four variants.
• More helpers for DateTime and DateOnly intervals. Converting back and forth, count calendar days (.Days()) and contains works across both types.
• OpenAPI: interval schemas generated for both Microsoft.OpenApi and Swashbuckle.
• JSON: serializes as { "Start", "End" }; optionally StartInclusive and EndInclusive properties.
• Inclusive by default, with per-bound inclusivity (half-open [1, 5), etc.) and validated construction (Create / TryCreate).

🗄️ EF Core

• Intervals map two ways: two indexable endpoint columns (the default — inclusive-only) or one JSON column (keeps each value's inclusivity). A corrupt row (Start > End) throws on read.
• Email now persists through EF Core (#​115).
• Non-public strong-type properties — an internal/private DDD backing field — get their value converter automatically once mapped (#​113).

🔒 Security

• Bump Microsoft.OpenApi to clear GHSA-v5pm-xwqc-g5wc (#​114).

Full changelog: KaliCZ/StrongTypes@v1.1.1...v1.2.0

Commits viewable in compare view.

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

Release notes

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

1.2.0

StrongTypes v1.2.0

Adds interval strong types — a full family of range types with JSON, EF Core, and OpenAPI support — plus EF Core support for Email and for non-public strong-type properties.

✨ Interval strong types (#​77 + #​119)

Four range types over any struct, IComparable<T> (int, DateOnly, DateTime, decimal, …):

• FiniteInterval<T> — both ends required
• Interval<T> — both ends optional (one must be provided)
• IntervalFrom<T> / IntervalUntil<T> — one end bounded

Highlights:

• Always correct - start never after end.
• Supports any IComparable.
• Set operations: Contains, Overlaps, GetOverlap; implicit widening and explicit narrowing between the four variants.
• More helpers for DateTime and DateOnly intervals. Converting back and forth, count calendar days (.Days()) and contains works across both types.
• OpenAPI: interval schemas generated for both Microsoft.OpenApi and Swashbuckle.
• JSON: serializes as { "Start", "End" }; optionally StartInclusive and EndInclusive properties.
• Inclusive by default, with per-bound inclusivity (half-open [1, 5), etc.) and validated construction (Create / TryCreate).

🗄️ EF Core

• Intervals map two ways: two indexable endpoint columns (the default — inclusive-only) or one JSON column (keeps each value's inclusivity). A corrupt row (Start > End) throws on read.
• Email now persists through EF Core (#​115).
• Non-public strong-type properties — an internal/private DDD backing field — get their value converter automatically once mapped (#​113).

🔒 Security

• Bump Microsoft.OpenApi to clear GHSA-v5pm-xwqc-g5wc (#​114).

Full changelog: KaliCZ/StrongTypes@v1.1.1...v1.2.0

Commits viewable in compare view.

Updated Marten from 9.12.0 to 9.15.3.

Release notes

Sourced from Marten's releases.

9.15.2

Marten 9.15.2

A patch release. Both fixes come out of the same 512-tenant-database production deployment, reported by @​erdtsieck, and both turned out to be worse than the reports described.

Bulk event insert ran a full schema apply on every batch

#​4946 — fixed in #​4949

The batch BulkInsertEventsAsync overloads opened with Storage.ApplyAllConfiguredChangesToDatabaseAsync() on every call.

That is not a cheap check. It calls Tenancy.BuildDatabases() and runs a full schema delta — partition introspection plus information_schema sweeps — across every database in the store. So a sharded store paid one apply per database, per batch. On the reporting deployment, each ~1,000-event batch was triggering 512 schema applies.

The measured effect: import throughput collapsed to ~17 events/s, against >3,000/s for the streaming overload. A 686k-event tenant projected to roughly 11 hours. The connection pool filled with ~370 backends whose last statement was Weasel's partition-introspection query, which fed directly into the server-wide connection pressure that deployment was already fighting.

That the streaming overload BulkInsertEventStreamAsync has no such call and is fine is the tell: the schema apply was never part of the contract. It was a leftover.

The apply is now:

• skipped entirely when the effective AutoCreate is None — it is a no-op there by contract, so all that remained was the introspection cost; and
• otherwise run at most once per database the import actually touches, memoized on IMartenDatabase.Identifier.

One subtlety worth recording, because it is the kind of thing that bites later: the memoized apply deliberately does not take a caller's CancellationToken. The first caller to arrive owns the single in-flight task that every concurrent caller for that database awaits — so binding that shared task to one caller's token would let a single cancelled batch fail sibling batches that were never cancelled. Each caller applies its own token at the await site instead. A schema apply is short and idempotent, so letting it run to completion is the cheaper trade.

Under AutoCreate.None, the event storage must already exist before import. That is the documented contract and it matches the streaming overload — but if you were previously relying on the per-call apply to create it for you under a non-None store, note the change.

The document bulk-insert path (BulkInsertAsync / BulkInsertDocumentsAsync) is unaffected. It routes through the ordinary per-feature EnsureStorageExistsAsync that Weasel already memoizes, not a full-store delta.

Tenant provisioning silently under-provisioned partitions

#​4944 — fixed in #​4950

AddPartitionToAllTables, and the tenant-provisioning paths built on it, walked the calling store's StoreOptions to decide which tables needed a list partition for a new tenant.

So any tool or host that provisions tenants from a store which doesn't register every document type silently under-provisioned. Document types unknown to the caller never got their partitions — and the tenant then failed with a Postgres 23514 check-constraint violation on first write to the missing partition. Nothing failed at provisioning time; the damage surfaced later, somewhere else.

The workaround was "the provisioning tool must register all document types," which re-creates schema knowledge in a second place and drifts as document types are added.

The sweep is now database-driven: it enumerates tenant list-partitioned tables from the Postgres catalog, so a partially-registered store still provisions every partitioned table it finds.

Scoping is enforced inside the catalog query rather than filtered in memory afterward:

• Schema — the store's own AllSchemaNames() only. Foreign partitioned tables in a shared database are never touched.
• Partition shape — LIST strategy, exactly one key column, and that column named tenant_id. This is the filter that matters most, and it is what keeps the sweep off Marten's own non-tenant list partitioning: UseArchivedStreamPartitioning keys mt_events on is_archived, and ByList() keys on its own field. Without it, a "helpful" sweep would start adding tenant partitions to tables partitioned on something else entirely.
• External management — tables marked ByExternallyManagedListPartitions() are subtracted.

Opt out with SweepPartitionedTablesFromDatabase (default on). No Weasel change was required.

Known limitation, and it is a real one: a document type registered into a schema the calling store has never heard of stays invisible to the schema filter — a store cannot own a schema it does not know exists. Single-schema stores (the default, and the reporting deployment's shape) are fully covered. Closing this properly would need a persisted table list alongside mt_tenant_partitions.

---

... (truncated)

9.15.1

Patch release for a silent data-correctness regression. If you use ForTenant() on an identity-mapped or dirty-tracked session, upgrade.

Fixed

• #​4947 — ForTenant() on an identity session stopped returning tenancy-neutral documents (reported by @​dervagabund, with a repro — thank you). A ForTenant() view of an identity- or dirty-tracked session no longer saw global (tenancy-neutral) documents tracked by the parent session. Since a global document has exactly one row per id for the whole database, LoadAsync through the ForTenant view missed the identity map, went to the database, and returned null for a document that is there. A silent wrong answer, not an error.

  Affected: 9.13.0, 9.14.x, 9.15.0. Introduced by the fix for #​4801, which tenant-scoped the identity map and version tracker for ForTenant sessions. That was correct for conjoined documents — where the same id means a different document per tenant — but it was applied per session rather than per document type, so it also isolated document types that are tenancy-neutral and must be shared.

  Sharing is now decided per document type. A nested ForTenant session shares the parent's identity-map and version-tracker entry for a type only when the storage is identity-mapped, the type is not Conjoined, and the nested session's database is the same instance as the parent's (under database-per-tenant, the same id in another tenant's database is a different document even for a tenancy-neutral type). The isolation introduced by #​4801 is preserved exactly — the Bug_4801 suite still passes, and the new tests include guard rails asserting conjoined documents stay isolated.

Full changelog: JasperFx/marten@9.15.0...9.15.1

9.15.0

Closed issues

• #​4942 — sharded tenancy: auto-assign never repaired half-provisioned tenants (PR #​4945). findOrAssignTenantDatabaseAsync returned early on an existing assignment row, skipping createPartitionsForTenant + per-tenant event-sequence provisioning — so a tenant whose provisioning was interrupted (assignment committed, partitions missing) failed every write with 23514 forever. Both early-return paths (including a second race-window hole under the advisory lock) now run the same idempotent repair the explicit AddTenantToShardAsync(tenantId, databaseId) overload always ran, guarded to once per process per tenant via the resolution cache.
• #​4941 — two-day silent projection outage (closed with full mapping). Root cause was #​4942; the invisibility was JasperFx/jasperfx#​506/#​507, fixed in JasperFx 2.27.0 which this release consumes.

Also in this release

• Bundles the fixed JasperFx.Events.SourceGenerator analyzer (JasperFx/jasperfx#​505) — CS1061 compile break for no-parameterless-ctor aggregates with instance Apply returning the aggregate.
• Follow-up enhancement filed as #​4944 (database-driven partition sweep via pg_inherits) for the #​4943 provisioning-tool scenario.

Verified against Wolverine (full solution + CoreTests/MartenTests/distribution/Http suites, zero failures) and CritterWatch before publishing. Thanks to @​erdtsieck for the dump-verified root-cause analysis.

9.14.1

Marten 9.14.1 is a patch release focused on a substantial round of LINQ query-translation improvements, plus event-store partitioning, high-water, and AoT fixes, and refreshed Weasel/JasperFx dependencies.

LINQ query translation

This release significantly expands what the LINQ provider can push down to PostgreSQL instead of falling back to slower strategies or throwing:

• Collection Any(predicate) filters now translate to JSONPath and OR-of-containment strategies, and the old explode/ctid fallback has been replaced by a correlated EXISTS strategy. All() shapes and duplicated array fields moved onto the same EXISTS strategy. The net effect is correct, index-friendlier SQL for nested-collection predicates.
• Indexing into complex child collections inside Where() clauses is now supported (e.g. x.Children[0].Name == "...").
• Aggregates over collections — Sum/Min/Max/Average — can now be used inside Where() clauses.
• Regex.IsMatch() is translated in Where() clauses.
• IComparable.CompareTo() now works for non-string comparables such as Guid (#​4920), alongside broader CompareTo() coverage, string IsOneOf via the ?| operator, and CollectionIsEmpty via ICollectionAware.
• GinIndexJsonDataMember() was added for member-scoped expression GIN indexes.

#​4916 — subclass queries now use duplicated fields and the base id

Querying a document subclass and filtering on a Duplicate()'d field or the base-class id previously emitted a JSONB filter (CAST(d.data ->> 'FarmId' as uuid)) instead of the real column, missing the duplicated column and the primary-key index:

o.Schema.For<Animal>().AddSubClass<Cow>().Duplicate(x => x.FarmId);

Query<Cow>().Where(x => x.FarmId == id)  // now: d.farm_id = :p0     (was: CAST(d.data ->> 'FarmId' ...))
Query<Cow>().Where(x => x.Id == id)      // now: d.id = :p0          (was: CAST(d.data ->> 'Id' ...))

A subclass shares its parent's table, so the parent's column-backed members (duplicated fields, the id, the soft-delete flag) are now inherited by the subclass's query member resolution. Querying the parent type was already correct and is unchanged.

Event store, partitioning & daemon

• #​4924 — hyphenated / GUID tenant ids under UseTenantPartitionedEvents. Registering a tenant whose partition suffix contains a - (so every GUID tenant id) made ApplyAllConfiguredChangesToDatabaseAsync() throw 42601 because the per-tenant CREATE SEQUENCE / DROP SEQUENCE DDL emitted the identifier unquoted. The schema-apply statements are now quoted (matching the quick-append function and the imperative provisioning path), so hyphenated tenants migrate cleanly. Quote — not sanitize — so the append function can still resolve the sequence by its raw suffix.
• #​4915 — projection coordinator shutdown. The projection coordinator now drains on disposal, and via the Weasel 9.16.3 bump the advisory-lock ObjectDisposedException path latches-and-rethrows so a HotCold cold node's leadership loop terminates instead of re-polling a disposed data source during shutdown.
• #​4913 — high-water scan under partitioning (JasperFx 2.26.0). Under UseTenantPartitionedEvents the store-global high-water agent was continuously running select max(seq_id) from mt_events, an unfiltered scan that fans out across every tenant partition on every poll. That store-global mark is not used to advance tenant projections (they advance per-tenant), so the recurring scan is now skipped under partitioning; tenant high water is driven by the per-tenant coordinator and poll timer.
• jasperfx#​502 (#​4922) — GetProjectionStatusesAsync now resolves the correct named database.

AoT / trimming

• #​4917 — corrected AoT annotations in the event graph.
• The AddEventType / QueryRawEventDataOnly generic-constraint tightening was reversed, and event-mapping construction now routes through the cached GenericFactoryCache while preserving the trimming root (#​4930).

Dependencies

• Weasel 9.16.3 (#​4932) — advisory-lock disposed-pool fix (marten#​4915).
• JasperFx 2.26.0 — the #​4913 high-water fix, plus 2.25.0's ShardState.DatabaseIdentifier (jasperfx#​501).

Closed issues

#​4913, #​4915, #​4916, #​4917, #​4924, and jasperfx#​502.

9.14.0

Marten 9.14.0 is the recommended upgrade for all 9.x users. It combines the LINQ SQL-injection security fix (first shipped in 9.13.0) with the fix for the projection-coordinator shutdown race in #​4874 and the accompanying dependency updates.

Beyond the LINQ updates, this made the new Per-Tenant Event Partitioning much more robust as we're testing that in conjunction with a JasperFx client for ludicrous scalability.

🔒 Security — SQL injection in the LINQ provider (GHSA-rfx3-98h7-v3xp)

Several LINQ / tenant-management code paths interpolated a runtime, potentially attacker-influenced value into generated SQL as a single-quoted literal without escaping or parameterization. A value containing a single quote could break out of the literal and inject SQL. The primary vector — a Dictionary<,> indexer key in a Where filter (a common "filter by attribute name" / EAV pattern) — was reported privately with an executed proof-of-concept and enabled filter / multi-tenant authorization bypass and blind data exfiltration.

Fixed sinks (#​4911):

• DictionaryItemMember — dictionary indexer key, e.g. Where(x => x.Attributes[key] == v)
• DictionaryContainsKeyFilter — Dictionary.ContainsKey(key) (Newtonsoft serializer + the Enum branch, which bypass System.Text.Json's quote escaping)
• SelectParser — a constant string projected through Select(x => new { L = runtimeString })
• DeleteAllForTenant — tenant id reaching per-tenant projection teardown (now parameterized)
• DatabaseScopedTenantPartitions — tenant id inlined into partition DDL
• EventLoader — per-tenant partition-pruning literal (defense-in-depth)

Each sink now escapes embedded single quotes or binds the value as a parameter; regression tests lock down every vector, and a follow-up LINQ-wide audit cleared the rest of the query hot path (full-text search, string-method translations, comparisons, IsOneOf/Contains/subset operators, and patching paths). Affected versions: 7.0.0 – 9.12.0. Also patched in 8.37.4 (8.x line) and 9.13.0.

Reported responsibly by @​svenclaesson — thank you. See advisory GHSA-rfx3-98h7-v3xp (CVE pending assignment).

🛠️ Reliability — projection-coordinator shutdown drain race (#​4874)

On host shutdown, the native HotCold projection coordinator could abort with ObjectDisposedException: 'Npgsql.PoolingDataSource' — the coordinator's leadership poll issued an OpenAsync against an already-disposed data source while tenancy was tearing down. This is the "case B" ordering storm reported against #​4874 (distinct from the async-tenancy foundation laid in #​4907, which did not resolve it).

The fix ships through the dependency updates below, with a Marten-side regression test (Bug_4874_coordinator_drain_ordering, #​4912):

• JasperFx 2.24.1 (jasperfx#​499/#​500) — ProjectionCoordinatorBase terminates the leadership loop on a disposed data source / wrapped cancellation instead of re-polling.
• Weasel 9.16.2 (weasel#​349/#​350) — AdvisoryLock guards against a disposed NpgsqlDataSource during shutdown (short-circuits while disposing and treats a disposed-pool ObjectDisposedException as a non-acquire rather than propagating).

⬆️ Dependency updates

• JasperFx 2.24.0 → 2.24.1
• Weasel 9.16.1 → 9.16.2
• Weasel.EntityFrameworkCore 9.2.1 → 9.16.2 (released from its prior version hold now that the Weasel line is published)

Full changelog since 9.13.0

• #​4911 — SQL injection fix in the LINQ provider (carried into this release)
• #​4912 — regression test for the #​4874 case-B coordinator-drain ordering storm
• JasperFx 2.24.1 / Weasel 9.16.2 / EFCore 9.16.2 bump (#​4874 shutdown-race fix)

9.13.0

Security release. Fixes SQL injection in the LINQ provider via unescaped string literals (#​4911).

Several LINQ / tenant-management code paths interpolated a runtime, potentially attacker-influenced value into generated SQL as a single-quoted literal without escaping or parameterization; a value containing a single quote could break out and inject SQL. The primary vector — a Dictionary<,> indexer key in a Where filter — was reported privately with an executed proof-of-concept (filter / multi-tenant authorization bypass, blind exfiltration).

Fixed sinks:

• DictionaryItemMember — dictionary indexer key
• DictionaryContainsKeyFilter — ContainsKey key (Newtonsoft serializer + Enum branch)
• SelectParser — constant string projected via Select(...)
• DeleteAllForTenant — tenant id in per-tenant projection teardown (now parameterized)
• DatabaseScopedTenantPartitions — tenant id in partition DDL
• EventLoader — per-tenant partition-pruning literal (defense-in-depth)

All 9.x users should upgrade. The 8.x line is fixed in 8.37.4. See advisory GHSA-rfx3-98h7-v3xp.

Commits viewable in compare view.

Updated ModelContextProtocol from 2.0.0-preview.1 to 2.0.0-preview.2.

Release notes

Sourced from ModelContextProtocol's releases.

2.0.0-preview.2

This second preview of the 2.0.0 series advances the SDK's alignment with the upcoming 2026-07-28 MCP protocol revision: it adds client-side conformance diagnostics for the SEP-2549 caching hints, makes Streamable HTTP error responses echo the request id per the base protocol and SEP-2243, and fully stabilizes now-stable protocol properties so consumer-defined source generators serialize them correctly. Separately -- and unrelated to the protocol revision -- it introduces DeferChangedEvents() on McpServerPrimitiveCollection<T> for batching list_changed notifications when registering primitives in bulk. There are no breaking changes relative to v2.0.0-preview.1.

What's Changed

• Document caching behavior and warn on non-conformant draft cacheable results (SEP-2549 follow-up) #​1669 by @​tarekgh
• Fully stabilize now-stable protocol properties #​1686 by @​eiriktsarpalis (co-authored by @​Copilot)
• Echo request id in post-parse Streamable HTTP error responses #​1687 by @​tarekgh
• Add DeferChangedEvents() to McpServerPrimitiveCollection for batched change notifications #​1689 by @​jeffhandley (co-authored by @​Copilot)

Documentation Updates

• Update package READMEs as part of the release process #​1683 by @​jeffhandley (co-authored by @​Copilot)

Acknowledgements

• @​cclabadmin submitted issue #​1677 (resolved by #​1687)
• @​lewing submitted issue #​1688 (resolved by #​1689)
• @​PranavSenthilnathan @​halter73 @​davidortinau @​jeffhandley @​lewing @​tarekgh reviewed pull requests

Full Changelog: modelcontextprotocol/csharp-sdk@v2.0.0-preview.1...v2.0.0-preview.2

Commits viewable in compare view.

Updated ModelContextProtocol.AspNetCore from 2.0.0-preview.1 to 2.0.0-preview.2.

Release notes

Sourced from ModelContextProtocol.AspNetCore's releases.

2.0.0-preview.2

This second preview of the 2.0.0 series advances the SDK's alignment with the upcoming 2026-07-28 MCP protocol revision: it adds client-side conformance diagnostics for the SEP-2549 caching hints, makes Streamable HTTP error responses echo the request id per the base protocol and SEP-2243, and fully stabilizes now-stable protocol properties so consumer-defined source generators serialize them correctly. Separately -- and unrelated to the protocol revision -- it introduces DeferChangedEvents() on McpServerPrimitiveCollection<T> for batching list_changed notifications when registering primitives in bulk. There are no breaking changes relative to v2.0.0-preview.1.

What's Changed

• Document caching behavior and warn on non-conformant draft cacheable results (SEP-2549 follow-up) #​1669 by @​tarekgh
• Fully stabilize now-stable protocol properties #​1686 by @​eiriktsarpalis (co-authored by @​Copilot)
• Echo request id in post-parse Streamable HTTP error responses #​1687 by @​tarekgh
• Add DeferChangedEvents() to McpServerPrimitiveCollection for batched change notifications #​1689 by @​jeffhandley (co-authored by @​Copilot)

Documentation Updates

• Update package READMEs as part of the release process #​1683 by @​jeffhandley (co-authored by @​Copilot)

Acknowledgements

• @​cclabadmin submitted issue #​1677 (resolved by #​1687)
• @​lewing submitted issue #​1688 (resolved by #​1689)
• @​PranavSenthilnathan @​halter73 @​davidortinau @​jeffhandley @​lewing @​tarekgh reviewed pull requests

Full Changelog: modelcontextprotocol/csharp-sdk@v2.0.0-preview.1...v2.0.0-preview.2

Commits viewable in compare view.

Updated OpenTelemetry.Instrumentation.Runtime from 1.15.1 to 1.16.0.

Release notes

Sourced from OpenTelemetry.Instrumentation.Runtime's releases.

1.16.0

• NuGet: OpenTelemetry.Extensions.AWS v1.16.0

  • Fix sampling behaviour to be compatible with .NET 11.
    (#​4396)

  • Updated OpenTelemetry core component version(s) to 1.16.0.
    (#​4487)

  See CHANGELOG for details.

• NuGet: OpenTelemetry.Instrumentation.AWS v1.16.0

  • Add instrumentation scope version and schema URL to metrics and traces.
    (#​4063)

  • Pass AWS attribute values to created meters as tags.
    (#​4063)

  • Capture SNS TopicArn as the aws.sns.topic.arn span attribute.
    (#​4043)

  • Add cloud.region attribute to all AWS SDK client spans.
    (#​4043)

  • Add messaging attributes for AWS SNS and SQS.
    (#​4043)

  • BREAKING: Update latest AWS Semantic Conventions to 1.40.0.
    (#​4043)

  • Fix suppression scope leakage when SuppressDownstreamInstrumentation is
    enabled.
    (#​4304)

  See CHANGELOG for details.

• NuGet: OpenTelemetry.Instrumentation.AWSLambda v1.16.0

  • Update System.Text.Json for netstandard2.0 to 8.0.5.
    (#​4154)

  • Add instrumentation scope version and schema URL to traces.
    (#​4063)

  See CHANGELOG for details.

1.16.0-rc.1

• NuGet: OpenTelemetry.Instrumentation.Process v1.16.0-rc.1

  • Updated semantic conventions to
    v1.42.0.
    (#​4602)

    • Breaking Change: The process.cpu.time metric attribute process.cpu.state
      was renamed to cpu.mode.
    • Added the process.uptime metric.
    • Added the process.windows.handle.count metric (Windows only).
    • Added the process.unix.file_descriptor.count metric (Linux only).

  • Assemblies are now digitally signed using cosign.
    (#​4637)

  • Updated semantic conventions to
    v1.43.0
    and marked package as release candidate.
    (#​4675)

  See CHANGELOG for details.

1.16.0-beta.2

• NuGet: OpenTelemetry.Instrumentation.Hangfire v1.16.0-beta.2

  • Assemblies are now digitally signed using cosign.
    (#​4637)

  • Fixed NullReferenceException in the metrics filter when a job's definition
    cannot be resolved.
    (#​4731)

  See CHANGELOG for details.

1.16.0-beta.1

• NuGet: OpenTelemetry.Instrumentation.ServiceFabricRemoting v1.16.0-beta.1

  • Raised the minimum required version of Microsoft.ServiceFabric.Actors and
    Microsoft.ServiceFabric.Services.Remoting from 7.1.2448 to 8.4.268, as the
    7.1 Service Fabric runtime is going out of support.
    (#​4510)

  • Updated OpenTelemetry core component version(s) to 1.16.0.
    (#​4487)

  See CHANGELOG for details.

1.16.0-alpha.1

• NuGet: OpenTelemetry.Instrumentation.EventCounters v1.16.0-alpha.1

  • Fixed OnEventWritten processing events from EventSources that were not
    configured via AddEventSources.
    (#​4031)

  • Updated OpenTelemetry core component version(s) to 1.16.0.
    (#​4487)

  See CHANGELOG for details.

1.15.2

• NuGet: OpenTelemetry.Exporter.Geneva v1.15.2

  • Updated OpenTelemetry core component version(s) to 1.15.3.
    (#​4166)

  See CHANGELOG for details.

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