Repository navigation
docs: prepare v4.18.4 release notes - #352
Conversation
[Low impact] The release-note change appears safe to merge.
|
Archfit: Architecture needs attention · advisory · no baselineNext: Advisories never block. Review the listed dimensions and diagnostics on the archfit/state check. 95 advisories · never block
On every row: Imbalanced coupling · critical · existed before this pull request · across modules · high volatility.
Why: functional coupling across a module boundary to a volatile target: a change on one side forces a change on the other (Balanced Coupling: critical severity) Why: intrusive (implementation-level) coupling across a module boundary to a volatile target: a change on one side forces a change on the other (Balanced Coupling: critical severity) Evidence and inputsDecision
Dimensions
Evidence gaps
Inputs and identity
Measurement is customer-attested: the producer is authenticated, the report content is not independently checked. For coding agentsAgent tasks[] |
Prepare the reviewed, committed release-note source for v4.18.4 after merging #350. Application changes since v4.18.3 exactly match reviewed PR350 source. Merged-source static/type/dependency/build checks and 231 clean-import checks pass. Three unchanged Git-helper tests hit 5-second command timeouts during the first concurrent run; focused serial reproduction checks and the complete unit suite were rerun with bounded concurrency, without changing code/timeouts. Publication remains gated on green final-head CI and notes merge. This PR changes only CHANGELOG.md. No live bridge update or restart.