Skip to content

Improve release-note rendering - #108

Merged
hdcodedev merged 1 commit into
mainfrom
fix/release-note-rendering
Oct 16, 2026
Merged

hdcodedev merged 1 commit into
mainfrom
fix/release-note-rendering

Conversation

@hdcodedev

Copy link
Copy Markdown
Member

Summary

  • Group release notes under user-facing headings for new features, bug fixes, improvements, documentation, and other changes.
  • Remove internal module suffixes from generated release-note entries.
  • Keep migration release pages when generated breaking-change content exists.
  • Restore ordered and unordered list markers in shared Markdown rendering.

Testing

  • git diff --cached --check
  • bash scripts/test-docs-release-links-contract.sh
  • npm run build
  • npm run lint — blocked by the installed TypeScript 7.0 and typescript-eslint incompatibility.
  • (human) Verified the implementation.

Test steps

  1. Run npm install.
  2. Run npm run build.
  3. Open a release notes page and a migration page.
  4. Confirm release notes use the new headings, Markdown lists show markers, and migration pages render when generated content is present.

@vercel

vercel Bot commented Oct 16, 2026 •

Copy link
Copy Markdown

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

Project Deployment Actions Updated
charts.hdcode.dev Ready Ready Preview Oct 16, 2026 6:44pm UTC

@hdcodedev
hdcodedev merged commit 120b9ea into main Oct 16, 2026
3 checks passed
@hdcodedev
hdcodedev deleted the fix/release-note-rendering branch October 16, 2026 18:45

This branch was successfully deployed

1 active deployment
Preview — 17143784 Deployed Oct 16, 2026 by vercel[bot]
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