chore(ops): regenerate package-lock.json#200
Merged
Merged
Conversation
github-actions
Bot
added
dependencies
Contributor
Author
Coverage Report
File CoverageNo changed files found. |
github-actions
Bot
force-pushed
the
ops/regenerate-lockfile
branch
from
7456149 to
d610dd1
Compare
github-actions
Bot
force-pushed
the
ops/regenerate-lockfile
branch
from
d610dd1 to
829a337
Compare
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.
🛠️ Automated Lockfile Regeneration
This PR was triggered manually via the Ops | Regenerate Lockfile workflow.
What changed?
package-lock.jsonwas deleted and cleanly regenerated using Node 20 / npm v10+.lockfileVersionto match the latest standard format (v3).Please verify that your CI tests pass before merging!