fix: keep all of a PR's changesets in the release PR summary#4031
Conversation
The changeset release PR summary deduplicated entries by PR number, so a PR that ships more than one changeset had every entry after the first dropped from the summary (they stayed only in the raw output). Key the dedup on entry content instead, which keeps distinct changesets from the same PR while still collapsing one changeset repeated across package sections.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📜 Recent review details⏰ Context from checks skipped due to timeout. (3)
🔇 Additional comments (1)
WalkthroughThe release-PR enhancement script now deduplicates changeset entries by normalized full entry text instead of by the PR number from the header link. It reconstructs each list item’s text, normalizes whitespace for the dedupe key, and skips entries already seen. The related comments were updated to describe the new behavior. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 ESLint
ESLint install failed: dependency version conflict. Check your lock file or package.json. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
The auto-generated changeset release PR (
changeset-release/main) builds its## Improvements/## Bug fixessummary withscripts/enhance-release-pr.mjs. The script deduplicated summary entries by PR number, so when a single PR shipped more than one changeset, only the first entry survived and the rest were silently dropped from the summary. The dropped entries still appeared in the raw<details>block, which is how the mismatch surfaced (for example in #3998, where one PR's four changesets showed up as a single summary line).Fix
Deduplicate on the full entry text rather than the bare PR number. The entry text embeds the PR link, so:
Verified against the raw changeset output from #3998: that PR's changesets went from 1 to all 4 in the generated summary.