fix(site): render changelog with shared MDX typography - #1846
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
✅ Deploy Preview for vjs10-site ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
📦 Bundle Size Report🎨 @videojs/html — no changesPresets (7)
Media (10)
Players (5)
Skins (30)
UI Components (39)
Sizes are marginal over the root entry point. ⚛️ @videojs/react — no changesPresets (7)
Media (9)
Skins (27)
UI Components (33)
Sizes are marginal over the root entry point. 🧩 @videojs/core — no changesEntries (68)
🏷️ @videojs/element — no changesEntries (2)
📦 @videojs/store — no changesEntries (3)
🔧 @videojs/utils — no changesEntries (11)
📦 @videojs/spf — no changesEntries (4)
ℹ️ How to interpretJS sizes are initial static graph totals (minified + brotli). Lazy dynamic chunks are shown separately when present.
Run |
decepulis
marked this pull request as ready for review
July 15, 2026 18:05
mihar-22
approved these changes
Jul 15, 2026
decepulis
added a commit
that referenced
this pull request
Jul 16, 2026
(cherry picked from commit 07cbd16)
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
defaultMarkdownComponentsmapping as blog posts.changelog-contenttypography styles.mdx, escaping MDX-sensitive generated textWhy
Blog posts used shared MDX typography components, while plain-Markdown changelog entries could not use Astro's component mapping. The changelog page compensated with a partial CSS mirror that could drift and did not cover the full component set.
Impact
Blog and changelog Markdown now share one typography implementation. Future typography changes apply to both automatically, while generated release-note text remains safe for MDX parsing. The latest beta.25 prose and changelog workflow changes from
mainare preserved.Validation
env -u SENTRY_AUTH_TOKEN pnpm build:site— 14/14 tasks passed; all 25 changelog routes prerenderedNote
Low Risk
Site-only typography and content-pipeline changes; MDX escaping in release workflow reduces parse risk from untrusted commit titles.
Overview
Changelog entries move from plain Markdown (
.md) to MDX (.mdx) so release notes use the same typography path as the blog instead of a hand-maintained CSS mirror on the changelog page.The changelog Astro page now passes
defaultMarkdownComponentsinto<Content />and drops the large scoped.changelog-contentstyle block.content.config.tsloads*.mdxfromsrc/content/changelog/. CI is aligned:release-pr.ymlwrites versioned.mdxfiles and escapes<,>,{,}in git-cliff bodies outside inline code so PR titles cannot break MDX;changelog-prose.ymllooks for.mdxand instructs the prose writer to keep output MDX-safe.site/CLAUDE.mdis updated to describe MDX changelog generation and shared typography.Reviewed by Cursor Bugbot for commit 3378b25. Bugbot is set up for automated code reviews on this repo. Configure here.