chore(scripts/create-github-release): fix release-notes diff range after 'Version Packages' PR is squash-merged - #11279
Conversation
|
View your CI Pipeline Execution ↗ for commit 08ac43e
☁️ Nx Cloud last updated this comment at |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 10 included reviews per hour; 7 remain after this review. 📝 WalkthroughWalkthroughThe release script now recognizes ChangesRelease commit handling
Estimated code review effort: 1 (Trivial) | ~5 minutes Merge Risk: ⚪ Minimal · up to This localized CI change corrects GitHub Release changelog ranges after squash-merging Version Packages PRs. No actionable merge-blocking risk remains beyond normal checks and review. Suggested reviewers: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 Generate unit tests (beta)
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 |
🚀 Changeset Version PreviewNo changeset entries found. Merging this PR will not cause a version bump for any packages. |
size-limit report 📦
|
…ter 'Version Packages' PR is squash-merged
08ac43e to
aaa789d
Compare
🎯 Changes
The GitHub Release published today (
release-2026-08-24-1925) listed three unrelated svelte-query fixes from the previous release instead of the two commits actually included (#11274, #11275). npm publishing and package versions were unaffected — only the "## Changes" summary on the GitHub Release was wrong.Root cause:
scripts/create-github-release.mjsfinds the previous release commit by grepping the full commit message for the substringci: changeset release(the commit messagechangesets/actionwrites on itschangeset-release/mainbranch). When the "Version Packages" PR carries a single commit, GitHub's squash-merge copies that commit's message into the squash commit body, so the substring survives and the grep works. When the PR is updated multiple times before merge (as happened today, after both #11274 and #11275 landed in quick succession), the PR has multiple commits, and GitHub's squash-merge instead uses the PR title only — so the squash commit body no longer containsci: changeset release, the grep silently skips the actual release commit, and the script's "previous release" pointer shifts back by one release.TanStack/routerhit and fixed this exact bug in #7456 — this PR ports that fix:git log --grepnow anchors both patterns with^and additionally matches^ci: Version Packages(the squash commit's title), so the release commit is found regardless of how GitHub composed the squash message.ci: Version Packagesas a release commit to exclude.Verified locally by re-running the (patched) diff-range logic against today's actual history — it now resolves
previousReleaseto96f2da635(#11271) instead of388bbaf18, and correctly yields exactly the #11274/#11275 commits for the changelog.✅ Checklist
pnpm run test:pr.🚀 Release Impact
Summary by CodeRabbit