Update all Yarn dependencies (2026-02-05)

[depfu]

This is your weekly update of all Yarn dependencies. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ @getalby/lightning-tools (6.0.0 → 6.1.0, minor) · Repo · Release · Diff

✳️ vite (7.2.7 → 7.3.1, minor) · Repo · Changelog · Release · Diff

✳️ lit (3.3.1 → 3.3.2, patch) · Repo · Changelog

---

Depfu will only send you the next scheduled PR once you merge or close this one.

All Depfu comment commands

@​depfu refresh

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	vite@​7.2.7 ⏵ 7.3.1			+1	+1
	@​getalby/​lightning-tools@​5.1.2 ⏵ 6.1.0	+6		+1	-1
	lit@​3.3.1 ⏵ 3.3.2	+1

View full report

[socket-security]

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		Obfuscated code: npm safer-buffer is 94.0% likely obfuscated Confidence: 0.94 Location: Package overview From: ? → npm/@open-wc/testing@3.2.2 → npm/@web/test-runner@0.15.3 → npm/@web/test-runner-playwright@0.9.0 → npm/safer-buffer@2.1.2 ℹ 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/safer-buffer@2.1.2. 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