chore(deps): regenerate package-lock.json after @types/node bump#60
Merged
Conversation
PR #58 (recovery cherry-pick of @types/node 20.19.39 → 20.19.40) wrote package.json but the Contents-API write for package-lock.json was lost, so main landed in a drifted state. up to date, audited 378 packages in 2s 63 packages are looking for funding run `npm fund` for details 6 high severity vulnerabilities To address issues that do not require attention, run: npm audit fix To address all issues (including breaking changes), run: npm audit fix --force Run `npm audit` for details. regenerates the lockfile cleanly; @types/node resolves to 20.19.41 (latest compatible with ^20.19.40).
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
1 participant
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.
Fixes the lockfile drift left on
mainwhen #58 merged with onlypackage.jsonupdated.npm installregeneratespackage-lock.jsoncleanly;@types/noderesolves to20.19.41(highest compatible with the new^20.19.40range).Follow-up to the cherry-pick recovery flagged in #58 — the Contents-API write for the lockfile failed during the recovery, so the merge landed in a drifted state until now.