* Initial plan
* Initial plan
Co-authored-by: canisminor1990 <[email protected]>
* fix: add legacy-peer-deps=true to prevent npm version crash in release:static
The `@semantic-release/npm` prepare step runs `npm version` which triggers
arborist peer dependency resolution. In CI with npm 10.x, this crashes with
"Cannot read properties of null (reading 'matches')" because peer dependency
nodes are missing from the bun-managed node_modules.
Adding `legacy-peer-deps=true` tells npm to use the legacy peer dependency
resolution algorithm which gracefully handles missing peer dependencies.
Co-authored-by: canisminor1990 <[email protected]>
---------
Co-authored-by: canisminor1990 <[email protected]>
Co-authored-by: Hanzo Dev <[email protected]>
* Initial plan
* fix: add setup-node to release workflow and package-lock=false to .npmrc
The `release:static` step fails because `@semantic-release/npm` runs
`npm version` which triggers dependency resolution. On the CI runner's
npm 10.x, this hits a known bug: "Cannot read properties of null
(reading 'matches')".
Two fixes:
1. Add `actions/setup-node@v4` with node-version 22 to the release
workflow, ensuring npm >= 10.8+ (past the bug fix) is available.
2. Add `package-lock=false` to .npmrc to prevent npm from attempting
lockfile operations (the project uses bun, not npm).
Co-authored-by: canisminor1990 <[email protected]>
---------
Co-authored-by: canisminor1990 <[email protected]>
Co-authored-by: Hanzo Dev <[email protected]>
