Skip to content

chore: remove unused pnpm-lock.yaml#87

Merged
RobThePCGuy merged 2 commits into
mainfrom
chore/drop-unused-pnpm-lock
Jul 25, 2026
Merged

chore: remove unused pnpm-lock.yaml#87
RobThePCGuy merged 2 commits into
mainfrom
chore/drop-unused-pnpm-lock

Conversation

@RobThePCGuy

Copy link
Copy Markdown
Owner

This repo had two lockfiles at root. CI runs npm ci with cache: npm, so pnpm-lock.yaml was never used to build anything — but Dependabot scanned it anyway.

It had drifted badly behind the lockfile we actually use:

package package-lock.json pnpm-lock.yaml
hono 4.12.25 4.12.19
dompurify 3.4.12 3.2.7

That accounted for 47 of 60 open Dependabot alerts — all against a file nothing builds from, for versions already patched in package-lock.json.

Also adds pnpm-lock.yaml and yarn.lock to .gitignore so a stray pnpm install cannot re-create the problem.

verify passing on this PR is the proof nothing depended on the removed file.

CI installs with `npm ci` and caches npm; nothing in this repo builds
from pnpm. The pnpm lockfile had drifted well behind package-lock.json
(hono 4.12.19 vs 4.12.25, dompurify 3.2.7 vs 3.4.12) and was the source
of 47 stale Dependabot alerts against dependencies that were already
patched in the lockfile we actually use.
Guards against pnpm-lock.yaml/yarn.lock reappearing and re-creating the
duplicate-alert problem.
@gemini-code-assist

Copy link
Copy Markdown
Contributor

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

@RobThePCGuy
RobThePCGuy merged commit 2d09288 into main Jul 25, 2026
4 checks passed
@RobThePCGuy
RobThePCGuy deleted the chore/drop-unused-pnpm-lock branch July 25, 2026 03:51
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