fix(release-blog-posts): follow commonmark spec and include new lines #5147
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.
This PR introduces the GitHub Flavoured Markdown Plugin (Remark) and updates the Release Blog Post script to follow the Hard Line convention from CommonMark.
It also updates all existing blog posts to follow that convention.
Reasoning behind:
When we switched to MDXJS as the Parser for Markdown, it meant that we also adopted the standard CommonMark specification for Markdown. Whilst most of the Markdown files got fixed, and whilst
<br />tags are technically not invalid CommonMark syntax, they're not part of the specification.Thus, we needed to update the blog posts to follow the specification.
Closes #5146