As the release notes are generated from the docs as they were when the release was made, this will not include newer versions of the docs. This is not really an issue currently, as the v2.0.0 release doesn't include release notes at all and v2.1.0 is the newest at the time of writing, but it will be an issue when we release v2.2.0 😄. This will affect both the main release notes page and the sub-chapters as indicated in SUMMARY.md.
I'm not sure exactly what the right solution is here. I'm wondering whether we should recursively copy/symlink release notes from the dev version of the docs into the dir we're building the old docs from before we build them.
It would be nice to add the "release notes" chapters to the v2.0.0 docs while we're at it (see also: #1189).
As the release notes are generated from the docs as they were when the release was made, this will not include newer versions of the docs. This is not really an issue currently, as the v2.0.0 release doesn't include release notes at all and v2.1.0 is the newest at the time of writing, but it will be an issue when we release v2.2.0 😄. This will affect both the main release notes page and the sub-chapters as indicated in
SUMMARY.md.I'm not sure exactly what the right solution is here. I'm wondering whether we should recursively copy/symlink release notes from the dev version of the docs into the dir we're building the old docs from before we build them.
It would be nice to add the "release notes" chapters to the v2.0.0 docs while we're at it (see also: #1189).