Repository navigation
Conversation
Promotes rc.2 unchanged. No code moves in this commit — the five packages drop their prerelease suffix and the two release-candidate changelog entries become one. DSoftStudio.Mediator 1.4.0-rc.2 -> 1.4.0 DSoftStudio.Mediator.Abstractions 1.4.0-rc.2 -> 1.4.0 DSoftStudio.Mediator.FluentValidation 1.0.10-rc.2 -> 1.0.10 DSoftStudio.Mediator.HybridCache 1.0.10-rc.2 -> 1.0.10 DSoftStudio.Mediator.OpenTelemetry 1.1.1-rc.2 -> 1.1.1 The changelog follows what 1.3.0 did: one entry per release, with the candidates leaving no trace. Merging them is not a copy-and-paste, because two of rc.2's fixes repaired code that the rc cycle itself introduced. No released version ever carried those defects, so listing them would describe a failure nobody could have suffered and make the release read as buggier than it was. Both were checked against the v1.3.0 tree rather than assumed: DSOFT011 0 occurrences in v1.3.0 MediatorNotificationTracingObserver file absent in v1.3.0 Everything else from rc.2 stays, because it is genuinely pre-existing: the stream tracing behaviour and the hand-rolled accessibility check both exist in v1.3.0, so their defects are real for anyone upgrading from it. Also resolves the cross-references the merge left dangling. "The equivalent guard on the request side shipped in rc.1" says nothing in an entry where rc.1 does not exist; both halves now land together, which is what a reader of 1.4.0 sees. Verified after packing that the graph is coherent: the three companions resolve DSoftStudio.Mediator 1.4.0 and the core resolves Abstractions 1.4.0.
Contributor
SummarySummary
CoverageDSoftStudio.Mediator - 91.6%
DSoftStudio.Mediator.Abstractions - 91.3%
DSoftStudio.Mediator.FluentValidation - 100%
DSoftStudio.Mediator.Generators - 91.5%
DSoftStudio.Mediator.HybridCache - 96.8%
DSoftStudio.Mediator.OpenTelemetry - 92.9%
|
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.
Promotes
1.4.0-rc.2unchanged. No code moves in this PR — the five packages drop their prerelease suffix and the two release-candidate changelog entries become one.DSoftStudio.MediatorDSoftStudio.Mediator.AbstractionsDSoftStudio.Mediator.FluentValidationDSoftStudio.Mediator.HybridCacheDSoftStudio.Mediator.OpenTelemetryThe changelog merge is not a copy-and-paste
The repository keeps one entry per release — 1.3.0 had candidates and left no trace of them — so the two rc entries consolidate rather than accumulate.
Two
Fixedbullets are dropped rather than merged. Both repaired code that the rc cycle itself introduced, so no released version ever carried the defect. Listing them would describe a failure nobody could have suffered, and make the release read as buggier than it was. Checked against thev1.3.0tree rather than assumed:Everything else from rc.2 stays, because it is genuinely pre-existing.
MediatorStreamTracingBehaviorexists inv1.3.0, so its five telemetry defects are real for anyone upgrading from there, and so is the hand-rolled accessibility check inStreamGenerator.The merge also left cross-references dangling, and those are resolved. "The equivalent guard on the request side shipped in rc.1" says nothing in an entry where rc.1 does not exist; both halves now land together, which is what a reader of 1.4.0 actually sees.
Verified
DSoftStudio.Mediator 1.4.0, and the core resolvesAbstractions 1.4.0rc.1/rc.2references survive inside the[1.4.0]entryAfter merge
Tag
v1.4.0, then the Release, then the publish workflow. The tag guard requires the tag to be reachable frommain, so the merge has to land first.One decision left: whether the 1.4.0 Release is marked Latest. It would displace
v1.3.0, which is normal for a stable — but it is the first thing a visitor sees, so it is worth being deliberate rather than defaulted.