Documentation is part of a release
A behavior change needs matching documentation before it can deploy. Each affected topic includes Summary, Technical, and Expert versions.
What the checks do
GitHub compares the recorded code fingerprint with the candidate release. Missing or outdated documentation stops the deployment instead of letting the wiki quietly fall behind.
Versions matter
The release records which code and documentation belong together. Failed deployments are not marked current, and rollback points readers back to the matching behavior.