Skip to content

build: Update package-lock.json#1213

Merged
d3xter666 merged 1 commit intomainfrom
fix-package-lock
Nov 24, 2025
Merged

build: Update package-lock.json#1213
d3xter666 merged 1 commit intomainfrom
fix-package-lock

Conversation

@d3xter666
Copy link
Copy Markdown
Member

We have hit the following npm issue: npm/cli#4828

Recreating the package-lock.json should fix that

@d3xter666
Copy link
Copy Markdown
Member Author

I have tested the solution on a fork on my account: https://github.com/d3xter666/cli/actions/runs/19635367626 and it seems to work well now.

I'd appreciate any better ideas

@d3xter666 d3xter666 requested a review from a team November 24, 2025 13:19
@coveralls
Copy link
Copy Markdown

Coverage Status

coverage: 94.657%. remained the same
when pulling 06e13e2 on fix-package-lock
into e5c236d on main.

Copy link
Copy Markdown
Member

@matz3 matz3 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please rather use build as this is not fixing an issue on consumer side.

@d3xter666 d3xter666 changed the title fix: Update package-lock.json build: Update package-lock.json Nov 24, 2025
@d3xter666 d3xter666 merged commit 6bca498 into main Nov 24, 2025
30 checks passed
@d3xter666 d3xter666 deleted the fix-package-lock branch November 24, 2025 13:56
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.

3 participants