How do you stop your README from turning into a pile of outdated lies?

With how fast code changes now especially with speedier refactoring tools our setup guides get outdated almost the next day.

A new teammate steps in follows the docs and immediately hits errors because the code moved on while the README stayed frozen. Making people update docs during PRs sounds nice in theory but it usually gets ignored when everyone is moving fast. How does your team force or encourage docs to stay accurate without slowing down shipping speed?