fix(changesets): migration v2 -> v3 - #6859
Conversation
|
dd4b16d to
d7d5d97
Compare
| cache: 'pnpm' | ||
| - run: pnpm install --frozen-lockfile && pnpm build && pnpm install --frozen-lockfile | ||
| - name: Run changesets-renovate | ||
| run: pnpm dlx @scaleway/changesets-renovate |
There was a problem hiding this comment.
install the right version as the latest should not work with changeset v2.
NB: The latest version use changeset cli v3.
d7d5d97 to
443c930
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #6859 +/- ##
=======================================
Coverage 90.97% 90.97%
=======================================
Files 571 571
Lines 10515 10515
Branches 3787 3787
=======================================
Hits 9566 9566
Misses 949 949 Continue to review full report in Codecov by Harness.
🚀 New features to boost your workflow:
|
Signed-off-by: Alexandre Philibeaux <aphilibeaux@scaleway.com>
443c930 to
6c7069b
Compare
Summary
Upgrades the repository from Changesets v2 to v3 following the official migration guide.
Changes
package.json: bumped@changesets/cli2.31.1→3.0.1and@changesets/changelog-github0.7.0→1.0.0.changeset/config.json: updated$schemato@changesets/config@4.0.0. The rest of the config was already v3-compatible (access: "public",baseBranch: "main",privatePackagesobject form, noprettieroption to migrate).github/workflows/release.yml: bumpedchangesets/actionv1.9.0→v2.1.1and renamed inputs:commit→commit-messagetitle→pr-titlepublish→publish-scriptpnpm-lock.yaml: regenerated