Repository navigation
Bump Cronos and 15 others - #1277
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.95.1 Bumps MailKit from 4.18.1 to 4.18.2 Bumps Markdig from 1.4.1 to 1.5.0 Bumps Marten from 9.50.3 to 9.54.1 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 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.1 Bumps OpenTelemetry.Instrumentation.Http from 1.20.0 to 1.20.1 Bumps QRCoder from 1.6.0 to 1.8.1 Bumps WolverineFx.Marten from 6.51.1 to 6.54.0 Bumps WolverineFx.RuntimeCompilation from 6.51.1 to 6.54.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.95.1 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.5.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dotnet - dependency-name: Marten dependency-version: 9.54.1 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: 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.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dotnet - dependency-name: OpenTelemetry.Instrumentation.Http dependency-version: 1.20.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dotnet - dependency-name: QRCoder dependency-version: 1.8.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dotnet - dependency-name: WolverineFx.Marten dependency-version: 6.54.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dotnet - dependency-name: WolverineFx.RuntimeCompilation dependency-version: 6.54.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.96.0.
Release notes
Sourced from JasperFx's releases.
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.5.0.
Release notes
Sourced from Markdig's releases.
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.54.2.
Release notes
Sourced from Marten's releases.
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.14.
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.14.
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.14.
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.
Pinned OpenTelemetry.Exporter.OpenTelemetryProtocol at 1.20.1.
Release notes
Sourced from OpenTelemetry.Exporter.OpenTelemetryProtocol's releases.
1.20.1
For highlights and announcements pertaining to this release see: Release Notes > 1.20.1.
The following changes are from the previous release 1.20.0.
NuGet: OpenTelemetry v1.20.1
Fixed a possible race condition on ARM64 when multiple threads record the
first measurement with no tags, or the first overflow measurement, that could
cause the measurement to be recorded incorrectly.
(#7951)
Fixed self-diagnostics preamble redaction of quoted or encoded PEM material
and prefixed JWTs.
(#7955)
Fixed default HTTP client log filtering when registering the OTLP log exporter
through
OpenTelemetryLoggerOptions.(#7959)
Fixed legacy self-diagnostics logging terminating the process when the log
file is truncated or the log volume runs out of space.
(#7956)
Experimental (pre-release builds only): Fixed
Logger.EmitLogignoringinstrumentation suppression, which could cause recursive exports or deadlocks.
(#7961)
Fixed delta double counters losing subsequent measurements after a non-finite
or large value and idle metric points with a
NaNvalue failing to be reclaimed.(#7963)
Improve the assignment of values to exponential histogram buckets when the
value is near a bucket boundary by using a pre-computed lookup table.
(#7911)
Fixed
LogRecords being returned to the shared pool while still queued forexport when an exporter stops enumerating a single-item or array
Batch<LogRecord>early which could cause aBatchLogRecordExportProcessoron the same provider to export missing or incorrect data.
(#7965)
Fixed a
SuppressInstrumentationScope.Enter()reference count never beingreleased when the
Activityit was entered for is not recorded, which causedall subsequent telemetry in that execution context to be suppressed.
(#7966)
Self-diagnostics log files, whether configured through
OTEL_DIAGNOSTICS.jsonor
SelfDiagnosticsOptions, are now always created as new files.(#7968)
... (truncated)
1.20.1-rc.1
The following changes are from the previous release 1.20.0.
NuGet: OpenTelemetry v1.20.1-rc.1
Fixed a possible race condition on ARM64 when multiple threads record the
first measurement with no tags, or the first overflow measurement, that could
cause the measurement to be recorded incorrectly.
(#7951)
Fixed self-diagnostics preamble redaction of quoted or encoded PEM material
and prefixed JWTs.
(#7955)
Fixed default HTTP client log filtering when registering the OTLP log exporter
through
OpenTelemetryLoggerOptions.(#7959)
Fixed legacy self-diagnostics logging terminating the process when the log
file is truncated or the log volume runs out of space.
(#7956)
Experimental (pre-release builds only): Fixed
Logger.EmitLogignoringinstrumentation suppression, which could cause recursive exports or deadlocks.
(#7961)
Fixed delta double counters losing subsequent measurements after a non-finite
or large value and idle metric points with a
NaNvalue failing to be reclaimed.(#7963)
Improve the assignment of values to exponential histogram buckets when the
value is near a bucket boundary by using a pre-computed lookup table.
(#7911)
Fixed
LogRecords being returned to the shared pool while still queued forexport when an exporter stops enumerating a single-item or array
Batch<LogRecord>early which could cause aBatchLogRecordExportProcessoron the same provider to export missing or incorrect data.
(#7965)
Fixed a
SuppressInstrumentationScope.Enter()reference count never beingreleased when the
Activityit was entered for is not recorded, which causedall subsequent telemetry in that execution context to be suppressed.
(#7966)
Self-diagnostics log files, whether configured through
OTEL_DIAGNOSTICS.jsonor
SelfDiagnosticsOptions, are now always created as new files.(#7968)
Self-diagnostics messages written to the sinks configured by
SelfDiagnosticsOptionsare now truncated to 16,384 characters so that the... (truncated)
1.20.1-beta.1
The following changes are from the previous release 1.20.0-beta.1.
NuGet: OpenTelemetry.Exporter.Prometheus.AspNetCore v1.20.1-beta.1
Fixed scrape responses being handed to the server in a single write, which
made the server buffer a full copy of the response for each client that did
not read it until the request completed or timed out. Responses are now
written in bounded slices so the server's back-pressure applies.
(#7957)
Fixed startup scrapes permanently omitting
target_infoand configuredresource constant labels from subsequent scrape responses.
(#7984)
Updated OpenTelemetry core component version(s) to
1.20.1.(#7990)
See CHANGELOG for details.
NuGet: OpenTelemetry.Exporter.Prometheus.HttpListener v1.20.1-beta.1
Fixed scrape responses being handed to the server in a single write, which
on Linux and macOS made the listener allocate and hold a full copy of the
response for each client that did not read it until the request completed or
timed out. Responses are now written in bounded slices.
(#7957)
Fixed scrape requests that announce a request body holding a thread pool
thread after their response had been sent on Linux and macOS for as long as
the client kept trickling in the body. The connection is now closed after
responding to a request with a body instead of being kept alive.
(#7962)
Fixed startup scrapes permanently omitting
target_infoand configuredresource constant labels from subsequent scrape responses.
(#7984)
Updated OpenTelemetry core component version(s) to
1.20.1.(#7990)
See CHANGELOG for details.
NuGet: OpenTelemetry.Shims.OpenTracing v1.20.1-beta.1
1.20.1.(#7990)
See CHANGELOG for details.
Commits viewable in compare view.
Pinned OpenTelemetry.Extensions.Hosting at 1.20.1.
Release notes
Sourced from OpenTelemetry.Extensions.Hosting's releases.
1.20.1
For highlights and announcements pertaining to this release see: Release Notes > 1.20.1.
The following changes are from the previous release 1.20.0.
NuGet: OpenTelemetry v1.20.1
Fixed a possible race condition on ARM64 when multiple threads record the
first measurement with no tags, or the first overflow measurement, that could
cause the measurement to be recorded incorrectly.
(#7951)
Fixed self-diagnostics preamble redaction of quoted or encoded PEM material
and prefixed JWTs.
(#7955)
Fixed default HTTP client log filtering when registering the OTLP log exporter
through
OpenTelemetryLoggerOptions.(#7959)
Fixed legacy self-diagnostics logging terminating the process when the log
file is truncated or the log volume runs out of space.
(#7956)
Experimental (pre-release builds only): Fixed
Logger.EmitLogignoringinstrumentation suppression, which could cause recursive exports or deadlocks.
(#7961)
Fixed delta double counters losing subsequent measurements after a non-finite
or large value and idle metric points with a
NaNvalue failing to be reclaimed.(#7963)
Improve the assignment of values to exponential histogram buckets when the
value is near a bucket boundary by using a pre-computed lookup table.
(#7911)
Fixed
LogRecords being returned to the shared pool while still queued forexport when an exporter stops enumerating a single-item or array
Batch<LogRecord>early which could cause aBatchLogRecordExportProcessoron the same provider to export missing or incorrect data.
(#7965)
Fixed a
SuppressInstrumentationScope.Enter()reference count never beingreleased when the
Activityit was entered for is not recorded, which causedall subsequent telemetry in that execution context to be suppressed.
(#7966)
Self-diagnostics log files, whether configured through
OTEL_DIAGNOSTICS.jsonor
SelfDiagnosticsOptions, are now always created as new files.(#7968)
... (truncated)
1.20.1-rc.1
The following changes are from the previous release 1.20.0.
NuGet: OpenTelemetry v1.20.1-rc.1
Fixed a possible race condition on ARM64 when multiple threads record the
first measurement with no tags, or the first overflow measurement, that could
cause the measurement to be recorded incorrectly.
(#7951)
Fixed self-diagnostics preamble redaction of quoted or encoded PEM material
and prefixed JWTs.
(#7955)
Fixed default HTTP client log filtering when registering the OTLP log exporter
through
OpenTelemetryLoggerOptions.(#7959)
Fixed legacy self-diagnostics logging terminating the process when the log
file is truncated or the log volume runs out of space.
(#7956)
Experimental (pre-release builds only): Fixed
Logger.EmitLogignoringinstrumentation suppression, which could cause recursive exports or deadlocks.
(#7961)
Fixed delta double counters losing subsequent measurements after a non-finite
or large value and idle metric points with a
NaNvalue failing to be reclaimed.(#7963)
Improve the assignment of values to exponential histogram buckets when the
value is near a bucket boundary by using a pre-computed lookup table.
(#7911)
Fixed
LogRecords being returned to the shared pool while still queued forexport when an exporter stops enumerating a single-item or array
Batch<LogRecord>early which could cause aBatchLogRecordExportProcessoron the same provider to export missing or incorrect data.
(#7965)
Fixed a
SuppressInstrumentationScope.Enter()reference count never beingreleased when the
Activityit was entered for is not recorded, which causedall subsequent telemetry in that execution context to be suppressed.
(#7966)
Self-diagnostics log files, whether configured through
OTEL_DIAGNOSTICS.jsonor
SelfDiagnosticsOptions, are now always created as new files.(#7968)
Self-diagnostics messages written to the sinks configured by
SelfDiagnosticsOptionsare now truncated to 16,384 characters so that the... (truncated)
1.20.1-beta.1
The following changes are from the previous release 1.20.0-beta.1.
NuGet: OpenTelemetry.Exporter.Prometheus.AspNetCore v1.20.1-beta.1
Fixed scrape responses being handed to the server in a single write, which
made the server buffer a full copy of the response for each client that did
not read it until the request completed or timed out. Responses are now
written in bounded slices so the server's back-pressure applies.
(#7957)
Fixed startup scrapes permanently omitting
target_infoand configuredresource constant labels from subsequent scrape responses.
(#7984)
Updated OpenTelemetry core component version(s) to
1.20.1.(#7990)
See CHANGELOG for details.
NuGet: OpenTelemetry.Exporter.Prometheus.HttpListener v1.20.1-beta.1
Fixed scrape responses being handed to the server in a single write, which
on Linux and macOS made the listener allocate and hold a full copy of the
response for each client that did not read it until the request completed or
timed out. Responses are now written in bounded slices.
(#7957)
Fixed scrape requests that announce a request body holding a thread pool
thread after their response had been sent on Linux and macOS for as long as
the client kept trickling in the body. The connection is now closed after
responding to a request with a body instead of being kept alive.
(#7962)
Fixed startup scrapes permanently omitting
target_infoand configuredresource constant labels from subsequent scrape responses.
(#7984)
Updated OpenTelemetry core component version(s) to
1.20.1.(#7990)
See CHANGELOG for details.
NuGet: OpenTelemetry.Shims.OpenTracing v1.20.1-beta.1
1.20.1.(#7990)
See CHANGELOG for details.
Commits viewable in compare view.
Pinned OpenTelemetry.Instrumentation.AspNetCore at 1.20.1.
Release notes
Sourced from OpenTelemetry.Instrumentation.AspNetCore's releases.
1.20.1
NuGet: OpenTelemetry.Extensions.AWS v1.20.1
1.20.1.(#5651)
See CHANGELOG for details.
NuGet: OpenTelemetry.Instrumentation.AWS v1.20.1
No notable changes.
See CHANGELOG for details.
NuGet: OpenTelemetry.Instrumentation.AWSLambda v1.20.1
No notable changes.
See CHANGELOG for details.
1.20.1-rc.1
NuGet: OpenTelemetry.Instrumentation.Process v1.20.1-rc.1
1.20.1.(#5651)
See CHANGELOG for details.
1.20.1-beta.1
NuGet: OpenTelemetry.Extensions.Enrichment v1.20.1-beta.1
1.20.1.(#5651)
See CHANGELOG for details.
1.20.1-alpha.1
NuGet: OpenTelemetry.Instrumentation.EventCounters v1.20.1-alpha.1
1.20.1.(#5651)
See CHANGELOG for details.
Commits viewable in compare view.
Pinned OpenTelemetry.Instrumentation.Http at 1.20.1.
Release notes
Sourced from OpenTelemetry.Instrumentation.Http's releases.
1.20.1
NuGet: OpenTelemetry.Extensions.AWS v1.20.1
1.20.1.(#5651)
See CHANGELOG for details.
NuGet: OpenTelemetry.Instrumentation.AWS v1.20.1
No notable changes.
See CHANGELOG for details.
NuGet: OpenTelemetry.Instrumentation.AWSLambda v1.20.1
No notable changes.
See CHANGELOG for details.
1.20.1-rc.1
NuGet: OpenTelemetry.Instrumentation.Process v1.20.1-rc.1
1.20.1.(#5651)
See CHANGELOG for details.
1.20.1-beta.1
NuGet: OpenTelemetry.Extensions.Enrichment v1.20.1-beta.1
1.20.1.(#5651)
See CHANGELOG for details.
1.20.1-alpha.1
NuGet: OpenTelemetry.Instrumentation.EventCounters v1.20.1-alpha.1
1.20.1.(#5651)
See CHANGELOG for details.
Commits viewable in compare view.
Updated QRCoder from 1.6.0 to 1.8.1.
Release notes
Sourced from QRCoder's releases.
1.8.1
What's Changed
New Contributors
Full Changelog: Shane32/QRCoder@v1.8.0...v1.8.1
1.8.0
What's Changed
New Contributors
Full Changelog: Shane32/QRCoder@v1.7.0...v1.8.0
1.7.0
New Features
Performance Enhancements
BitArrayby @TimothyMakkison in optimise: remove unnecessaryBitArrayShane32/QRCoder#607QRCodeGenerator(NETCORE_APP only) by @gfoidl in Reduced some allocations inQRCodeGenerator(NETCORE_APP only) Shane32/QRCoder#595ArrayPool.Rentto preventbyte[]allocation by @TimothyMakkison in PngByteQRCode: useArrayPool.Rentto preventbyte[]allocation Shane32/QRCoder#615QRCodewith one colour by @TimothyMakkison in optimise: fillQRCodewith one colour Shane32/QRCoder#626Bug Fixes
Documentation Changes
Refactoring and Other Changes
... (truncated)
Commits viewable in compare view.
Pinned WolverineFx.Marten at 6.55.1.
Release notes
Sourced from WolverineFx.Marten's releases.
6.55.1
Fixes
DatabaseBatchCommandExceptionand logged as an Error. Genuine SQL/connection failures are still reported.HttpEndpointaimed at/_wolverine/invokein its default (buffered) mode now delivers by posting each envelope individually, instead of receiving a 415 for every batch and retrying forever./batch/{queue}and.SendInline()endpoints are unchanged.6.55.0
Highlights
WolverineFx.Bobcat is out of alpha, on Bobcat 1.0.0 (#5222, #5229). Bobcat 1.0.0 shipped tonight, and
WolverineFx.BobcatandWolverineFx.Bobcat.EventModelnow publish as stable 6.55.0 instead of-alpha.1.WolverineFx.Bobcat.Httpstays6.55.0-alpha.1until Alba 9 ships stable, because a stable package cannot depend on Alba 9.0.0-rc.2. A spec project thatwrite-specsgenerates with no--wolverine-versionpins the stableWolverineFx.Bobcat(#5222, #5223).MessageCausedBynames your handler (#5224, #5225).IWolverineObserver.MessageCausedByreported the generated handler class (Internal.Generated.WolverineHandlers.StartTripHandler939323516). It now reports the handler you wrote (TripService.StartTripHandler), the same string as themessage.handlerspan tag, resolved at codegen time. Code generated by an earlier version keeps working through the old overload.CosmosDB sagas start with a conditional create (#5221, thanks @thechucklingatom). A second start message for an existing saga id used to silently overwrite the running saga. It now fails with the
SagaConcurrencyExceptionthat Marten, Azure Blob and S3 already raise, so oneOnException<SagaConcurrencyException>()policy covers every provider.Fixes
ListeningAgent.StartAsyncis serialized, and deliveries are deferred to a drainedBufferedReceiver(#5228)CancellationTokenSource(#5226)Dependencies
Originno longer raises aSourceDisagreement)Full Changelog: JasperFx/wolverine@V6.54.0...V6.55.0
6.54.0
Highlights
Dead letter failure groups (#5209, #5210). Wolverine now fingerprints every message as it moves to dead letter storage, so dead letters can be managed one failure group at a time:
IDeadLetterFingerprinterhashes the exception type and the first stack frame from application code. Register your own to replace it.DeadLetterEnvelopeQuerygainsFailureGroup,ExceptionMessageMatch(Exact / Contains),TenantIdandArchived.SummarizeAllAsyncoverload groups by failure group, message type or endpoint, with first and last failure times.ReplayMatchingAsync,DiscardMatchingAsync,ArchiveMatchingAsyncandRestoreMatchingAsyncreport how many dead letters they affected.ReplayCount,LastReplayedAtandFirstFailedAt.DurabilitySettings.ArchivedDeadLetterRetention.IDeadLetters.Capabilitiestells you what a store supports.All changes are additive. The relational stores pick up seven nullable columns on
wolverine_dead_letters, an index and a newwolverine_dead_letter_historytable through the normal schema migration. See the dead letter storage guide.Deduplication fixes (#5205, #5206, #5208), and Bobcat 1.0.0-rc.4 dependency pins (#5211). The
WolverineFx.Bobcat*packages remain alpha (6.54.0-alpha.1).What's Changed
Full Changelog: JasperFx/wolverine@V6.53.0...V6.54.0
6.53.0
What's Changed
New Contributors
Full Changelog: JasperFx/wolverine@V6.52.0...V6.53.0
6.52.0
Wolverine 6.52.0 is a feature release. The headline items are Aspire-style registration by connection-string name for every transport and every message store, timer agents for short-cadence recurring schedules, and the 6.x groundwork for Wolverine 7.0's one-chain-per-handler model. There are no breaking API changes. Two behavior changes are worth knowing about up front: recurring schedules that fire more often than every 15 minutes now run on a timer agent (opt out per schedule with
UseScheduledMessages()), and outgoing envelopes a transport cannot map are dead-lettered instead of being logged and deleted.Many thanks to everyone who reported issu...
Description has been truncated