docs: Point Federation Version Support doc to Changelog

RELEASE_CHECKLIST.md

@@ -241,8 +241,6 @@ Start following the steps below to start a release PR.  The process is **not ful
      - Run our compliance checks and update the `licenses.html` file as appropriate.
      - Ensure we're not using any incompatible licenses in the release.
 
-7. **MANUALLY CHECK AND UPDATE** the `federation-version-support.mdx` to make sure it shows the version of Federation which is supported by the Routter.
-
 11. Now, review and stage he changes produced by the previous step.  This is most safely done using the `--patch` (or `-p`) flag to `git add` (`-u` ignores untracked files).
 
     ```

apollo-federation/README.md

@@ -25,7 +25,7 @@ Any version may have breaking API changes, as this API is expected to only be u
 Instead, the version number matches exactly that of the `apollo-router` crate version using it.
 
 This version number is **not** that of the Apollo Federation specification being implemented.
-See [Router documentation](https://www.apollographql.com/docs/router/federation-version-support/)
+See the [Apollo Federation Changelog](https://www.apollographql.com/docs/graphos/schema-design/federated-schemas/reference/versions)
 for which Federation versions are supported by which Router versions.
 
 ## Contributing

apollo-federation/src/lib.rs

@@ -10,7 +10,7 @@
 //! Instead, the version number matches exactly that of the `apollo-router` crate version using it.
 //!
 //! This version number is **not** that of the Apollo Federation specification being implemented.
-//! See [Router documentation](https://www.apollographql.com/docs/router/federation-version-support/)
+//! See the [Apollo Federation Changelog](https://www.apollographql.com/docs/graphos/schema-design/federated-schemas/reference/versions)
 //! for which Federation versions are supported by which Router versions.
 
 #![warn(