Bump the nuget group with 20 updates - #284
Open
dependabot[bot] wants to merge 1 commit into
Open
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps MailKit from 4.17.0 to 4.18.0 Bumps Marten from 9.32.1 to 9.37.0 Bumps Microsoft.AspNetCore.Authentication.JwtBearer from 10.0.11 to 10.0.12 Bumps Microsoft.AspNetCore.Mvc.Testing from 10.0.11 to 10.0.12 Bumps Microsoft.Extensions.Caching.Abstractions from 10.0.11 to 10.0.12 Bumps Microsoft.Extensions.Caching.Memory from 10.0.11 to 10.0.12 Bumps Microsoft.Extensions.Caching.StackExchangeRedis from 10.0.11 to 10.0.12 Bumps Microsoft.Extensions.Configuration from 10.0.11 to 10.0.12 Bumps Microsoft.Extensions.Configuration.Binder from 10.0.11 to 10.0.12 Bumps Microsoft.Extensions.DependencyInjection from 10.0.11 to 10.0.12 Bumps Microsoft.Extensions.DependencyInjection.Abstractions from 10.0.11 to 10.0.12 Bumps Microsoft.Extensions.Hosting.Abstractions from 10.0.11 to 10.0.12 Bumps Microsoft.Extensions.Http from 10.0.11 to 10.0.12 Bumps Microsoft.Extensions.Logging.Abstractions from 10.0.11 to 10.0.12 Bumps Microsoft.Extensions.TimeProvider.Testing from 10.9.0 to 10.10.0 Bumps Sentry.AspNetCore from 6.10.0 to 6.11.0 Bumps Sentry.OpenTelemetry.Exporter from 6.10.0 to 6.11.0 Bumps Supabase.Gotrue from 8.1.0 to 8.1.1 Bumps Supabase.Storage from 8.1.0 to 8.1.1 Bumps xunit.v3 from 4.0.0 to 4.0.1 --- updated-dependencies: - dependency-name: MailKit dependency-version: 4.18.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget - dependency-name: Marten dependency-version: 9.37.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget - dependency-name: Microsoft.AspNetCore.Authentication.JwtBearer dependency-version: 10.0.12 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: Microsoft.AspNetCore.Authentication.JwtBearer dependency-version: 10.0.12 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: Microsoft.AspNetCore.Mvc.Testing dependency-version: 10.0.12 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: Microsoft.AspNetCore.Mvc.Testing dependency-version: 10.0.12 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: Microsoft.Extensions.Caching.Abstractions dependency-version: 10.0.12 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: Microsoft.Extensions.Caching.Memory dependency-version: 10.0.12 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: Microsoft.Extensions.Caching.Memory dependency-version: 10.0.12 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: Microsoft.Extensions.Caching.StackExchangeRedis dependency-version: 10.0.12 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: Microsoft.Extensions.Configuration dependency-version: 10.0.12 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: Microsoft.Extensions.Configuration dependency-version: 10.0.12 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: Microsoft.Extensions.Configuration dependency-version: 10.0.12 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: Microsoft.Extensions.Configuration dependency-version: 10.0.12 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: Microsoft.Extensions.Configuration.Binder dependency-version: 10.0.12 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: Microsoft.Extensions.DependencyInjection dependency-version: 10.0.12 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: Microsoft.Extensions.DependencyInjection.Abstractions dependency-version: 10.0.12 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: Microsoft.Extensions.DependencyInjection dependency-version: 10.0.12 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: Microsoft.Extensions.DependencyInjection dependency-version: 10.0.12 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: Microsoft.Extensions.DependencyInjection dependency-version: 10.0.12 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: Microsoft.Extensions.Hosting.Abstractions dependency-version: 10.0.12 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: Microsoft.Extensions.Logging.Abstractions dependency-version: 10.0.12 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: Microsoft.Extensions.Http dependency-version: 10.0.12 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: Microsoft.Extensions.TimeProvider.Testing dependency-version: 10.10.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget - dependency-name: Sentry.AspNetCore dependency-version: 6.11.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget - dependency-name: Sentry.OpenTelemetry.Exporter dependency-version: 6.11.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget - dependency-name: Supabase.Gotrue dependency-version: 8.1.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: Supabase.Storage dependency-version: 8.1.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: xunit.v3 dependency-version: 4.0.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: xunit.v3 dependency-version: 4.0.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: xunit.v3 dependency-version: 4.0.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: xunit.v3 dependency-version: 4.0.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: xunit.v3 dependency-version: 4.0.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: xunit.v3 dependency-version: 4.0.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget ... Signed-off-by: dependabot[bot] <support@github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updated MailKit from 4.17.0 to 4.18.0.
Release notes
Sourced from MailKit's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Marten from 9.32.1 to 9.37.0.
Release notes
Sourced from Marten's releases.
9.37.0
Eighteen commits, and almost all of them are
Marten.PgVectorcorrectness — found by auditing the search surface 9.36.0 had just shipped. Every one of these was silent: a plausible answer, in a plausible order, that was wrong.Vector and hybrid search returned the wrong rows
Cosinerather than the metric the index declared, so anL2index was searched by cosine and silently fell back to a sequential scanhnsw.ef_search(default 40) — so it under-returned however large thelimitT, never the concrete subtypeto_tsvectorwhen no index matched theregConfigVectorProjectionwrote the wrong rowsid, so the later tenant's write replaced the earlier one'sForTenant(...)appends landed in the wrong tenantGuid.Emptyon string-identified streamsSearches now run through the session (#5421, #5423)
The session's connection, transaction, command timeout, resilience pipeline and
IMartenSessionLogger. A search on a session inside a caller-managed transaction now sees that session's uncommitted writes, the wayQuery<T>()does.SET LOCALstill cannot leak onto a pooled connection.VectorSearchAsync,VectorSearchWithScoresAsyncandVectorProjectionSearchAsyncgainCancellationTokenoverloads. Overloads rather than defaulted parameters: an optional argument is compiled into the caller, so widening a shipped signature breaks every assembly that has not been rebuilt.ColumnWeightsis refused, not ignored (#5446)HybridSearchOptionsgained per-column weights for the text leg (jasperfx#854, JasperFx 2.72.0). Marten weights at index time throughWeightedFullTextIndex, so there is nothing a per-call weight could apply to — and it is refused by name rather than ignored, because a caller who weights a title column and silently gets an unweighted ranking has no way to find out.Timestamps and the explorer
#5379 —⚠️ Only patching was affected — an ordinary
mt_last_modifiedno longer jumps by the server's UTC offset when a document is patched.now() at time zone 'utc'strips the offset, and the naive result is re-read in the session'sTimeZone: on a UTC+2 database the stored instant was two hours in the past.Store/SaveChangestakes the column default, which was always correct.#5430 (thanks @erikshafer) covers the event half of the same defect, reached through stream compaction, which #5445 fixed and left untested — and its assertions run over two time zones in both directions, where a one-sided bound passes against a negative offset.
#5383 — database-scoped explorer reads, honest store-global reads, and two tenant-scoping defects.
On JasperFx 2.72.0.
9.36.0
Takes
Marten.PgVectorfrom a vector search that could not be indexed and could not be called portably, to one that shares theJasperFx.Events.Vectorscontracts with Fisher and Polecat, can be served by an HNSW index, returns scores, and fuses with full text.VectorIndex— declare an HNSW index for a vector searchts_rankleg and the vector leg#5413 deleted that package's own
IEmbeddingProviderandDistanceFunctionin favour of the shared ones, and removed the deadVectorOn/PgVectorOptionsregistry, which had no references anywhere including the tests. ThePgvector.Vectoroverload ofVectorSearchAsyncwas kept and forwards, so the common call site is source-compatible.Minor rather than major because the whole package family shares one version and Marten itself has no break in this range — a major bump would move every other package for an extension package's API.
The search surface shipped here was audited immediately afterwards, and ten silent defects came out of it — searches that skipped Marten's default filters and returned soft-deleted rows, a distance metric that defaulted to
Cosinerather than the one the index declared, an indexed search capped at 40 rows byhnsw.ef_search, aVectorProjectionthat ignored conjoined tenancy, and more. Every one of them returned a plausible answer in a plausible order.All of them are fixed in 9.37.0. If you are picking up
Marten.PgVectorfor the first time, start there rather than here.On the tag. This points at
daeb27b5, not at the "Release 9.36.0" commitbaf1fc3f. The publish dispatch from the release commit was cancelled, and the run that actually pushed the packages went fromdaeb27b5— one commit later, carrying #5417. The tag names what shipped.9.35.0
Marten 9.35.0 — Event Model naming, store identity, and idempotent archiving.
Three, all deliberate. None require a code change to adopt, but each changes what an existing application observes.
1. A store's derived Event Model is now named after your service, not
"EventModel"(#5408).The store-derived Event Model source fell back to the literal
"EventModel"— the one default guaranteed to be wrong for every host. Wolverine names its derived model afterJasperFxOptions.ServiceName, and so does Bobcat's spec assembly, so the common case (Wolverine + one Marten store) assembled two models out of the box and had to restate a name it had already declared.The fallback is now the service name. An explicit name still wins:
If you were relying on the model being called
EventModel, setopts.EventModelName = "EventModel"explicitly.2. The primary store's
Subjectnow followsStoreName(#5409).Subjectwas a literalmarten://mainthat ignoredStoreOptions.StoreName, whileIdentityhad always been built from it — so naming a primary store moved one and left the other behind, andSubjectis the one consumers key on. Both are now built fromStoreName. Tooling that keys onstore.Subject(CritterWatch's explorer reads and shard progression ids among them) will seemarten://{storename}for a named store where it previously sawmarten://main.A store name is user-supplied text and a uri host is not, so names are sanitized:
My Storewould otherwise throwUriFormatExceptionanda/bwould silently parse its tail as a path. Ordinary names are unchanged.3. Archiving an already-archived stream is a no-op instead of an error (#5403).
Under
UseArchivedStreamPartitioning, a second archive of the same stream raised23505onmt_streams_archived_pkey. This also stalled async single-stream projections withIncludeArchivedEvents = truewhen they processed anArchivedmarker after an inline snapshot had already archived the stream. Repeated archiving now succeeds and does nothing.A genuine collision is still reported: a different active stream reusing an archived stream id still fails, rather than being silently swallowed and losing its metadata.
Fixes and improvements
StoreOptions.EventModelName. A host that calledAddEventModel("Something", …)assembled two models: its own, and one the store contributed under the default name. The name is configured onStoreOptionsand read lazily when the model is assembled, soAddEventModelmay be called before or afterAddMarten.BuildStoreOptionsassignedStoreNameboth before and after theIConfigureMarten<T>chain, so a contribution that named the store was silently reverted to the marker type's name.is_archivedis the list partition key on bothmt_streamsandmt_events, the archive function's new predicates also let PostgreSQL prune to the active partition, where the previous statements had to consider both.ImHashMapkeyed byFrame, which does not overrideGetHashCode, meant statement order followed identity hash codes and varied per process. Every Event Model slice also now carries the store it came from, so two stores projecting a document of the same simple name leave a recorded disagreement rather than one silently winning (jasperfx#836).Compatibility
Binary compatible with 9.34.0. The public
AddMarten/AddMartenStore<T>surface is unchanged — verified by diffing the extracted signature list against the 9.34.0 tag. New configuration is additive onStoreOptions.9.34.0
Native AOT support for event-sourced applications, and a round of integrity fixes to the diagnostics and monitoring surface — including one deliberate behaviour change worth reading before upgrading.
Native AOT
Event-sourced applications now run under Native AOT.
Utf8JsonWriterinstead of round-tripping through the consumer's serializer, removing a reflection-dependent path from AOT reads.Diagnostics and monitoring
Three fixes to the event store explorer and projection-status APIs. All three are cases where a monitoring read returned something misleading, or changed the system it was observing.
#5400 — Behaviour change. The four explorer read APIs no longer provision anything. They resolved their database through
ITenancy.FindOrCreateDatabase, and two tenancy models take the "or create" half literally:ShardedTenancyassigned an unknown tenant to a shard and ran partition + per-tenant sequence DDL for it, andSingleServerMultiTenancyissuedCREATE DATABASEfor a database named after the id. A console polling a retired or mistyped tenant id therefore brought that tenant — or a whole database — into existence.An unrecognized tenant id now throws
UnknownTenantIdException, which is whatStaticMultiTenancyandMasterTableTenancyalready did, so the explorer answers the same way across every tenancy model. Adds the publicITenancy.TryFindDatabase, a read-only counterpart toFindOrCreateDatabase; it is a default interface member, so customITenancyimplementations keep working unchanged.FindOrCreateDatabaseitself is untouched — create-on-demand remains its documented job for real tenant traffic.If you call
GetRecentStreamsAsync,ReadStreamAsync,QueryByTagsAsyncorGetProjectionStatusesAsyncwith a tenant id that may not exist, it now throws where it previously succeeded.#5382 —
GetProjectionStatusesAsync(ct)threwNotSupportedExceptionon a database-per-tenant store, because a tenant-less call has no default tenant to open a session against. It now answers from the projection registry, so "is this projection still registered?" — the only store-agnostic way to ask, and what orphan detection is built on — works on the store shape that most needs it.Note the original issue reported that both overloads threw. Only the tenant-less one did; passing a tenant id or a database identifier from
AllDatabases()has always worked and reads real per-database progression.#5396 —
ShardStatus.Statereports the state of a reachable daemon instead of always answeringUnknown.Unknownnow means what it is documented to mean: there is no daemon here to ask.Correctness
IVersionedmarker interface. Thanks to @JurJean for the report and the original fix.[JsonStringEnumMemberName]/[EnumMember]names are honored in LINQ translation rather than the CLR member name being assumed.byte[], and its limits are documented. Thanks to @erdtsieck.Event modeling
ProjectionEventModelSourceis registered fromAddMartenandAddMartenStore<T>, so Event Model views resolve from a Marten store without manual wiring.pgvector
Docs and internals
PrefixSearchand the session-level full-text search shortcuts.GuidOptimisticConcurrencyCompliancein the shared compliance suite.Dependencies
... (truncated)
9.33.0
The concurrency and portability release: a shared-state race that broke parallel
db-apply, a Native AOT query failure, and two cross-store divergences settled in Marten's favour and against it respectively.Dependencies move to JasperFx 2.67.0 and Weasel 9.31.1.
db-apply --parallelcould die with "Collection was modified" (#5364)Applying schema changes to many databases concurrently intermittently failed on one of them with:
Reported from a production deployment at 29 databases and
--parallel 16, where it hit exactly one database per run.One
ManagedListPartitionsinstance is shared by every database in a store. It mutated its partition dictionary in place and published it through aReadOnlyDictionary— which wraps rather than copies — soInitializeAsync'sClear()-and-refill ran while another database's worker was mid-enumeration. Fixed upstream in Weasel 9.31.1 (JasperFx/weasel#583) by publishing the registry as a snapshot swapped copy-on-write. Marten needs only the bump; there is no Marten code change.Two things worth knowing if you hit this before upgrading:
The same Weasel fix covers
Weasel.SqlServer'sManagedTenantPartitions, which had the identical shape.An enum compared to a captured variable failed under Native AOT (#5361)
where x.Status == capturedthrewBadLinqExpressionExceptionwrappingPlatformNotSupportedException: Dynamic code generation is not supported on this platform, while the same comparison against a literal worked. C# lowers enum equality to a comparison of the underlying integers, so the value side always arrives asConvert(closure.captured, Int32)— a shape 9.32.1's reflective walk did not cover, which sent it to FastExpressionCompiler and therefore toReflection.Emit.Two changes, because the enum shape was the symptom rather than the cause. The reflective walk now handles conversions between an enum and anything sharing its integral representation, including the
Nullable<T>forms — widening and narrowing are still left alone, so no value is ever reinterpreted. AndReduceToConstantno longer requires the ability to emit at all: where the platform cannot, shapes the walk declines fall back to the BCL expression interpreter instead of throwing. Without that second half, every expression shape Marten has not explicitly been taught was a latent AOT failure.EventQuery.TagValuesis now honored (#5365)The lossy name/value tag filter, on the composable query object. Previously you filtered by tags or by everything else: the dictionary form existed only on the non-composable
QueryByTagsAsync, which is unpaged and has noTotalCount. Now a caller holding a tag name can AND it with the event type, window, stream, metadata and tenant filters and keep paging and a truthful total.Note the semantics, which differ from the rich
TagConditionsform deliberately: entries AND (an event must carry every named tag at the given value), whereTagConditionsconditions OR. Supplying both spellings on one query is refused rather than resolved by a silent precedence rule.Behaviour change: dictionary tag queries accept either spelling, case-insensitively
Fixing the above exposed a divergence in the existing
IEventStore.QueryByTagsAsync(IReadOnlyDictionary<string,string>, …)overload. It matched a tag name against the CLR type name only and compared the value case-sensitively, while Polecat accepted either spelling and compared case-insensitively — so the same dictionary answered differently depending on which store you asked, and guessing wrong was anArgumentExceptionat runtime.Both that overload and the new
TagValuespath now resolve names through the shared matcher (CLR simple name or registered table suffix, case-insensitively) and compare values against the string form of the stored tag value, ordinal case-insensitively. Postgres renders a Guid lowercase through::textwhile SQL Server renders it uppercase, so an operator's copy-pasted id no longer depends on which store answered.If you relied on a tag name or value being matched case-sensitively, this query now matches more rows than it used to. An unregistered tag name is still an
ArgumentExceptionlisting what is registered, never an empty answer.CompactStreamAsync<T>infers the fold for an unregistered aggregate (#5366)Compaction refused any type without a registered aggregation projection, while Fisher and Polecat both inferred one. That made a compaction policy able to target only an aggregate the application already snapshots — a real constraint on the feature, invisible until runtime, and one nobody would infer from the API.
CompactStreamAsync<T>now builds the aggregator fromT's ownCreate/Applyconventions when no projection is registered, which is what every other aggregation path in Marten already did. The typed overload namesToutright, and that is the same declaration of intent a registration would be.... (truncated)
Commits viewable in compare view.
Updated Microsoft.AspNetCore.Authentication.JwtBearer from 10.0.11 to 10.0.12.
Release notes
Sourced from Microsoft.AspNetCore.Authentication.JwtBearer's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.AspNetCore.Mvc.Testing from 10.0.11 to 10.0.12.
Release notes
Sourced from Microsoft.AspNetCore.Mvc.Testing's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.Extensions.Caching.Abstractions from 10.0.11 to 10.0.12.
Release notes
Sourced from Microsoft.Extensions.Caching.Abstractions's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.Extensions.Caching.Memory from 10.0.11 to 10.0.12.
Release notes
Sourced from Microsoft.Extensions.Caching.Memory's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.Extensions.Caching.StackExchangeRedis from 10.0.11 to 10.0.12.
Release notes
Sourced from Microsoft.Extensions.Caching.StackExchangeRedis's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.Extensions.Configuration from 10.0.11 to 10.0.12.
Release notes
Sourced from Microsoft.Extensions.Configuration's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.Extensions.Configuration.Binder from 10.0.11 to 10.0.12.
Release notes
Sourced from Microsoft.Extensions.Configuration.Binder's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.Extensions.DependencyInjection from 10.0.11 to 10.0.12.
Release notes
Sourced from Microsoft.Extensions.DependencyInjection's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.Extensions.DependencyInjection.Abstractions from 10.0.11 to 10.0.12.
Release notes
Sourced from Microsoft.Extensions.DependencyInjection.Abstractions's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.Extensions.Hosting.Abstractions from 10.0.11 to 10.0.12.
Release notes
Sourced from Microsoft.Extensions.Hosting.Abstractions's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.Extensions.Http from 10.0.11 to 10.0.12.
Release notes
Sourced from Microsoft.Extensions.Http's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.Extensions.Logging.Abstractions from 10.0.11 to 10.0.12.
Release notes
Sourced from Microsoft.Extensions.Logging.Abstractions's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.Extensions.TimeProvider.Testing from 10.9.0 to 10.10.0.
Release notes
Sourced from Microsoft.Extensions.TimeProvider.Testing's releases.
10.10.0
This month's release focuses on AI package reliability: closing gaps in evaluation scoring, hardening OpenAI image-option handling, and removing the deprecated OpenAI Assistants API support.
Experimental API Changes
Removed Experimental APIs
OPENAI001) #7724What's Changed
AI
AI Evaluation
Repository Infrastructure Updates
Acknowledgements
Full Changelog: dotnet/extensions@v10.9.0...v10.10.0
Commits viewable in compare view.
Updated Sentry.AspNetCore from 6.10.0 to 6.11.0.
Release notes
Sourced from Sentry.AspNetCore's releases.
6.11.0
Features ✨
Fixes 🐛
Dependencies ⬆️
Deps
Commits viewable in compare view.
Updated Sentry.OpenTelemetry.Exporter from 6.10.0 to 6.11.0.
Release notes
Sourced from Sentry.OpenTelemetry.Exporter's releases.
6.11.0
Features ✨
Fixes 🐛
Dependencies ⬆️
Deps
Commits viewable in compare view.
Updated Supabase.Gotrue from 8.1.0 to 8.1.1.
Release notes
Sourced from Supabase.Gotrue's releases.
8.1.1
8.1.1 (2026-09-14)
Bug Fixes
Commits viewable in compare view.
Updated Supabase.Storage from 8.1.0 to 8.1.1.
Release notes
Sourced from Supabase.Storage's releases.
8.1.1
8.1.1 (2026-09-14)
Bug Fixes
Commits viewable in compare view.
Updated xunit.v3 from 4.0.0 to 4.0.1.
Release notes
Sourced from xunit.v3's releases.
No release notes found for this version range.
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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill 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 versionwill 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