Repository navigation
chore: configure changesets for releases - #2
Merged
Merged
Conversation
Add @changesets/cli with a .changeset config targeting `main`, a release workflow that opens a Version Packages PR or publishes to npm, and a major changeset for the async public API. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Bump @changesets/cli from ^2.31.1 to ^3.0.3 and regenerate the lock file. Align the .changeset config schema with the bundled @changesets/config@4.0.1. Verified: `changeset status` reports the pending major bump and `changeset version` bumps 2.2.5 -> 3.0.0 with a generated CHANGELOG. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Regenerate package-lock.json with in-range transitive updates (132 version bumps, mostly @babel/* 7.28 -> 7.29) plus deduping of nested picomatch/yaml/cac copies. No package.json changes. Verified: `npm run build` and `npm test` (86 passed) succeed. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
npm 11 omits vite's optional peer dependency (terser) from the lock file, but npm 10 — shipped with the Node 18/20/22 CI matrix — requires these entries. This made `npm ci` fail with EUSAGE: 'Missing: terser@5.51.2 from lock file'. Regenerated with npm@10.8.2 (the version CI uses), which restores terser@5.51.2, acorn@8.19.0 and @jridgewell/source-map@0.3.11 as optional peer entries. Purely additive: 70 insertions, 0 deletions. Verified locally with npm 10: `npm ci`, `npm test` (86 passed), `npm run build` and `node benchmark.js` all succeed. `npm ci --dry-run` also passes under npm 11. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@changesets/cli@3 requires Node `^22.11 || ^24 || >=26` and npm >= 10.9.0, which produced ~17 EBADENGINE warnings on the Node 18.x/20.x CI jobs since this package supports Node >= 16. Version 2 declares no engines, matches the eridu-tech-core reference and keeps CI output clean. Realign the .changeset config schema with @changesets/config@3.1.4, the version bundled with CLI v2. Verified with npm 10 (CI's version): `npm ci`, `npm test` (86 passed), `npm run build` and `node benchmark.js` all succeed. `changeset status` reports the pending major bump and `changeset version` bumps to 3.0.0 with a generated CHANGELOG. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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.
Add @changesets/cli with a .changeset config targeting
main, a release workflow that opens a Version Packages PR or publishes to npm, and a major changeset for the async public API.Co-authored-by: Copilot 223556219+Copilot@users.noreply.github.com