fix(ci): sync package-lock.json with package.json (unblock smoke npm ci) #17

2026-06-13T06:18:22Z

peptiderepo commented

2026-06-13 06:18:22 +00:00

(Migrated from github.com)

What changed

Regenerated package-lock.json using npm install --package-lock-only. No source files, configuration files, or package versions were touched.

Versions resolved in the new lock:

Package	Old (lock)	New (lock)	package.json range
`@playwright/test`	1.59.1	1.60.0	`^1.60.0`
`playwright`	1.59.1	1.60.0	(transitive)
`playwright-core`	1.59.1	1.60.0	(transitive)
`typescript`	(missing)	6.0.3	`^6.0.3`

Why

npm ci requires an exact lock↔manifest match. The lock was pinning Playwright at 1.59.1 while package.json specifies ^1.60.0, and typescript was completely absent from the lock. This caused every npm ci invocation to abort with an integrity/sync error, blocking the smoke gate that guards all org-wide deploys.

Risk

Minimal. This is a lockfile-only change — no source code, no package.json edits, no version strategy changes. The resolved packages are identical to what package.json has always declared.

Test plan

npm ci --dry-run succeeds against the regenerated lock (verified locally before opening this PR)
git diff --stat shows only package-lock.json modified (1 file, +30/-14 lines)

## What changed Regenerated `package-lock.json` using `npm install --package-lock-only`. No source files, configuration files, or package versions were touched. **Versions resolved in the new lock:** | Package | Old (lock) | New (lock) | package.json range | |---|---|---|---| | `@playwright/test` | 1.59.1 | 1.60.0 | `^1.60.0` | | `playwright` | 1.59.1 | 1.60.0 | (transitive) | | `playwright-core` | 1.59.1 | 1.60.0 | (transitive) | | `typescript` | *(missing)* | 6.0.3 | `^6.0.3` | ## Why `npm ci` requires an exact lock↔manifest match. The lock was pinning Playwright at 1.59.1 while `package.json` specifies `^1.60.0`, and `typescript` was completely absent from the lock. This caused every `npm ci` invocation to abort with an integrity/sync error, blocking the smoke gate that guards all org-wide deploys. ## Risk **Minimal.** This is a lockfile-only change — no source code, no package.json edits, no version strategy changes. The resolved packages are identical to what package.json has always declared. ## Test plan - `npm ci --dry-run` succeeds against the regenerated lock (verified locally before opening this PR) - `git diff --stat` shows only `package-lock.json` modified (1 file, +30/-14 lines)

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: peptide-repo/peptide-e2e#17