Skip to content

chore: sync published workspace versions#211

Merged
sirdeggen merged 1 commit into
mainfrom
automation/sync-published-versions
Jun 19, 2026
Merged

chore: sync published workspace versions#211
sirdeggen merged 1 commit into
mainfrom
automation/sync-published-versions

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Updates workspace package references, pnpm-lock.yaml, and infra/*/package-lock.json after a successful npm publish.

@socket-security

Copy link
Copy Markdown

@socket-security

Copy link
Copy Markdown

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
Obfuscated code: npm better-sqlite3 is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: infra/uhrp-server-cloud-bucket/package-lock.jsonnpm/@bsv/wallet-toolbox@2.1.30npm/better-sqlite3@12.11.1

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/better-sqlite3@12.11.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

@sirdeggen sirdeggen merged commit 30c6d6f into main Jun 19, 2026
10 checks passed
@sonarqubecloud

Copy link
Copy Markdown

@codecov

codecov Bot commented Jun 19, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

ty-everett pushed a commit to ty-everett/ts-stack that referenced this pull request Jun 22, 2026
….json

The release sync PR (bsv-blockchain#211) refreshed this lockfile with --legacy-peer-deps
while it still carried the old eslint@10 stack; bsv-blockchain#212 then removed eslint
from package.json. The merge left package.json (no eslint) against a
lockfile still pinning eslint@10.4.1, so the Docker `npm ci --omit=dev`
failed with "package.json and package-lock.json are not in sync".

Regenerate the lockfile from the current (eslint-free) package.json so
ts-standard's own bundled eslint resolves and npm ci passes.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.

1 participant