Skip to content

chore(deps): lock file maintenance#2646

Merged
renovate[bot] merged 1 commit intomainfrom
renovate/lock-file-maintenance
Mar 27, 2026
Merged

chore(deps): lock file maintenance#2646
renovate[bot] merged 1 commit intomainfrom
renovate/lock-file-maintenance

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Mar 26, 2026

This PR contains the following updates:

Update Change
lockFileMaintenance All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.


Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, on day 1 of the month ( * 0-3 1 * * ) in timezone America/Vancouver, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.


Thanks for the PR!

Deployments, as required, will be available below:

Please create PRs in draft mode. Mark as ready to enable:

After merge, new images are deployed in:

@renovate renovate bot enabled auto-merge (squash) March 26, 2026 16:02
@github-project-automation github-project-automation bot moved this from New to Waiting in DevOps (NR) Mar 26, 2026
@socket-security
Copy link
Copy Markdown

socket-security bot commented Mar 26, 2026

@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 3 times, most recently from 2e5b1e4 to 2f12240 Compare March 27, 2026 12:46
@socket-security
Copy link
Copy Markdown

socket-security bot commented Mar 27, 2026

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 @electric-sql/pglite is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: backend/package-lock.jsonnpm/prisma@7.6.0npm/@electric-sql/pglite@0.4.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/@electric-sql/pglite@0.4.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.

Warn High
Obfuscated code: npm vite is 91.0% likely obfuscated

Confidence: 0.91

Location: Package overview

From: backend/package-lock.jsonnpm/vitest@4.1.2npm/vite@8.0.3

ℹ 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/vite@8.0.3. 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

@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from 2f12240 to feeaf30 Compare March 27, 2026 18:05
@renovate renovate bot merged commit c96a18b into main Mar 27, 2026
24 of 27 checks passed
@renovate renovate bot deleted the renovate/lock-file-maintenance branch March 27, 2026 18:16
@github-project-automation github-project-automation bot moved this from Waiting to Done in DevOps (NR) Mar 27, 2026
DerekRoberts added a commit that referenced this pull request Apr 1, 2026
PR #2646 lock file maintenance updated hono to 4.12.9 in the lock file,
but the overrides in package.json pinned hono@<4.11.7 to 4.11.7, causing
npm ci to fail with a version mismatch. Regenerating the lock file resolves
the inconsistency.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

0 participants