build(deps): bump @opentui/core from 0.3.0 to 0.3.1

[dependabot]

Bumps @opentui/core from 0.3.0 to 0.3.1.

Release notes

Sourced from @​opentui/core's releases.

Release v0.3.1

What's Changed

• feat(core): renderer: add split-footer replay reset by @​simonklee in anomalyco/opentui#1130

Full Changelog: anomalyco/opentui@v0.3.0...v0.3.1

Commits

• 2d4de31 Release v0.3.1
• 20fa223 feat(core): renderer: add split-footer replay reset (#1130)
• 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/core to 0.3.1 to pick up the renderer split-footer replay reset. No app code changes.

• Dependencies
  • packages/opencode/package.json: raise @opentui/core from >=0.1.92 to >=0.3.1.
  • Update bun.lock to resolve @opentui/core@0.3.1 and platform binaries.

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

Greptile Summary

This Dependabot PR bumps @opentui/core from 0.3.0 to 0.3.1 (a patch release adding split-footer replay reset) and tightens the minimum version requirement in packages/opencode/package.json from >=0.1.92 to >=0.3.1.

• The top-level @opentui/core is updated to 0.3.1 along with all platform-specific optional binaries.
• @opentui/solid still declares @opentui/core@0.3.0 as its peer dependency, causing bun to resolve a second, nested copy of @opentui/core@0.3.0 under @opentui/solid, as reflected in the new lock file entries.

Confidence Score: 4/5

Safe to merge if @opentui/solid and @opentui/core do not share singleton instances across module boundaries; the dual-version resolution in bun is the main risk.

The core change is a straightforward patch bump. The main concern is that bun now bundles two different versions of @opentui/core — 0.3.1 for the app and 0.3.0 for @opentui/solid — because @opentui/solid's peer dep still pins 0.3.0. If the TUI library relies on a shared module instance (renderer singleton, layout tree), the split could cause subtle runtime breakage; if the packages are stateless utilities, it will be harmless.

bun.lock — specifically the newly added @opentui/solid/@opentui/core nested entries that introduce the dual-version resolution.

Important Files Changed

Filename	Overview
packages/opencode/package.json	Tightens @opentui/core minimum version from >=0.1.92 to >=0.3.1; @opentui/solid version constraint is unchanged and still resolves to 0.3.0 (a different instance)
bun.lock	Bumps @opentui/core to 0.3.1 and all platform binaries accordingly; adds nested @opentui/solid/@opentui/core at 0.3.0 to satisfy solid's peer dep, resulting in two versions of @opentui/core in the graph

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["packages/opencode\n(@cortexkit/opencode-anthropic-auth)"]
    A -->|">=0.3.1"| B["@opentui/core@0.3.1\n(top-level resolution)"]
    A -->|">=0.1.92"| C["@opentui/solid@0.3.0"]
    C -->|"peer: 0.3.0\n(nested resolution)"| D["@opentui/core@0.3.0\n(@opentui/solid/@opentui/core)"]
    style D fill:#f9c74f,stroke:#f3722c
    style B fill:#90be6d,stroke:#577590

Loading

_{Reviews (1): Last reviewed commit: "build(deps): bump @opentui/core from 0.3..." | Re-trigger Greptile}

Greptile also left 1 inline comment on this PR.

[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.3.1

View full report

[greptile-apps]

Dual @opentui/core versions resolved at runtime

After this bump, bun resolves two distinct copies of @opentui/core: 0.3.1 at the top level and 0.3.0 nested under @opentui/solid. If @opentui/solid shares state or singleton objects (e.g., a renderer instance, layout engine, or event bus) with the top-level @opentui/core, the two separate module instances will not share that state, potentially causing subtle rendering or layout bugs. Consider also bumping @opentui/solid to a version whose peer dep allows >=0.3.1, which would collapse the graph back to a single instance.

[ualtinok]

Closed as superseded by the combined dependency update in f5876fa, which applies these bumps together to avoid bun.lock conflicts.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.