release: v3.3.0 - #425
Merged
Merged
Conversation
Contributor
Performance NumbersMeasured commit: Benchmark methodology is unchanged; the historical Standalone comparison is diagnostic regression smoke. Historical Standalone deltaDelta direction: + is better; - is worse.
Current TargetMap evidenceThese raw rows are current-run diagnostics. Use fresh bracketed controls before accepting a micro-optimization. |
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.
Automated release preparation for v3.3.0 (run: https://github.com/Ambiguous-Interactive/DxMessaging/actions/runs/31923135430).
Release checklist
package.jsonversion is 3.3.0 andCHANGELOG.mdhas the## [3.3.0]section below.release: v3.3.0title (release-tag.yml matches that subject on master).Changelog for 3.3.0
Added
Inspector wiring (#372).
Monitor and Flow Graph (#346).
MessageRegistrationBuildException(#367).
(#362).
Changed
(#404,
#411).
now marks problems (#353).
(#371).
(#374).
one message type (#374).
policy (#367).
(#362).
resolved once when registrations change instead of being re-collected on every emission, and
emissions no longer repeat handler and post-processor lookups the bus already resolved. One
interceptor costs roughly half what it did, and four cost roughly a quarter
(#408).
Fixed
MessageRegistrationTokenregistrations with null callbacks leaving partial token orbus state behind after throwing (#414).
until the next emission, while removals finish the current post phase
(#413).
taking effect during that same emission; interceptor changes now wait for the next emission, as
the snapshot semantics documentation already described
(#408).
DxMessagingStaticState.Reset()from inside an interceptor so it stops the rest of thedispatch instead of invoking callbacks against reset bus state
(#395).
(#345).
keep their height (#344).
(#384).
GlobalMessageBusScopeandRegistrationDisposablevalues restoring or removing newerstate, and remove the 1,024 nested-scope cap
(#375).
working (#367).
object-lookup APIs (#365,
#367).
What happens after merge
release: v3.3.0commit on master and pushes the annotated tagv3.3.0.v3.3.0ref and manually dispatch release.yml: validate (pack + attest), the trusted Unity editmode check, the .unitypackage export,npm publish (Trusted Publishing), then the GitHub Release with the .tgz, .sha256, and .unitypackage assets
plus the asset-store-submission artifact.