fix: changeset release now catches server-changes#4209
Conversation
|
|
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. (4)
🔇 Additional comments (2)
WalkthroughThis change refactors scripts/enhance-release-pr.mjs to centralize retrieval of server change markdown data. parseServerChanges() now calls a new getServerChangeFileData() helper instead of directly reading the .server-changes directory. This helper first attempts to load live .server-changes/*.md files via getLiveServerChangeFileData(); if none are found, it falls back to getDeletedServerChangeFileDataFromReleaseBranch(), which computes a git merge-base between configurable base and release refs, identifies deleted .server-changes files in that range, and recovers their contents using git show, skipping individual files that fail to recover. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches📝 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 |
Read .server-changes from git when the working tree copy has already been cleaned up, and log recovery failures instead of swallowing them. Folds in the fix from #4209. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014CjQVhMqLbRo3VuLaGSLfg
|
closed in favour of #4204 |
Changeset releases were missing server-changes from the generated release notes due to ordering issues.
What changed:
enhancement runs.