Define a process when the docs of a feaure are merged but the feature doesn't make it in the release

The past couple of releases we've seen a few cases where the docs for a feature are merged, but the feature itself doesn't make it in the release after all. How can we mitigate this?

• How to avoid this in the first place?
  • Use MR dependencies
• What to do in case the docs are already merged?
  • Revert
  • Add an introduced note stating the next version