Repository navigation
fix(ci): migrate release workflow to Changesets v3 - #20
Merged
Merged
Conversation
|
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The Release workflow fails because
changesets/actionv2 requires Changesets CLI v3, while the repository still uses CLI v2 and the previous action interface.Upgrade
@changesets/clito^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-fundnpm run lintnpm run type-checknpm test— all 187 tests passed.npm run versiongenerated the HTML codemod changelog and synchronized its package and registry manifest to1.0.0, preserving the CSS and internal utilities versions.changeset git-tagcreated 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 || >=26and 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