chore(deps)(deps-dev): bump @types/node from 20.19.39 to 20.19.40 (recovered from #57)#58
Merged
Conversation
Owner
Author
|
Note: this recovery PR is incomplete — the cherry-pick wrote Two paths to close out:
The systemic Hypatia red on this repo is being fixed separately by #59. |
hyperpolymath
added a commit
that referenced
this pull request
May 12, 2026
Fixes the lockfile drift left on `main` when #58 merged with only `package.json` updated. `npm install` regenerates `package-lock.json` cleanly; `@types/node` resolves to `20.19.41` (highest compatible with the new `^20.19.40` range). 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.
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.
Recovery cherry-pick of the bump from closed PR #57. The original PR was closed under the rationale that estate-wide CI failures dominated its red marks — that was correct about the failures being systemic, but closing the bump itself stranded the dependency update. Reapplying.
The systemic CI cause ( SHA no longer resolves) is being fixed separately; see hyperpolymath/proof-of-work#44 and hyperpolymath/affinescript-vite#9.
🤖 Recovered by Claude Code.