Skip to content

chore(deps): lock file maintenance#517

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/lock-file-maintenance
Open

chore(deps): lock file maintenance#517
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/lock-file-maintenance

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Dec 29, 2025

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: (UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
  • 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.

@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from a444ab5 to d6e302c Compare January 8, 2026 19:34
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from 3a9502a to ed79b2a Compare January 23, 2026 17:11
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from ed79b2a to c95c0bf Compare February 2, 2026 19:08
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from 57edd48 to 26c670e Compare February 17, 2026 17:33
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 26c670e to 0c166df Compare March 5, 2026 20:13
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 0c166df to cc424c0 Compare March 14, 2026 22:13
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from 26c02d1 to b17fec8 Compare April 1, 2026 19:31
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from b17fec8 to 4cdc306 Compare April 8, 2026 18:01
@socket-security
Copy link
Copy Markdown

socket-security Bot commented Apr 8, 2026

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updatedlodash-es@​4.17.22 ⏵ 4.18.1100100 +1979 +187100

View full report

@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 4cdc306 to cde655b Compare April 29, 2026 16:31
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from cde655b to 29b394f Compare May 12, 2026 13:07
@socket-security
Copy link
Copy Markdown

socket-security Bot commented May 12, 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 js-yaml is 85.0% likely obfuscated

Confidence: 0.85

Location: Package overview

From: package-lock.jsonnpm/semantic-release@25.0.2npm/js-yaml@4.2.0

ℹ 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/js-yaml@4.2.0. 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 29b394f to d004aab Compare May 18, 2026 10:33
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from d004aab to 8cbea58 Compare May 28, 2026 16:31
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 8cbea58 to 511b3d2 Compare June 1, 2026 20:09
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.

0 participants