MongoDB

MongoDB’s per-version release notes each carry a dedicated “Known Issues” subsection, structured consistently across major versions. That consistency is useful: if you are on 7.0 and tracking a replication or index-build anomaly, the subsection is where MongoDB documents the gap between intended and actual behaviour, along with any available workaround.

The release notes are also the place to track deprecations and default-behaviour changes, which in MongoDB’s history have carried real operational weight. The removal of MMAPv1 in 4.2 and the shift to a majority default write concern in 5.0 both required deliberate migration work. The known-issues subsection is narrow in scope; the surrounding release notes are the wider surface worth reading before any major version upgrade.