fix(deps): update dependency @vercel/stega to v1

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@​vercel/stega	0.1.2 → 1.1.0

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "before 3am on the first day of the month"
• 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 has been generated by Mend Renovate using a curated preset maintained by . View repository job log here

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​@​vercel/​stega@​1.1.0
	npm/​@​types/​react@​19.2.17
	npm/​isbot@​5.2.1

View full report

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
preview-kit-next-app-router	Ready	Preview, Comment	Jul 21, 2026 12:55am
preview-kit-next-pages-router	Ready	Preview, Comment	Jul 21, 2026 12:55am
preview-kit-remix	Ready	Preview, Comment	Jul 21, 2026 12:55am
preview-kit-test-studio	Ready	Preview, Comment	Jul 21, 2026 12:55am

[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 @vercel/stega is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: packages/preview-kit/package.json → npm/@vercel/[email protected] ℹ 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 [email protected]. 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/@vercel/[email protected]. 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