Skip to content

chore(deps): update#10

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

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

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Mar 1, 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: (UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, on day 1 of the month (* 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 enabled auto-merge (squash) March 1, 2026 01:05
@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Mar 1, 2026

⚠️ No Changeset found

Latest commit: 491d77d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link
Copy Markdown

@ellipsis-dev ellipsis-dev Bot left a comment

Choose a reason for hiding this comment

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

Skipped PR review on a7c1f1c because no changed files had a supported extension. If you think this was in error, please contact us and we'll fix it right away.

@socket-security
Copy link
Copy Markdown

socket-security Bot commented Mar 1, 2026

@socket-security
Copy link
Copy Markdown

socket-security Bot commented Mar 1, 2026

All alerts resolved. Learn more about Socket for GitHub.

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

View full report

@pkg-pr-new
Copy link
Copy Markdown

pkg-pr-new Bot commented Mar 1, 2026

Open in StackBlitz

npm i https://pkg.pr.new/mini-shiki@10

commit: 491d77d

@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch 3 times, most recently from 2b7919c to 6efd12b Compare March 9, 2026 02:26
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 6efd12b to fbe3883 Compare March 13, 2026 15:43
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from fbe3883 to b50e3fe Compare April 1, 2026 18:09
@codacy-production
Copy link
Copy Markdown

codacy-production Bot commented Apr 1, 2026

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.

@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from b50e3fe to f231b9a Compare April 15, 2026 18:27
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from f231b9a to 0d45d83 Compare April 29, 2026 15:04
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from 1a0d499 to 08618eb Compare May 18, 2026 10:09
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 08618eb to 491d77d Compare May 20, 2026 03:46
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