Skip to content

fix: expose the changelog fallback in Markdown#748

Draft
parvahuja wants to merge 1 commit into
mainfrom
parv/markdown-changelog-fallback
Draft

fix: expose the changelog fallback in Markdown#748
parvahuja wants to merge 1 commit into
mainfrom
parv/markdown-changelog-fallback

Conversation

@parvahuja

@parvahuja parvahuja commented Jul 25, 2026

Copy link
Copy Markdown
Member

What changed

When release data is unavailable during a build, generated Markdown now shows a short message with a link to Tempo's GitHub releases instead of an HTML comment.

The post-build audit also rejects the hidden fallback if it reaches a .md page or llms-full.txt. It checks the Markdown node rather than raw text, so the same marker remains valid inside a fenced example.

Why

Vocs represents a failed changelog fetch as <!-- changelog unavailable -->. That is invisible to a Markdown reader, so the generated changelog appears empty.

Converting that exact marker gives agents a useful canonical source without changing the authored page or the human-rendered site.

Validation

  • env CI=true pnpm test — 299 tests passed
  • env CI=true VITE_USE_HTTP=true NODE_OPTIONS=--max-old-space-size=4096 pnpm build
  • pnpm run check:markdown
  • ./node_modules/.bin/biome check src/lib/markdown-output.ts src/lib/markdown-output.test.ts scripts/check-markdown-components.mjs

@vercel

vercel Bot commented Jul 25, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
tempo-docs Ready Ready Preview, Comment Jul 25, 2026 1:11am

Request Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant