Repository navigation
Bump Cronos and 17 others - #1310
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps Cronos from 0.11.1 to 0.13.0 Bumps JasperFx from 2.90.2 to 2.101.0 Bumps MailKit from 4.18.1 to 4.18.2 Bumps Markdig from 1.4.1 to 1.6.0 Bumps Marten from 9.50.3 to 9.58.0 Bumps Microsoft.AspNetCore.SignalR.Client from 10.0.13 to 10.0.14 Bumps Microsoft.AspNetCore.TestHost from 10.0.13 to 10.0.14 Bumps Microsoft.Extensions.DependencyModel from 10.0.13 to 10.0.14 Bumps Microsoft.Extensions.TimeProvider.Testing from 10.9.0 to 10.11.0 Bumps Microsoft.Testing.Extensions.TrxReport from 2.5.1 to 2.5.2 Bumps OpenTelemetry.Exporter.OpenTelemetryProtocol from 1.20.0 to 1.20.1 Bumps OpenTelemetry.Extensions.Hosting from 1.20.0 to 1.20.1 Bumps OpenTelemetry.Instrumentation.AspNetCore from 1.20.0 to 1.20.2 Bumps OpenTelemetry.Instrumentation.Http from 1.20.0 to 1.20.2 Bumps SkiaSharp from 4.153.1 to 4.155.0 Bumps SkiaSharp.NativeAssets.Linux.NoDependencies from 4.153.1 to 4.155.0 Bumps WolverineFx.Marten from 6.51.1 to 6.63.0 Bumps WolverineFx.RuntimeCompilation from 6.51.1 to 6.63.0 --- updated-dependencies: - dependency-name: Cronos dependency-version: 0.13.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dotnet - dependency-name: JasperFx dependency-version: 2.101.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dotnet - dependency-name: MailKit dependency-version: 4.18.2 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dotnet - dependency-name: Markdig dependency-version: 1.6.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dotnet - dependency-name: Marten dependency-version: 9.58.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dotnet - dependency-name: Microsoft.AspNetCore.SignalR.Client dependency-version: 10.0.14 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dotnet - dependency-name: Microsoft.AspNetCore.TestHost dependency-version: 10.0.14 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dotnet - dependency-name: Microsoft.Extensions.DependencyModel dependency-version: 10.0.14 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dotnet - dependency-name: Microsoft.Extensions.TimeProvider.Testing dependency-version: 10.11.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dotnet - dependency-name: Microsoft.Testing.Extensions.TrxReport dependency-version: 2.5.2 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dotnet - dependency-name: OpenTelemetry.Exporter.OpenTelemetryProtocol dependency-version: 1.20.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dotnet - dependency-name: OpenTelemetry.Extensions.Hosting dependency-version: 1.20.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dotnet - dependency-name: OpenTelemetry.Instrumentation.AspNetCore dependency-version: 1.20.2 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dotnet - dependency-name: OpenTelemetry.Instrumentation.Http dependency-version: 1.20.2 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dotnet - dependency-name: SkiaSharp dependency-version: 4.155.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dotnet - dependency-name: SkiaSharp.NativeAssets.Linux.NoDependencies dependency-version: 4.155.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dotnet - dependency-name: WolverineFx.Marten dependency-version: 6.63.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dotnet - dependency-name: WolverineFx.RuntimeCompilation dependency-version: 6.63.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dotnet ... Signed-off-by: dependabot[bot] <support@github.com>
Contributor
Author
|
Looks like these dependencies are updatable in another way, so this is no longer needed. |
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.
Pinned Cronos at 0.13.0.
Release notes
Sourced from Cronos's releases.
0.13.0
Release Notes
0.12.0
Release Notes
Hcharacter (#89 by @epicoxymoron).netcoreapp3.1platform withnet8.0in tests.Commits viewable in compare view.
Updated JasperFx from 2.90.2 to 2.102.0.
Release notes
Sourced from JasperFx's releases.
2.102.0
JasperFx 2.102.0 is a minor release with one new
IEventDatabasecapability. It lets monitoring report projection lag as time rather than as a count of events.IEventDatabase.FetchFirstEventTimestampsAfterAsync, the age of the oldest unprocessed event (#1150 / #1151).(TenantId, Sequence)position, it returns the store's timestamp of the first event with a higher sequence, ornullwhen there is none (the shard is caught up). You get onePendingEventAge(TenantId, Sequence, Timestamp)per position, in the order asked.PendingEventAgealso hasIsCaughtUpandAgeAt(now), which never returns a negative age when clocks are skewed.NotSupportedExceptionon a store that hasn't implemented it. Anulltimestamp means "caught up", so that default can't answer without reporting a lagging shard as current. The single-position convenienceFetchFirstEventTimestampAfterAsync(sequence, tenantId)calls the batched member by default. The in-memory prototyping store implements both.PendingEventAgeCompliancesuite, gated bySupportsPendingEventAges(default false), with 12 facts. They cover the "strictly after" rule, ordering and duplicates, archived events and conjoined tenant scoping. A newSupportsStreamArchivingfixture flag (default true) gates the archived facts. Stores must enroll the new suite (or excuse it) orComplianceSuiteInventory.AssertEnrolledfails.Marten, Polecat and Fisher implement the method in their JasperFx 2.102.0 upgrades.
What's Changed
Full Changelog: JasperFx/jasperfx@v2.101.1...v2.102.0
2.101.1
JasperFx 2.101.1 is a patch release with one fix.
StopAsync/PauseAsynccalls on the projection coordinator no longer throwObjectDisposedException(#1148 / #1149).ProjectionCoordinatorBaseread, awaited across, then disposed and replaced its shared cancellation source and runner with nothing serializing callers. Two stops in flight at once could cancel a source the other had just disposed. Two starts in flight at once could each build a leadership loop, leaving one running that nothing would ever cancel.RunCommandstops the host again whenApplicationStoppingfires, so tests hosting an app throughWebApplicationFactoryor Alba had twoIHost.StopAsynccalls racing at teardown.ProjectionCoordinatorpick this up from the base class. Marten'sExplicitProjectionCoordinatorhas its own fix in JasperFx/marten#5843.StressTestsproject that runs its tests one at a time, so they can't starve timing-sensitive tests of thread-pool threads.What's Changed
Full Changelog: JasperFx/jasperfx@v2.101.0...v2.101.1
2.101.0
JasperFx 2.101.0 makes the command line work from a Native AOT binary, adds a build warning for a source generator that never reaches the compiler, and fixes assembly scanning on Windows.
Highlights
help,run,describeand every other command failed from a native binary, because commands were found and built through reflection that trimming removes.JasperFx.SourceGeneratorregisters each command, a factory for it and its input, and an[InjectService]injector, as ordinary code the trimmer keeps. JasperFx and JasperFx.Events now ship built with it, anddescribeno longer throws when referenced-assembly metadata is missing.JasperFx.SourceGeneratorin every assembly that contributes commands. The trimming warnings onApplyJasperFxExtensions/RunJasperFxCommandsnow say when it is safe to suppress them.aot-cliCI job publishes aCreateSlimBuilderapp with Native AOT and runshelp,help <command>, an application command,check-env,describeandrunfrom the binary.JFXEVT1138: a build warning when the events source generator never reaches the compiler (#1138 / #1139).JasperFx.Events.SourceGeneratoris pinned to a different version than the copy bundled by a store, the SDK keeps the higher copy, and a project target then removes that one.JasperFxEventsReportLostSourceGenerator=false.runtimes/nativefolders on Windows too, and skips satellite resource assemblies (#1143 / #1145)."/runtimes"with a forward slash, so on Windows every native DLL, such as the coverage collector'scovrun64.dll, was tried twice and failed on each host start.What's Changed
Full Changelog: JasperFx/jasperfx@v2.100.1...v2.101.0
2.100.1
JasperFx 2.100.1 is a patch release with one fix.
CatchUpAsyncno longer returns cleanly while a shard has faulted (#1134 / #1135). The tracker delivers a failed shard's state to listeners asynchronously, so the daemon'sRecordercould still be empty whenCatchUpAsyncchecked it, and it reported success though a projection had thrown. That was the cause of flaky daemon tests in Marten (marten#5696) and Polecat (polecat#933).ForceAllMartenDaemonActivityToCatchUpAsyncand its Polecat and Fisher equivalents now fail when a projection throws.What's Changed
Full Changelog: JasperFx/jasperfx@v2.100.0...v2.100.1
2.100.0
JasperFx 2.100.0 is mostly about running many tenants in one process: per-tenant projection work can be queued and bounded, and store-wide rebuilds fan out per tenant.
Highlights
DaemonSettings.SerializeTenantProjectionBatches, #1127).GenerationRules.ReuseCompiledAssemblies, #1114 / #1129), andAssemblyGenerator's reference cache is keyed on path plus last-write time (#1110 / #1126).ComplianceSuiteInventory, so a store can't leave a suite out silently (#1123).StartsStream/Against, a secondStartsStream<T>()throws instead of silently replacing the first, and a derived snapshot view is placed in its aggregate's chapter. The projection stepper also assigns the document's identity.What's Changed
Full Changelog: JasperFx/jasperfx@v2.99.0...v2.100.0
2.99.0
What's Changed
Full Changelog: JasperFx/jasperfx@V2.98.0...v2.99.0
2.98.0
JasperFx 2.98.0 covers everything since 2.97.0. 2.97.1 was tagged in the source but never reached NuGet, so its fixes ship here.
Behaviour changes
Side effects keep their correlation id (#1101, #1105). With event metadata on, a message published with
slice.PublishMessage(message)now carries the correlation id that all of the slice's appended events agree on, on the async path and both inline paths. It used to get the daemon page's id, which merged unrelated flows that landed in one page, or a fresh id inline. This changes the envelope's correlation id for existing side effects. Where the events don't agree, or event metadata is off, nothing changes. Causation is deliberately left out, so a side effect's handler still names that side effect as the cause of what it appends.An HTTP endpoint and a message handler fold cleanly (#1099, #1103). Two derived sources claiming
HttpandMessageHandleron one slice no longer raise threeSourceDisagreementhotspots.TriggerKind,HandlerType,HandlerMethodandOriginkeep the HTTP side in either source order. Other real disagreements still raise their hotspots.Cloned events keep their correlation and causation ids (#1107). Fan-out and
ReplaceEventused to drop them.New
SubscriptionDescriptor.PublishedTypessays what a projection writes, including event projections and composites, whereAggregateTypeis null. Empty doesn't mean "writes nothing": a flat table projection has rows with no type.IPublishesTypesis the new non-generic interface behind it (#1102, #1106).MessageMetadata.From(IEvent)attributes a side effect to one event when a slice spans several flows (#1105).EventModelSliceDescriptor.AdditionalEntryPointsandEventModelEntryPointkeep the message handler beside the endpoint on a folded slice. Every slice's JSON now carriesadditionalEntryPoints: [], and older payloads read as empty (#1103).Fixes
IsValidNumberno longer accepts text that isn't a number, andReadExpectedBufferAsyncfails on a short read (#1098).TryCreateUsagelists its projections (#1106).For event store authors
EventProjectionRegistrationCompliancefacts need no store changes. They pass on Marten, Polecat and Fisher.2.97.0
What's Changed
Full Changelog: JasperFx/jasperfx@V2.96.2...v2.97.0
2.96.2
Fixes
RunCommandnow awaits host shutdown instead of blocking a thread-pool thread withManualResetEventSlim.Wait(). That block could starve the thread pool on single-core machines (#1092, #1093)All JasperFx packages that share
JasperFxVersionare 2.96.2. JasperFx.RuntimeCompiler stays at 5.0.1.2.96.1
What's Changed
New Contributors
Full Changelog: JasperFx/jasperfx@V2.96.0...v2.96.1
2.96.0
Event Modeling
Originno longer raises aSourceDisagreement: an observed origin names the service the slice was watched on, not a store, so runtime observation confirms the slice. Two observed services or two derived stores still disagree (#1083, #1085).@jasperfx/event-model-vue 0.16.0
SourceDisagreementrenders as a muted "≠" badge on the disputed card (or the slice header for roles with no card) instead of a red sticky; findings keep their stickies.disagreementPresentation="sticky"restores the old rendering, andplaceDisagreements/disagreementLinesare exported for host legends and selection detail (#1084, #1085).2.95.1
Full Changelog: JasperFx/jasperfx@V2.95.0...V2.95.1
2.95.0
Full Changelog: JasperFx/jasperfx@V2.94.0...V2.95.0
2.94.0
All three are binary-compatible additions; default implementations throw NotSupportedException naming a store built against an older JasperFx. PR #1074.
2.93.0
Highlights
SubscribeFromSequence/SubscribeFromTimefloor and seeds the progression row first (it used to replay from 0). There is also a new persisted per-database floor seam onIEventDatabase(FetchProjectionFloorAsync/TrySetProjectionFloorAsync/SetProjectionFloorAsync) and a newAsyncOptions.SubscribeFromFirstRun()strategy. Store implementations: JasperFx/marten#5740, JasperFx/polecat#813, JasperFx/fisher#471.IDocumentStoreDiagnosticsWriter.UndeleteDocumentAsync(#1059, #1062) andDocumentQueryOptions.OrderByMetadata(#1058, #1063).SkipApplyErrors, a non-transientDbExceptionraised from projection code is no longer dead-lettered event by event. It pauses the shard withShardFailure.IsTransient = false.--key=valuesplits at the first=only, so connection strings passed byWebApplicationFactoryno longer produce "Invalid usage" output (#1057, #1060).Compliance suites
SoftDeleteCompliance,DocumentMetadataCompliance(#785, #1067) andProjectionFloorCompliance(#1068). New undelete and metadata-ordering facts inDocumentStoreDiagnosticsCompliance. Everything new is gated off by default.SingleTenantedEventSlicingComplianceis[Obsolete]and will be removed in 3.0 (#727, #1066, #1065).Other
PublishAotgate proving the AOT roots companion end to end, with a negative control (#777, #1069).Compatibility
No public members were removed or changed. Every member added to an existing interface has a default implementation (verified against 2.92.0 with a public-API diff and the contract ratchet), so stores built against 2.92 keep loading.
2.92.0
IEventStore.PreviewHighWaterAdvanceAsyncandIEventStore.AdvanceHighWaterMarkToLatestAsync. They preview and advance a database's high water mark (or one tenant's under per-tenant event partitioning) to the highest committed sequence, with anexpectedCurrentMarkcompare-and-set. Both are default members that throwNotSupportedExceptionuntil a store implements them.ProjectionHost.AdvanceHighWaterMarkToLatestAsyncno longer throwsNotImplementedException.2.91.0
What's Changed
Full Changelog: JasperFx/jasperfx@v2.90.2...v2.91.0
Commits viewable in compare view.
Updated MailKit from 4.18.1 to 4.18.2.
Release notes
Sourced from MailKit's releases.
No release notes found for this version range.
Commits viewable in compare view.
Pinned Markdig at 1.6.0.
Release notes
Sourced from Markdig's releases.
1.6.0
Changes
✨ New Features
🐛 Bug Fixes
Full Changelog: 1.5.1...1.6.0
Published with dotnet-releaser
1.5.1
Changes
🚨 Breaking Changes
🐛 Bug Fixes
Full Changelog: 1.5.0...1.5.1
Published with dotnet-releaser
1.5.0
Changes
🐛 Bug Fixes
Full Changelog: 1.4.2...1.5.0
Published with dotnet-releaser
1.4.2
Changes
✨ New Features
🐛 Bug Fixes
Full Changelog: 1.4.1...1.4.2
Published with dotnet-releaser
Commits viewable in compare view.
Updated Marten from 9.50.3 to 9.59.0.
Release notes
Sourced from Marten's releases.
9.59.0
Marten 9.59.0 moves to JasperFx 2.102.0 and Weasel 9.50.0. It adds read-only DCB tag queries on a query session, reports how old a projection's oldest unprocessed event is, and fixes a shutdown race in the explicit projection coordinator.
Highlights
EventsExistAsync,QueryByTagsAsyncandAggregateByTagsAsyncare now onIQuerySession.Events, so a read-only endpoint no longer needs a document session to read by tags (thanks to new contributor @alekbarszczewski, #5841).FetchForWritingByTagsstill needs a document session. Existing calls throughIDocumentSession.Eventsare unchanged, both in source and in compiled assemblies. A class that implementsMarten.Events.IQueryEventStoreitself has three more members to implement.IEventDatabase.FetchFirstEventTimestampsAfterAsync. It returns the timestamp of the oldest event a shard hasn't processed yet, in one round trip. CritterWatch uses it to report projection lag as time instead of a count of events (#5844).StopAsync/PauseAsynccalls, such as the second stop JasperFx'sRunCommandissues whenWebApplicationFactoryor Alba stops the host, no longer stop and dispose the same daemons twice or log "Error while trying to stop daemon agents". A start that overlaps a stop no longer starts a disposed daemon, and a daemon resolved during a stop is no longer dropped without being disposed (#5842, #5843).db-*commands (db-apply,db-assert,db-patch,db-dump,db-list) now appear and run there too. JIT applications see no change (#5840, #5845).AutoCreate, apply at startup,db-apply/resources setupas a deployment step, ordb-patchscripts for a DBA, with links to the Weasel CLI and JasperFx stateful resource docs (#5839).What's Changed
New Contributors
Full Changelog: JasperFx/marten@v9.58.0...V9.59.0
9.58.0
Marten 9.58.0 moves to JasperFx 2.100.0 and Weasel 9.49.0, and makes per-tenant composite rebuilds work on per-tenant partitioned stores.
Highlights
pk_mt_event_progression(#5829, #5833).FetchForExclusiveWritingin a batch throwsStreamLockedExceptionon a locked stream (thanks to new contributor @esond).LogFactoryis set when a customIMartenLoggeris configured.What's Changed
New Contributors
Full Changelog: JasperFx/marten@V9.57.0...v9.58.0
9.57.0
Highlights
ShouldDeleteorDeleteEvent<T>, used to lose its whole history to an empty snapshot. Compaction now leaves it alone and logs an information line. (#5797)IncludeStreamandIncludeEventsused to leave those rows in plain text and report success. (#5797)opts.Events.AutoDiscoverTagTypesturns off automatic DCB tag type registration, for stores that use strong-typed identifiers but not DCB. It's on by default, and explicitRegisterTagType<T>()calls work either way. Thanks to @gschuager for the report and the design. (#5806)EventStoreUsagereports the event store'sTenancyStyle, so a console can tell conjoined events from conjoined documents. (#5805)Action needed after upgrading
If you rely on masking for archived or skipped events: run the same
ApplyEventDataMaskingcall again. Data that was archived or skipped when you last ran it is still in plain text until you do.That call runs your rules again over everything the first pass reached. If a rule isn't safe to run twice, such as one that draws a new pseudonym, add
x.IsArchivedto anIncludeEventsfilter that still names the same subject:Never use
x.IsArchivedas the whole filter, because that masks every archived event in the store.If you compact streams: the deleted events can't be rebuilt from Marten. To find affected streams, replace
<schema>and run this, then restore those streams from a backup or from wherever an archiver copied them:An archiver closed over
IDocumentSessionwas never called for past compactions, so that copy won't exist.Behaviour changes
IncludeEventsnow includes archived events. A masking filter that needs only live events should add!x.IsArchived.IDocumentOperationsorIDocumentSessionnow throwsInvalidOperationExceptionbefore anything is queued. It used to be skipped silently, with the events deleted anyway. An archiver closed overIDocumentSessionis now called.ToParameterTypenow throws for an unmapped type where it used to return a character catch-all. An enum resolves through its underlying type, so along-backed enum givesBigint. Marten's own call sites are not affected.What's Changed
Full Changelog: JasperFx/marten@v9.56.0...V9.57.0
... (truncated)
9.56.0
What's Changed
Full Changelog: JasperFx/marten@V9.55.0...v9.56.0
9.55.0
Read before upgrading
Apps running under a Turkish or Azerbaijani culture (
tr-TR,az-AZ) with document types whose names contain an uppercaseI. Document aliases (#5778),DdlTemplatelookups and flat-table upsert function names (#5783) are now lowered with the invariant culture. Before this release, those cultures turnedIinto a dotlessı, so a document typeInvoicewas stored inmt_doc_ınvoice. From 9.55.0 it maps tomt_doc_invoice, and Marten will create that table empty. Rename the existing tables (and their upsert functions) to the invariant name before upgrading, or the existing documents will appear to be missing. Apps on any other culture are unaffected: the names they generate are unchanged.Behaviour change:
StoredDocument.Versionfor projection documents (#5773). For a mapping that usesUseVersionFromMatchingStreamwith revisions, the diagnostics version token is now<mt_version>:<mt_last_modified as epoch microseconds>(or an md5 of the document body when last-modified tracking is disabled). It used to bemt_versionalone, which did not change when the daemon rewrote the document at the same stream version. Anything that parsed the token as an integer must be updated. Undeleting a projection document through the diagnostics writer also no longer bumpsmt_versionpast the stream's version.Fixes worth calling out
x.Inner.Value, instead of falling back to the JSONB path.TrackConnections = TrackLevel.Verbose, amarten.append.eventactivity event is now emitted on every append route, including the Quick routes that are the V9 default. Expect more events per append than before.DatabaseSchemaNamethat is a reserved word or contains uppercase. Before, every schema apply after the first failed with42P07(weasel#750, contributed by @marc-RocketRez).StreamPagedByCursorwrites each page's bytes directly and disposes its pooled stream (#5776, @chrisbbe).What's Changed
New Contributors
Full Changelog: JasperFx/marten@v9.54.2...V9.55.0
9.54.2
What's Changed
New Contributors
Full Changelog: JasperFx/marten@V9.54.1...v9.54.2
9.54.1
Full Changelog: JasperFx/marten@V9.54.0...V9.54.1
9.54.0
Full Changelog: JasperFx/marten@v9.53.0...V9.54.0
9.53.0
9.53.0 is a minor release. It picks up JasperFx 2.94.0 and implements the three members that release adds, for CritterWatch's Document Store Explorer and Event Store Explorer (#5756).
New
IReadOnlyEventStore.QueryEventData<T>(tenantId)(jasperfx#1073): store-agnostic LINQ over the bodies of one event type, across every stream. It runs through the sharedDocumentQueryableExtensionsterminators (ToListAsync,CountAsync,AnyAsync,FirstOrDefaultAsync).QueryRawEventDataOnly<T>()under the shared name. Events in archived streams are excluded, as they are there.BadLinqExpressionExceptionnaming it.QueryStreamStates:NotSupportedException;IDocumentStoreDiagnosticsWriter.PreviewDocumentJsonAsync(jasperfx#1071): a dry run ofSaveDocumentJsonAsync.ExpectedVersion.DocumentTypeRef.IsSoftDeleted(jasperfx#1070):IDocumentStoreDiagnostics.DocumentTypesAsyncreports whether each type usesDeleteStyle.SoftDelete. A sub-class reports its root mapping's delete style.Compliance
EventDataQueryComplianceis newly enrolled.ReportsDocumentDeleteStyleandSupportsDocumentWritePreviewgates are on.Dependencies
9.52.0
Highlights and behaviour changes
Built on JasperFx 2.93.1.
mt_event_projection_floors. Every event store gets this table as a schema migration on its nextapply (#5740). It holds the persisted projection start floors behind the new
AsyncOptions.SubscribeFromFirstRun().A database whose schema has not been migrated yet keeps starting its projections exactly as before. Floors survive
DeleteAllDocumentsAsync,DeleteAllEventDataAsyncandResetAllData, and they are removed along with a tenant.StoreOptions.Advanced.ExceptionTransforms(#5682). Register your own exception transforms, consultedbefore Marten's built-in ones, to turn a
PostgresExceptionwith your own SQLSTATE into a typed exception.UndeleteDocumentAsync), and ordera document page by last modified, numeric revision or created time ("newest first").
shard reports
ShardFailureCategory.ApplyEventand names the event, where it used to reportOtherwith no event.It is still not dead-lettered, and it was never retried before either.
IEventStore.PreviewHighWaterAdvanceAsync/AdvanceHighWaterMarkToLatestAsync(#5738): preview, thenadvance, the high-water mark to the latest event, the store-agnostic operation CritterWatch calls.
UseTenantPartitionedEventsno longer fails with23503, whether the store has DCB tagrows (#5720) or a
[NaturalKey]aggregate (#5742);intpastint.MaxValue, soILongVersionedworks as #4526 advised (#5723);
UndoDeleteWhere/HardDeleteWhereno longer cause a falseConcurrencyExceptionon a numeric-revision writelater in the same session (#5743).
Aspire.AppHost.Sdk13.6.3 with a PostgreSQL resource. The NuGet publish workflow nolonger installs the obsolete aspire workload (#5724).
What's Changed
Full Changelog: JasperFx/marten@v9.51.0...v9.52.0
9.51.0
What's Changed
Full Changelog: JasperFx/marten@V9.50.3...v9.51.0
Commits viewable in compare view.
Updated Microsoft.AspNetCore.SignalR.Client from 10.0.13 to 10.0.15.
Release notes
Sourced from Microsoft.AspNetCore.SignalR.Client's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.AspNetCore.TestHost from 10.0.13 to 10.0.15.
Release notes
Sourced from Microsoft.AspNetCore.TestHost's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.Extensions.DependencyModel from 10.0.13 to 10.0.15.
Release notes
Sourced from Microsoft.Extensions.DependencyModel'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.11.0.
Release notes
Sourced from Microsoft.Extensions.TimeProvider.Testing's releases.
10.11.0
.NET Extensions 10.11.0
This release adds optional scope capture for buffered logs and updates experimental HTTP latency enrichment APIs. It also includes fixes for AI streaming and function invocation, evaluation reports, HybridCache invalidation, and logging.
Experimental API Changes
New Experimental APIs
GlobalLogBufferingOptions.IncludeScopesandPerRequestLogBufferingOptions.IncludeScopes(EXTEXP0003) #7813Breaking Changes to Experimental APIs
AddHttpLatencyTelemetryis renamed toAddHttpServerLatencyTelemetryand moves fromHttpLatencyTelemetryServiceCollectionExtensionstoHttpLoggingServiceCollectionExtensions. It remains experimental underEXTEXP0013in this release. #7730What's Changed
AI
AI Evaluation
Telemetry and Observability
ASP.NET Core Extensions
AI Project Templates
Caching
... (truncated)
10.10.1
This release fixes two OpenAI integration issues: a TypeLoadException on tool-carrying Responses API calls and a streaming crash against third-party OpenAI-compatible endpoints, by upgrading the OpenAI SDK to 2.14.0.
Packages in this release
10.10.110.10.1What's Changed
AI
Acknowledgements
Full Changelog: dotnet/extensions@v10.10.0...v10.10.1
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 Microsoft.Testing.Extensions.TrxReport from 2.5.1 to 2.5.3.
Release notes
Sourced from Microsoft.Testing.Extensions.TrxReport's releases.
No release notes found for this version range.
Commits viewable in compare view.
Pinned OpenTelemetry.Exporter.OpenTelemetryProtocol at 1.21.0.
Release notes
Sourced from OpenTelemetry.Exporter.OpenTelemetryProtocol's releases.
1.21.0
For highlights and announcements pertaining to this release see: Release Notes > 1.21.0.
The following changes are from the previous release 1.21.0-rc.2.
NuGet: OpenTelemetry v1.21.0
OpenTelemetryLoggerOptionsis now bound from theLogging:OpenTelemetryconfiguration section using the configuration binding source generator instead
of reflection, making it fully trim and Native AOT compatible. An empty value
for a boolean option is now ignored on all target frameworks rather than
throwing on some, depending on the version of
Microsoft.Extensions.Configuration.Binderin use.(#8100)
Fixed the self-diagnostics environment snapshot leaving a dangling comma in a
redacted
OTEL_RESOURCE_ATTRIBUTESvalue when it contained empty entries.(#8104)
See CHANGELOG for details.
NuGet: OpenTelemetry.Api v1.21.0
System.Diagnostics.DiagnosticSourcedependency to11.0.0for all target frameworks.
(#8066)
See CHANGELOG for details.
NuGet: OpenTelemetry.Api.ProviderBuilderExtensions v1.21.0
No notable changes.
See CHANGELOG for details.
NuGet: OpenTelemetry.Exporter.Console v1.21.0
No notable changes.
See CHANGELOG for details.
NuGet: OpenTelemetry.Exporter.InMemory v1.21.0
No notable changes.
See CHANGELOG for details.
NuGet: OpenTelemetry.Exporter.OpenTelemetryProtocol v1.21.0
... (truncated)
1.21.0-rc.2
The following changes are from the previous release 1.21.0-rc.1.
NuGet: OpenTelemetry v1.21.0-rc.2
Fixed an exception when downscaling empty exponential histogram buckets after
a reset.
(#8064)
Fixed tracing callbacks continuing after provider shutdown or disposal on older
target frameworks.
(#8065)
Fixed initialization failures when environment variable access is denied.
Configuration reloads retain the last successful values when access is denied.
(#8070)
Fixed a source, meter or legacy activity name with a trailing line feed
matching a wildcard pattern which does not end in a wildcard.
(#8074)
Fixed
OTEL_RESOURCE_ATTRIBUTESvalues being decoded as form data, whichchanged a
+to a space. Values are now only percent-decoded, as defined bythe Resource SDK specification.
(#8074)
Updated the schema URL of resources created by the SDK to use OpenTelemetry
Semantic Conventions version
1.45.0.(#8079)
Added support for batching the metric points exported by
PeriodicExportingMetricReader. When a maximum export batch size is set,using the new constructor overload or
PeriodicExportingMetricReaderOptions.MaxExportBatchSize, the metricpoints of each collection are split into batches of at most that many
metric points, even if that splits up the metric points of a single
metric. The batches are exported serially with the export timeout
applying to each export. It can also be configured with the
OTEL_METRIC_EXPORT_MAX_BATCH_SIZEenvironment variable.(#8053)
Fixed
PeriodicExportingMetricReaderexporting a collection which was stillin progress when
Shutdown()timed out to its exporter after the exporterhad been shut down.
([#8053](https://github.com/open-telemetry/opentelemetry-do...
Description has been truncated