Skip to content

Conversation

@sg-doc-holiday
Copy link

@sg-doc-holiday sg-doc-holiday bot commented Jan 28, 2026

Release notes

  • Adds a Mintlify-compatible Release Notes MDX page that renders structured release notes JSON into emoji category sections with concise bullet lists
  • Implements formatting rules for release notes following the style guide, including categorization into features, enhancements, and bug fixes
  • Includes release notes content for features, bug fixes, and improvements categorized under emojis like �38, �39, and �30
  • Updates the release-notes.mdx page to trim each release note entry to only the first sentence, improving readability by removing excess detail
  • Replaces the initial dynamic placeholder rendering in release-notes.mdx with static, style-guide-compliant release notes for the 2026-01-28 release date, using emoji category headings and concise bullet points without trailing periods
  • Applies wording and category name consistency updates in release-notes.mdx by renaming the 'New' category to 'Features' and replacing internal notes with user-facing stability improvements to better align with style guide requirements

This covers 3 commits.

Interaction Instructions

This PR was generated by Doc Holiday and is ready to be iterated on.

Leave comments on this pull request in plain English to guide Doc Holiday's next steps.
You might ask to:

  • Update or rewrite documentation
  • Create or update release notes
  • Remove sections or files
  • Merge this PR with another Doc Holiday PR

Examples:

  • @doc.holiday update these docs to follow my style guide: https://link.to/style-guide
  • @doc.holiday write new documentation about quantum compute and how its steam generates a 429
  • @doc.holiday combine this PR with #404
  • @doc.holiday delete this file: release-notes/file.md

Add a Mintlify-compatible Release Notes page that renders the newly generated release notes (in %NEW_RELEASE_NOTES% JSON form) into emoji category sections with concise bullet lists, following the release-notes formatting rules in the style guide.
Trim each release note entry to a single sentence by keeping only the first sentence and removing the follow-up detail sentences.
Replace the invalid MDX/JS placeholder rendering with static, style-guide-compliant release notes for the 2026-01-28 event date, using emoji category headers and bullet lists without trailing periods.
Apply wording consistency updates (use 'Features' category name) and remove an internal-facing 'dependencies' note in favor of a user-facing stability improvement, aligning with the style guide’s requirement to avoid internal changes and keep release notes concise.
@sonarqubecloud
Copy link

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants