Skip to content

ci: publish with changesets/action v2 so releases get tags again - #25

Merged
ru44 merged 1 commit into
masterfrom
ci/changesets-action-v2
Oct 10, 2026
Merged

ru44 merged 1 commit into
masterfrom
ci/changesets-action-v2

Conversation

@ru44

@ru44 ru44 commented Oct 10, 2026 •

Copy link
Copy Markdown
Member

Why

cliuno@2.2.0 reached npm, but the Publish run never pushed a v2.2.0 tag or opened a GitHub release.

I created the v2.2.0 tag and release by hand, on the Version Packages commit 242dc80.

Change

  • Moved to changesets/action@v2, the release line built for CLI v3. It reads what was published from the CHANGESETS_OUTPUT file, which changeset publish inside scripts/ci-publish.sh writes because the script inherits the env.
  • v2 switched its inputs to kebab-case and stopped reading the GITHUB_TOKEN env var:
    • version → version-script
    • publish → publish-script
    • The env block is gone, since github-token defaults to the workflow token.
  • Unchanged: npm OIDC trusted publishing, the ci-publish.sh guard against re-publishing, and the Version Packages PR flow.

Testing

  • actionlint passes on publish.yml and main.yml.
  • The tag and release path only runs on a real publish, so the next release is the end-to-end check. Pushes with nothing to release still exit early in ci-publish.sh. v2 allows a custom publish script that writes no output file and only logs a warning.

Summary by CodeRabbit

  • Chores
    • Updated the automated release process to follow the current versioning and publishing workflow. The process also continues to identify which packages are published, helping keep package releases consistent with the repository’s release configuration. These changes affect release operations rather than features or behavior available in the product.

@changesets/cli v3 no longer prints the "New tag:" lines that changesets/action v1
parsed, so the 2.2.0 run published to npm but skipped the git tag and GitHub
release (both were created by hand afterwards). Action v2 reads the
CHANGESETS_OUTPUT file instead and renames the inputs to version-script,
publish-script and github-token (which defaults to the workflow token).
@coderabbitai

coderabbitai Bot commented Oct 10, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration
  • Configuration used: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: a4dde6df-2521-4ec3-86e8-da98483597d2

📥 Commits

Reviewing files that changed from the base of the PR and between 242dc80 and aac9fb9.


📒 Files selected for processing (1)
  • .github/workflows/publish.yml

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.



📝 Walkthrough

Walkthrough

The publish workflow now uses changesets/action@v2 with script inputs. It removes the explicit GITHUB_TOKEN environment entry and updates comments about release behavior and the CHANGESETS_OUTPUT file.

Changes

Publish workflow

Layer / File(s) Summary
Changesets publish step
.github/workflows/publish.yml
The step uses version-script and publish-script instead of the v1 inputs. It removes the explicit token environment entry and updates comments about release behavior and published-package output.

Priority: ➖ Normal

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Bug fix


Merge Risk: ⚪ Minimal · up to aac9f

The publish workflow’s script handoff and token permissions match the v2 action contract. No material merge-blocking risk is established.

Pre-merge checks | Passed 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check Passed The title clearly identifies the main change: migrating the publishing workflow to changesets/action v2 to restore release tags.
Docstring Coverage Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR

  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@ru44
ru44 merged commit e900f0d into master Oct 10, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant