build(deps): bump @opentui/solid from 0.4.1 to 0.4.2

[dependabot]

Bumps @opentui/solid from 0.4.1 to 0.4.2.

Release notes

Sourced from @​opentui/solid's releases.

Release v0.4.2

What's Changed

• handle threaded output backpressure + stale fps by @​kommander in anomalyco/opentui#1169
• fix(solid): share catalogue across entry points by @​simonklee in anomalyco/opentui#1171
• terminal: probe OSC 52 clipboard support by @​simonklee in anomalyco/opentui#1168
• clipboard: fix OSC 52 target handling by @​simonklee in anomalyco/opentui#1182
• fix: scroll position and selection by @​simonklee in anomalyco/opentui#1188

Full Changelog: anomalyco/opentui@v0.4.1...v0.4.2

Commits

• 3e2d0aa Release v0.4.2
• fb6c5ca fix(solid): share catalogue across entry points (#1171)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

---

^{Need help on this PR? Tag /codesmith with what you need. Autofix is disabled.}

---

Summary by cubic

Upgrade @opentui/solid to 0.4.2 to bring stability fixes (OSC 52 clipboard, scroll/selection) and better output backpressure handling. Updates the dependency range in packages/opencode and refreshes the lockfile (pulls in @opentui/core 0.4.2).

• Dependencies
  • @opentui/solid: 0.4.1 → 0.4.2; range set to >=0.4.2.
  • Transitive update: @opentui/core to 0.4.2 in bun.lock.

^{Written for commit 84c00c9. Summary will update on new commits.}

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​opentui/​core@​0.4.1 ⏵ 0.4.2			+1
	@​opentui/​solid@​0.4.1 ⏵ 0.4.2

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 @opentui/core is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: packages/opencode/package.json → npm/@opentui/core@0.4.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/@opentui/core@0.4.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