Repository navigation
fix(ci): support Changesets v3 in version previews - #422
Conversation
|
View your CI Pipeline Execution ↗ for commit de4a3a7
☁️ Nx Cloud last updated this comment at |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
commit: |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub. |
GitHub Actions provides GITHUB_REPOSITORY, but the comment script only checked REPOSITORY. This skipped release notifications even when a valid published package list was supplied. Use the standard variable as a fallback while retaining the existing override. An explicitly empty GH_TOKEN input also bypasses the composite action's default. Fall back to github.token for comments and grant issues: write for linked-issue notifications. Document that the release workflow still requires its custom token; this fallback applies only to comments.

🎯 Changes
#414 and TanStack/query#11583 upgraded changesets to v3, and with the upgrade, I'm getting issues on the angular pre-release branch.
This PR updates
@changesets/get-release-planand@changesets/actionmatching the upgrade guide (links point to the section in the guide). It also updates the pnpm version mentioned in the readme, and the name of the output name of the action.I didn't find any major issues outside the prerelease workflow. It ignores a PR comments like here: https://github.com/TanStack/config/actions/runs/38833780698/job/116758200847#step:6:16 in the release #420 . You can see in the run that 0.3.5 was published but the step that uses an output does not detect it.
✅ Checklist
pnpm test:pr.🚀 Release Impact
Summary by CodeRabbit