Pin dependency versions to lockfile values#1435
Merged
JamieMagee merged 1 commit intomasterfrom Jan 26, 2026
Merged
Conversation
Replaces semver ranges (^, ~) with exact versions from package-lock.json. Dependabot handles updates, so pinning prevents unexpected version drift when npm install runs instead of npm ci. Closes #1434
There was a problem hiding this comment.
Pull request overview
This PR pins all npm dependency and devDependency versions in package.json to the exact versions currently recorded in package-lock.json to avoid unreviewed version drift when using npm install. This makes dependency updates fully Dependabot-driven and reviewable.
Changes:
- Replaced semver ranges (
^,~) for runtime dependencies with exact version numbers. - Replaced semver ranges for devDependencies with exact version numbers.
- Left GitHub-based dependency references unchanged.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
qtomlinson
approved these changes
Jan 26, 2026
qtomlinson
added a commit
to qtomlinson/crawler
that referenced
this pull request
Apr 6, 2026
Replace all semver ranges (^ and ~) in package.json with exact versions resolved from package-lock.json, including the lzma-native override. This ensures unreviewed dependency drift cannot occur when npm install is used instead of npm ci — all version updates will go through Dependabot-driven, reviewed PRs. The root package entry in package-lock.json now reflects the exact pinned versions from package.json, including updates like debug 4.4.3, extend 3.0.2, and winston 3.19.0. Similar to clearlydefined/service#1435.
qtomlinson
added a commit
to qtomlinson/crawler
that referenced
this pull request
Apr 6, 2026
Replace all semver ranges (^ and ~) in package.json with exact versions resolved from package-lock.json, including the lzma-native override. This ensures unreviewed dependency drift cannot occur when npm install is used instead of npm ci — all version updates will go through Dependabot-driven, reviewed PRs. The root package entry in package-lock.json now reflects the exact pinned versions from package.json, including updates like debug 4.4.3, extend 3.0.2, and winston 3.19.0. Similar to clearlydefined/service#1435.
qtomlinson
added a commit
to qtomlinson/crawler
that referenced
this pull request
Apr 6, 2026
Replace all semver ranges (^ and ~) in package.json with exact versions resolved from package-lock.json, including the lzma-native override. This ensures unreviewed dependency drift cannot occur when npm install is used instead of npm ci — all version updates will go through Dependabot-driven, reviewed PRs. The root package entry in package-lock.json now reflects the exact pinned versions from package.json, including updates like debug 4.4.3, extend 3.0.2, and winston 3.19.0. Similar to clearlydefined/service#1435.
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.
Replaces semver ranges (
^,~) in package.json with exact versions from package-lock.json.Why?
Running
npm installinstead ofnpm cican pull in newer versions that satisfy the range. This happens when the lock file gets deleted, regenerated, or when someone troubleshoots by clearing node_modules.Since Dependabot handles weekly updates, pinning versions means every dependency change goes through a reviewed PR rather than happening silently.
Changes
github:clearlydefined/spdx#v0.1.10)Closes #1434