Skip to content

fix(ci): migrate release workflow to Changesets v3 - #20

Merged
bjohansebas merged 1 commit into
mainfrom
fix/changesets-v3-release
Nov 8, 2026
Merged

bjohansebas merged 1 commit into
mainfrom
fix/changesets-v3-release

Conversation

@bjohansebas

@bjohansebas bjohansebas commented Nov 8, 2026 •

Copy link
Copy Markdown
Member

Summary

The Release workflow fails because changesets/action v2 requires Changesets CLI v3, while the repository still uses CLI v2 and the previous action interface.

Upgrade @changesets/cli to ^3.0.3, update its configuration schema and lockfile, and migrate the workflow inputs, package output, and tagging command to the v3-compatible interface. This restores changelog generation and passes tagged packages to the Codemod Registry publishing job.

What kind of change does this PR introduce?

CI fix.

Did you add tests for your changes?

No new automated tests were added for this release tooling update. Validation passed:

  • npm ci --no-audit --no-fund
  • npm run lint
  • npm run type-check
  • npm test — all 187 tests passed.
  • In an isolated clone, npm run version generated the HTML codemod changelog and synchronized its package and registry manifest to 1.0.0, preserving the CSS and internal utilities versions.
  • changeset git-tag created the expected HTML tag and structured event consumed by action v2. A second run produced no duplicate tags or publication events.

The Release workflow itself runs on pushes to main.

Does this PR introduce a breaking change?

No changes to codemod behavior or public APIs. Contributor tooling now requires Node.js ^22.11 || ^24 || >=26 and npm >=10.9.0; CI already uses a supported LTS version.

If relevant, what needs to be documented once your changes are merged or what have you already documented?

No additional documentation is needed. The Changesets configuration and release workflow are updated together.

Use of AI

Codex assisted with diagnosing the failed workflow, updating the dependency and workflow configuration, running the validations above, and drafting this description.

Summary by CodeRabbit

  • Chores
    • Updated release configuration and automation to use the current publishing workflow, including its package publication outputs and authentication settings.
    • These changes affect how releases are prepared and published; they do not change the features available in the product or the end-user experience.

@changeset-bot

changeset-bot Bot commented Nov 8, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: db1c852

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@socket-security

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updated@​changesets/​cli@​2.31.1 ⏵ 3.0.399 +210074 -2591 -3100

View full report

@bjohansebas
bjohansebas merged commit a0ea678 into main Nov 8, 2026
10 checks passed
@bjohansebas
bjohansebas deleted the fix/changesets-v3-release branch November 8, 2026 15:17
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