docs: changelog entry for Chrome Extension updates#36
Merged
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
samgutentag
added
changelog
Member
|
Verification status (2026-05-26): Verified: customers can use this. Ready to publish.
Note: per #38's body, this draft can be closed in favor of the consolidated weekly post (#38). Labels: |
samgutentag
force-pushed
the
mintlify/b68a87cf
branch
from
931e50a to
54fd66c
Compare
Restructure body to canonical changelog shape: bold opener sentence, bullet list with **Lead** — body items, single docs link at end. Add required `type: update` frontmatter; unquote `date:` and `category:` per canonical convention. Wire the entry into the three sites the initial draft missed: - docs.json nav (under Changelog tab → 2026 group) - changelog/index.mdx (master index with tag-filter UI) - merge-queue/changelog.mdx (product-page index; adds new May 2026 section above April) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
samgutentag
added a commit
that referenced
this pull request
May 26, 2026
…ring Adds `scripts/sync-changelog.py`, which regenerates the four sites the changelog lives on from a single source of truth: the frontmatter of each `changelog/*.mdx` entry. Removes the manual-maintenance burden that came up in PR #36/#37/#39 review (each changelog PR previously had to update docs.json + master index + product-page index in addition to the entry file). The script targets: - docs.json — Changelog tab year-group `pages` arrays (surgical replace) - changelog/index.mdx — master index with tag-filter UI - merge-queue/changelog.mdx — entries where category = "Merge Queue" - flaky-tests/changelog.mdx — entries where category = "Flaky Tests" Other categories (Code Quality, CI Autopilot, Web App) appear in the master index but have no product-page index per current convention. Usage: python3 scripts/sync-changelog.py apply python3 scripts/sync-changelog.py --check CI mode; exits 1 on drift Also commits a normalization pass on the 4 target files: same-day entries are now sorted alphabetically by slug (was somewhat random), and one stray blank line after frontmatter is dropped. No content changes — all 154 entries preserved. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
4 tasks
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
1 participant
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
Adds a weekly changelog post covering the Chrome Extension improvements shipped since the last changelog entry (April 30).
Changes
changelog/2026-05-19-merge-queue-chrome-extension-updates.mdxdraft postContext
Only one product-affecting PR has merged since the April 30 "Merge Queue: Chrome Extension" changelog entry: #29, which documents
Skip batching,Celebration Mode, and automatic bot comment hiding in the Chrome Extension. The post matches the tone and structure of recent entries on trunk.io/changelog.