chore: merge master into release/6.5.0 - #807
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Release 6.4.4
Parse (#NNNN) references from commits between the previous release tag and this version's tag (falling back to the X.Y.x branch when untagged), so a release still gets a complete changelog even if PRs were never milestoned. Adds a --dry-run flag and optional GITHUB_TOKEN auth. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Each generated changelog entry now carries an MDX comment naming the PR
author(s) ({/* REVIEW-PENDING @author ... */}). Authors delete the line to
confirm their entry. A new CI workflow (check-release-notes.yml) fails any PR
to master that still contains an unresolved marker, so release notes cannot be
published until every entry is confirmed.
- scripts/changelog-constants.ts: shared REVIEW_MARKER sentinel
- scripts/check-changelog-review.ts + check:changelog-review script
- generate-changelog.ts: capture PR author, inject markers deterministically
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
…ssing Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Revert PR discovery to milestone-based lookup (assign a PR to the X.Y.Z milestone to include it), replacing the tag/branch commit-range diffing that broke when no version tag exists yet. Keeps GITHUB_TOKEN auth, --dry-run, and per-item review markers. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
3 participants
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.
Brings the docs
masterbranch up to date intorelease/6.5.0.masteris ahead by 27 commits (and the branches have diverged), including thechangelog CI work that should also apply to the release branch:
changelog entry carries a
REVIEW-PENDINGmarker;check-release-notes.ymlfails any push to the branch that still has an unresolved marker, so release
notes can't publish until every entry is confirmed.
switched it to release-commit ranges, but a later commit reverted it back to
milestones — assign a PR to the
X.Y.Zmilestone to include it).Merge (do not squash) to preserve history on the release branch.
🤖 Generated with Claude Code