You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
Cross-Session MessagingArea: what it touches
ImprovementsKind: in v2.1.225,
ImprovementsSection of the release
What
When an inbound cross-session peer message is held, the explanation now tells you whether an org managed setting or the repository's own settings forced it, rather than just reporting an explicit setting.
Details
Two new hold-reason cases: managed-setting and repo-setting, in addition to the plain explicit-setting case.
The repo case explains that a repo may only tighten, so your own "accept" cannot override it, and points at --setting-sources to exclude it.
The resolver was reworked to return both the effective value and which tier decided it; repo-level local and project settings are attributed as repoSettings.
Evidence
This repository's settings set "crossSessionInbound" to "hold" (a repo may only tighten, so your own "accept" cannot override it); remove the repo setting or exclude it with --setting-sources., This repository's settings set "crossSessionInbound" to "hold" (your own "accept" cannot override a repo tightening).
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
