Skip to content

fix(ci): remove package-lock.json to fix release-please crash#108

Merged
webdevcom01-cell merged 1 commit into
mainfrom
fix/release-please-lockfile-crash
May 21, 2026
Merged

fix(ci): remove package-lock.json to fix release-please crash#108
webdevcom01-cell merged 1 commit into
mainfrom
fix/release-please-lockfile-crash

Conversation

@webdevcom01-cell
Copy link
Copy Markdown
Owner

Problem

Release workflow fails on every push to main:

##[error]release-please failed: Cannot set properties of undefined (setting 'version')

Root cause: release-please v17 (node strategy) fetches package-lock.json and tries to update the packages[""].version field when bumping versions. This project uses pnpmpackage-lock.json is a stale npm artifact that doesn't have the structure release-please expects.

Fix

  • git rm package-lock.json — removes the stale lockfile
  • Added package-lock.json to .gitignore so it can't re-appear

pnpm-lock.yaml remains the canonical lockfile, untouched.

Test plan

  • After merge: Release workflow on main completes without Cannot set properties of undefined error
  • pnpm install still works (pnpm-lock.yaml unaffected)
  • CI (typecheck + vitest) passes

release-please v17 tries to update package-lock.json when bumping
versions but crashes with 'Cannot set properties of undefined
(setting version)' because this pnpm project's lockfile format
differs from what the node strategy expects.

Removing the stale npm lockfile and ignoring it going forward.
pnpm-lock.yaml remains the canonical lockfile.
@webdevcom01-cell webdevcom01-cell merged commit 7bc73fc into main May 21, 2026
@webdevcom01-cell webdevcom01-cell deleted the fix/release-please-lockfile-crash branch May 22, 2026 13:41
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