Ensure upcoming releases page is synchronized across branches #89
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We only update one version of
docs/pages/upcoming-release.mdx
at a time, as this isn't really a "versioned" page. We only use this page to communicate what's coming in the next set of releases and when to expect them.As a result, consumers of our docs have a poor experience. If they're looking at the correct version of the docs, they see accurate and up to date info, but if they're on any other version, they see old, outdated, and inapplicable info.
We solve this by copying the default version of upcoming-releases.mdx to all other branches prior to deployment, ensuring that readers see the same content no matter which version is selected in the version selector.