Skip to content

chore(deps): update dependency solid-refresh to v0.7.8#256

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/solid-refresh-0.x-lockfile
Open

chore(deps): update dependency solid-refresh to v0.7.8#256
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/solid-refresh-0.x-lockfile

Conversation

@renovate

@renovate renovate Bot commented Feb 27, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
solid-refresh 0.7.50.7.8 age confidence

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • 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 added the renovate label Feb 27, 2026
@bolt-new-by-stackblitz

Copy link
Copy Markdown

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

@socket-security

socket-security Bot commented Feb 27, 2026

Copy link
Copy Markdown

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

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Addedsolid-refresh@​0.7.810010010085100

View full report

@renovate renovate Bot force-pushed the renovate/solid-refresh-0.x-lockfile branch from eb5920e to b3ae45c Compare March 3, 2026 20:55
@renovate renovate Bot changed the title chore(deps): update dependency solid-refresh to v0.7.6 chore(deps): update dependency solid-refresh to v0.7.7 Mar 3, 2026
@renovate renovate Bot force-pushed the renovate/solid-refresh-0.x-lockfile branch from b3ae45c to 9233172 Compare March 4, 2026 20:37
@renovate renovate Bot changed the title chore(deps): update dependency solid-refresh to v0.7.7 chore(deps): update dependency solid-refresh to v0.7.8 Mar 4, 2026
@renovate renovate Bot force-pushed the renovate/solid-refresh-0.x-lockfile branch from 9233172 to 29a1f0b Compare March 5, 2026 15:03
@renovate renovate Bot force-pushed the renovate/solid-refresh-0.x-lockfile branch from 29a1f0b to 98f67aa Compare March 13, 2026 10:38
@renovate renovate Bot force-pushed the renovate/solid-refresh-0.x-lockfile branch from 98f67aa to 692d770 Compare April 1, 2026 16:44
@renovate renovate Bot force-pushed the renovate/solid-refresh-0.x-lockfile branch from 692d770 to cbcd9a4 Compare April 8, 2026 16:48
@renovate renovate Bot force-pushed the renovate/solid-refresh-0.x-lockfile branch from cbcd9a4 to 95cafb1 Compare April 29, 2026 12:14
@renovate renovate Bot force-pushed the renovate/solid-refresh-0.x-lockfile branch 2 times, most recently from 3738d6c to 2cbb46a Compare May 18, 2026 15:07
@renovate renovate Bot force-pushed the renovate/solid-refresh-0.x-lockfile branch from 2cbb46a to 090fccd Compare May 28, 2026 18:16
@renovate renovate Bot force-pushed the renovate/solid-refresh-0.x-lockfile branch from 090fccd to 65e1bb1 Compare June 11, 2026 18:06
@renovate renovate Bot force-pushed the renovate/solid-refresh-0.x-lockfile branch from 65e1bb1 to 9f0460b Compare July 12, 2026 15:36
@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 @emnapi/runtime is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: pnpm-lock.yamlnpm/tsdown@0.14.2npm/@sxzz/test-utils@0.5.13npm/@emnapi/runtime@1.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/@emnapi/runtime@1.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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants