fix: pin snapshot action with changesets CLI v3 publish parsing - #755
fix: pin snapshot action with changesets CLI v3 publish parsing#755ardatan wants to merge 2 commits into
Conversation
Point release-snapshot at the fix that recognizes bare name@version lines from @changesets/cli v3 so alpha/rc comments list published packages again. Temporary pin to ardatan/changesets-action until the-guild-org/changesets-snapshot-action#3 is merged.
|
Follow up the-guild-org/changesets-snapshot-action#3 review that disallows slashes in v3 name@version package name segments.
There was a problem hiding this comment.
Pull request overview
Updates the shared reusable snapshot-release workflow so snapshot publishing can correctly parse @changesets/cli v3 publish output and avoid posting incorrect “no linked changesets” PR comments across downstream repos consuming release-snapshot.yml@v1.
Changes:
- Switch the snapshot publishing step to a temporarily pinned fork (
ardatan/changesets-action@29038f2...) that includes updated parsing for Changesets CLI v3 output.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Point alpha/rc at the shared-config fork that parses v3 publish output so snapshot PR comments list packages again until the-guild-org/shared-config#755 lands on v1.
Summary
@changesets/cliv3, because the pinned snapshot action only parses the old publish stdout formats.release-snapshot.ymltoardatan/changesets-action@29038f2(same fix as the-guild-org/changesets-snapshot-action#3).v1so repos usingrelease-snapshot.yml@v1(e.g. graphql-tools) pick it up on merge.the-guild-org/changesets-snapshot-action@<merge-sha>.Test plan
@changesets/cli≥ 3 (e.g. graphql-tools) and confirm the PR comment lists published packages.the-guild-org/changesets-snapshot-actionpin.