Skip to content

chore(deps): bump the npm-tui-minor-patch group across 1 directory with 6 updates - #454

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/src/plugins/tui/npm-tui-minor-patch-9caeb01d52
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/src/plugins/tui/npm-tui-minor-patch-9caeb01d52

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

Bumps the npm-tui-minor-patch group with 6 updates in the /src/plugins/tui directory:

Package From To
@opencode/plugin 2.0.26 2.3.0
@opentui/core 0.5.17 0.8.4
@opentui/solid 0.5.17 0.8.4
solid-js 1.9.12 1.9.19
@profullstack/hqtui 0.11.1 0.12.0
tsdown 0.23.0 0.23.7

Updates @opencode/plugin from 2.0.26 to 2.3.0

Release notes

Sourced from @​opencode/plugin's releases.

v2.3.0

Highlights

  • Background Subagents by Default: Subagents now return immediately, continue in the background, and report back whenever they become idle. You can keep working in the parent session while multiple subagents run concurrently. (#63382)
  • Quieter Transcripts by Default: The TUI now summarizes each run of tool calls and thoughts into one collapsible activity row, so the answer is easier to follow. To see every step again, set Verbosity to medium or high in settings, or set session.verbosity in your TUI config; an existing setting is kept. (#63207)
  • Jump to an Earlier Prompt: In the desktop app, open Jump to message from the command palette or press Cmd+Alt+G (Ctrl+Alt+G on Windows and Linux) to search prompts across the current session and jump directly to one. (#63585)

Core

Improvements

  • Subagents now always run in the background, return their session ID immediately, and report results to their parent whenever they become idle. (#63382)
  • Added experimental support for MCP events, behind the mcp_events flag. (#63254, #63261, #63269)
  • Shell commands now survive server handoffs and keep their output when interrupted.
  • Added experimental support for moving a shell command to the background when its timeout expires, behind the shell_timeout_background flag. With the flag on, an explicit timeout on a background command stops it. (#63024, #63703)
  • Local Windows shell commands now run through the process daemon.
  • Added support for freeform tool input on compatible models.
  • Added LM Studio decision-model support.
  • Agents are now told when their session is a fork. Thanks @​hasta84. (#63235)
  • Tool output truncation now keeps the beginning of the output and preserves a usable preview if the full output cannot be saved.
  • Tail reads no longer load the entire file into memory.
  • Providers can present a client certificate for gateways that require mutual TLS. Set settings.tls with cert, key and an optional passphrase on the provider; values accept {file:} and {env:} like apiKey. (#61832)
  • When a subagent goes idle while its own background work is still running, its report to the parent now says it is still running, so the parent waits for the final report instead of treating the partial answer as done. (#63675)
  • Code Mode gets simpler structured results from file and skill tools: write and edit return their confirmation as a string, patch returns an empty result, and skill returns the skill's directory and content. (#63616, #63635, #63618, #63623)

Bug fixes

  • Fixed case-only file renames in patches on case-insensitive filesystems.
  • Fixed stale thinking being retained after Claude Agent prompts or tools change.
  • Fixed directly driven child sessions not resuming after a restart.
  • Fixed plugin replacement stopping when cleanup of an earlier plugin fails.
  • Fixed MCP OAuth refreshes and localhost redirects when a server rewrites 127.0.0.1.
  • Fixed saved API keys being omitted from local-model discovery.
  • Local model discovery (Ollama, LM Studio, vLLM) waits up to 15 seconds per request instead of 1, so remote or tunnelled endpoints list their models, and a slow endpoint no longer delays other endpoints or config reloads. (#63700)
  • In Code Mode, calling a namespace as if it were a tool now suggests up to three real tools under it. (#63697)
  • Fixed retryable provider streams losing completed work when interrupted.
  • Fixed GitHub Copilot requests using the wrong endpoint before models finish loading.
  • Fixed exhausted request rate limits being treated as terminal. Thanks @​Kyle-j-bush. (#59816)
  • Fixed LM Studio models with a null context length and accepted decision-type models. Thanks @​tomzhu1024. (#56214)

TUI

Improvements

  • Transcript verbosity now defaults to low, which summarizes each run of tools and thoughts into one activity row. A session.verbosity you already set is kept. (#63207)
  • Session IDs found in messages can now be opened directly.
  • Activity tabs are clickable and open the correct view.
  • Shell mode has its own prompt color under the new designs.

Bug fixes

... (truncated)

Changelog

Sourced from @​opencode/plugin's changelog.

v2.3.0 — 2026-11-13

Highlights

  • Background Subagents by Default: Subagents now return immediately, continue in the background, and report back whenever they become idle. You can keep working in the parent session while multiple subagents run concurrently. (#63382)
  • Quieter Transcripts by Default: The TUI now summarizes each run of tool calls and thoughts into one collapsible activity row, so the answer is easier to follow. To see every step again, set Verbosity to medium or high in settings, or set session.verbosity in your TUI config; an existing setting is kept. (#63207)
  • Jump to an Earlier Prompt: In the desktop app, open Jump to message from the command palette or press Cmd+Alt+G (Ctrl+Alt+G on Windows and Linux) to search prompts across the current session and jump directly to one. (#63585)

Core

Improvements

  • Subagents now always run in the background, return their session ID immediately, and report results to their parent whenever they become idle. (#63382)
  • Added experimental support for MCP events, behind the mcp_events flag. (#63254, #63261, #63269)
  • Shell commands now survive server handoffs and keep their output when interrupted.
  • Added experimental support for moving a shell command to the background when its timeout expires, behind the shell_timeout_background flag. With the flag on, an explicit timeout on a background command stops it. (#63024, #63703)
  • Local Windows shell commands now run through the process daemon.
  • Added support for freeform tool input on compatible models.
  • Added LM Studio decision-model support.
  • Agents are now told when their session is a fork. Thanks @​hasta84. (#63235)
  • Tool output truncation now keeps the beginning of the output and preserves a usable preview if the full output cannot be saved.
  • Tail reads no longer load the entire file into memory.
  • Providers can present a client certificate for gateways that require mutual TLS. Set settings.tls with cert, key and an optional passphrase on the provider; values accept {file:} and {env:} like apiKey. (#61832)
  • When a subagent goes idle while its own background work is still running, its report to the parent now says it is still running, so the parent waits for the final report instead of treating the partial answer as done. (#63675)
  • Code Mode gets simpler structured results from file and skill tools: write and edit return their confirmation as a string, patch returns an empty result, and skill returns the skill's directory and content. (#63616, #63635, #63618, #63623)

Bug fixes

  • Fixed case-only file renames in patches on case-insensitive filesystems.
  • Fixed stale thinking being retained after Claude Agent prompts or tools change.
  • Fixed directly driven child sessions not resuming after a restart.
  • Fixed plugin replacement stopping when cleanup of an earlier plugin fails.
  • Fixed MCP OAuth refreshes and localhost redirects when a server rewrites 127.0.0.1.
  • Fixed saved API keys being omitted from local-model discovery.
  • Local model discovery (Ollama, LM Studio, vLLM) waits up to 15 seconds per request instead of 1, so remote or tunnelled endpoints list their models, and a slow endpoint no longer delays other endpoints or config reloads. (#63700)
  • In Code Mode, calling a namespace as if it were a tool now suggests up to three real tools under it. (#63697)
  • Fixed retryable provider streams losing completed work when interrupted.
  • Fixed GitHub Copilot requests using the wrong endpoint before models finish loading.
  • Fixed exhausted request rate limits being treated as terminal. Thanks @​Kyle-j-bush. (#59816)
  • Fixed LM Studio models with a null context length and accepted decision-type models. Thanks @​tomzhu1024. (#56214)

TUI

Improvements

  • Transcript verbosity now defaults to low, which summarizes each run of tools and thoughts into one activity row. A session.verbosity you already set is kept. (#63207)
  • Session IDs found in messages can now be opened directly.
  • Activity tabs are clickable and open the correct view.
  • Shell mode has its own prompt color under the new designs.

... (truncated)

Commits
  • a6b15d3 release: v2.3.0
  • b81c5f3 feat(plugin): export Tool from the effect entrypoint (#63698)
  • 2f886a2 fix(core): pass stored message metadata to session request hooks (#63590)
  • ec263d6 fix(core): keep plugin swaps going when a cleanup fails (#63548)
  • b268a4e feat(session-ui): maximize Mermaid diagrams to zoom and pan them (#59250)
  • ffcaeec refactor(app): remove leftover foreground subagent UI (#63391)
  • 2ef38b2 fix(app): accept a pasted redirect URL for provider sign-in (#63315)
  • e56eff2 feat(core): tell agents when they are in a fork (#63235)
  • 36f559b chore: move the data site off sst
  • c4bf172 v0.8.4 (#63055)
  • Additional commits viewable in compare view

Updates @opentui/core from 0.5.17 to 0.8.4

Release notes

Sourced from @​opentui/core's releases.

Release v0.8.4

A chat log often puts many CodeRenderable blocks in a ScrollBoxRenderable with viewportCulling: true. With streaming: true and drawUnstyledText: false, a block that gets new content keeps showing its old highlighted text until the new highlight is ready, so the reader never sees a flash of plain text. But a block starts its highlight from its update hook, and a frame calls no hooks on a block that the scroll box culls. In 0.8.3, a culled block therefore kept its old text in its buffer, and layout measured that old text. The scroll box reported a stale scrollHeight until the block scrolled back into view.

In 0.8.4, a block that gets new content first asks the scene whether the hooks of the next frame reach it. If they do, the block keeps its old highlight, as before. If they do not, as for a culled, hidden, or detached block, the block loads the new plain text at once, so layout measures the new content. It does not paint that text until the highlight is ready. The highlight starts in the first frame that reaches the block again. C hosts can ask the same question with ot_scene_reaches_hooks. It answers with the branch selection that the next frame uses.

Added

  • native: ot_scene_reaches_hooks tells if the hooks of a frame reach a node. It selects culled branches as the next frame does. See C.

Fixed

  • core: A culled streaming CodeRenderable with drawUnstyledText: false now measures new content immediately. It does not paint that text until its highlight is ready. See Code.

API changes and documentation: https://opentui.com/docs/releases/0.8.4

Full Changelog: anomalyco/opentui@v0.8.3...v0.8.4

Release v0.8.3

Over ssh, sshd drops COLORTERM. A terminal that draws 24-bit color but sends TERM=xterm-256color without COLORTERM therefore got every color mapped to the 256-color palette. In WezTerm and xterm over ssh, a navy #23344b turned into a gray #3a3a3a. In 0.8.2, only a kitty XTVERSION reply turned on 24-bit color. In 0.8.3, when COLORTERM does not settle the question, the startup queries also ask XTGETTCAP RGB and Tc. A positive reply turns on 24-bit color. So does an XTVERSION reply from Ghostty, WezTerm, foot, XTerm, iTerm2, or tmux, because tmux converts 24-bit colors for its client itself. The replies come back through ssh, so this works without COLORTERM. Inside GNU Screen, OpenTUI sends neither query, because Screen drops 24-bit colors and prints the query bodies as text. When nothing answers, the old TERM rule still applies. Alacritty and mosh answer none of these queries, so they still need COLORTERM=truecolor.

The width method decides how many cells an emoji sequence takes. When OpenTUI picks a different method than the terminal uses, the line overflows or leaves gaps. Before, OpenTUI kept the unicode method in terminals that do not report mode 2027, even though many of them draw a sequence one code point at a time. tmux 3.6 and later draws a sequence as one cluster but got wcwidth. An inherited TERM_PROGRAM=ghostty also forced unicode-wide in other terminals. Now the method comes from one place, with the strongest evidence first:

  1. OPENTUI_FORCE_*, also over SSH.
  2. The multiplexer.
  3. The DECRPM 2027 reply. An unrecognized or permanently reset mode means wcwidth, except in kitty and iTerm2.
  4. XTVERSION.
  5. The environment, where TERM wins over an inherited TERM_PROGRAM.
Terminal Before After
Alacritty, xterm, urxvt, GNOME Terminal, VS Code, Zellij, foot (wcswidth) unicode wcwidth
tmux 3.6+ wcwidth unicode
kitty started from Ghostty unicode-wide unicode
Ghostty over SSH, libghostty unicode unicode-wide

No method matches tmux when variation-selector-always-wide is off. Unicode is the closest. If the new choice is wrong for your terminal, set OPENTUI_FORCE_UNICODE or OPENTUI_FORCE_WCWIDTH. These settings still win.

Before this release, a host that started an unmodified OpenTUI app could not easily make it load a different native build. setRenderLibPath() needs code, and OTUI_ASSET_ROOT needs the whole asset tree under one root. OPENTUI_LIB_PATH names one library file, under both Bun and Node:

OPENTUI_LIB_PATH=../opentui/packages/native/lib/x86_64-linux/libopentui.so bun run src/index.ts

A relative path resolves against the working directory. setRenderLibPath() takes precedence over the variable, and the variable takes precedence over OTUI_ASSET_ROOT and the platform package. If the file is missing or does not load, the error names the variable. Core now also checks the context ABI version when it loads a library, so a library built for another context ABI fails at load and not at a later call.

A host that embeds a terminal often has to know where the terminal's view is. For example, it can pass an unused wheel step to an outer scroll view or draw a scrollbar. Counting scroll steps does not give the answer. Output and resizes keep the view on its history rows, a scrollback clear jumps to the live screen, and the alternate screen has no history. EmbeddedTerminalRenderable.getScroll() reads the current view from the emulator, including the moves that the emulator makes on its own:

function scrollStatus(terminal: EmbeddedTerminalRenderable): string {
</tr></table> 

... (truncated)

Commits
  • d4a2af2 Release v0.8.4
  • f7e5763 native: select a culled branch as the next frame will
  • b6ab797 native: report whether a frame's hooks reach a node
  • feecf2c core: keep Code highlights only where the scene runs its hooks
  • 07697c5 core: measure culled Code content without waiting for a highlight
  • b9e9d46 Release v0.8.3
  • 6adfa20 native: ask the terminal for 24-bit color before falling back (#1941)
  • e4ad586 native: export the audio engine in opentui.h (#1935)
  • cd23e75 native: report the embedded terminal viewport (#1934)
  • d8e5461 core: load the native library from OPENTUI_LIB_PATH (#1933)
  • Additional commits viewable in compare view

Updates @opentui/solid from 0.5.17 to 0.8.4

Release notes

Sourced from @​opentui/solid's releases.

Release v0.8.4

A chat log often puts many CodeRenderable blocks in a ScrollBoxRenderable with viewportCulling: true. With streaming: true and drawUnstyledText: false, a block that gets new content keeps showing its old highlighted text until the new highlight is ready, so the reader never sees a flash of plain text. But a block starts its highlight from its update hook, and a frame calls no hooks on a block that the scroll box culls. In 0.8.3, a culled block therefore kept its old text in its buffer, and layout measured that old text. The scroll box reported a stale scrollHeight until the block scrolled back into view.

In 0.8.4, a block that gets new content first asks the scene whether the hooks of the next frame reach it. If they do, the block keeps its old highlight, as before. If they do not, as for a culled, hidden, or detached block, the block loads the new plain text at once, so layout measures the new content. It does not paint that text until the highlight is ready. The highlight starts in the first frame that reaches the block again. C hosts can ask the same question with ot_scene_reaches_hooks. It answers with the branch selection that the next frame uses.

Added

  • native: ot_scene_reaches_hooks tells if the hooks of a frame reach a node. It selects culled branches as the next frame does. See C.

Fixed

  • core: A culled streaming CodeRenderable with drawUnstyledText: false now measures new content immediately. It does not paint that text until its highlight is ready. See Code.

API changes and documentation: https://opentui.com/docs/releases/0.8.4

Full Changelog: anomalyco/opentui@v0.8.3...v0.8.4

Release v0.8.3

Over ssh, sshd drops COLORTERM. A terminal that draws 24-bit color but sends TERM=xterm-256color without COLORTERM therefore got every color mapped to the 256-color palette. In WezTerm and xterm over ssh, a navy #23344b turned into a gray #3a3a3a. In 0.8.2, only a kitty XTVERSION reply turned on 24-bit color. In 0.8.3, when COLORTERM does not settle the question, the startup queries also ask XTGETTCAP RGB and Tc. A positive reply turns on 24-bit color. So does an XTVERSION reply from Ghostty, WezTerm, foot, XTerm, iTerm2, or tmux, because tmux converts 24-bit colors for its client itself. The replies come back through ssh, so this works without COLORTERM. Inside GNU Screen, OpenTUI sends neither query, because Screen drops 24-bit colors and prints the query bodies as text. When nothing answers, the old TERM rule still applies. Alacritty and mosh answer none of these queries, so they still need COLORTERM=truecolor.

The width method decides how many cells an emoji sequence takes. When OpenTUI picks a different method than the terminal uses, the line overflows or leaves gaps. Before, OpenTUI kept the unicode method in terminals that do not report mode 2027, even though many of them draw a sequence one code point at a time. tmux 3.6 and later draws a sequence as one cluster but got wcwidth. An inherited TERM_PROGRAM=ghostty also forced unicode-wide in other terminals. Now the method comes from one place, with the strongest evidence first:

  1. OPENTUI_FORCE_*, also over SSH.
  2. The multiplexer.
  3. The DECRPM 2027 reply. An unrecognized or permanently reset mode means wcwidth, except in kitty and iTerm2.
  4. XTVERSION.
  5. The environment, where TERM wins over an inherited TERM_PROGRAM.
Terminal Before After
Alacritty, xterm, urxvt, GNOME Terminal, VS Code, Zellij, foot (wcswidth) unicode wcwidth
tmux 3.6+ wcwidth unicode
kitty started from Ghostty unicode-wide unicode
Ghostty over SSH, libghostty unicode unicode-wide

No method matches tmux when variation-selector-always-wide is off. Unicode is the closest. If the new choice is wrong for your terminal, set OPENTUI_FORCE_UNICODE or OPENTUI_FORCE_WCWIDTH. These settings still win.

Before this release, a host that started an unmodified OpenTUI app could not easily make it load a different native build. setRenderLibPath() needs code, and OTUI_ASSET_ROOT needs the whole asset tree under one root. OPENTUI_LIB_PATH names one library file, under both Bun and Node:

OPENTUI_LIB_PATH=../opentui/packages/native/lib/x86_64-linux/libopentui.so bun run src/index.ts

A relative path resolves against the working directory. setRenderLibPath() takes precedence over the variable, and the variable takes precedence over OTUI_ASSET_ROOT and the platform package. If the file is missing or does not load, the error names the variable. Core now also checks the context ABI version when it loads a library, so a library built for another context ABI fails at load and not at a later call.

A host that embeds a terminal often has to know where the terminal's view is. For example, it can pass an unused wheel step to an outer scroll view or draw a scrollbar. Counting scroll steps does not give the answer. Output and resizes keep the view on its history rows, a scrollback clear jumps to the live screen, and the alternate screen has no history. EmbeddedTerminalRenderable.getScroll() reads the current view from the emulator, including the moves that the emulator makes on its own:

function scrollStatus(terminal: EmbeddedTerminalRenderable): string {
</tr></table> 

... (truncated)

Commits

Updates solid-js from 1.9.12 to 1.9.19

Commits

Updates @profullstack/hqtui from 0.11.1 to 0.12.0

Release notes

Sourced from @​profullstack/hqtui's releases.

0.12.0: context menus

Right-click context menus. Tabs get Close tab, Close all but this tab, Close all tabs and app-supplied items (e.g. Reload from disk); middle-click closes. ui.contextArea adds a menu to any content, ui.contextMenu / widgets.drawContextMenu draw one, app.openContextMenu opens one from code. Also: a modal with no focusable controls now receives arrow keys (fixes emoji picker arrows in a live app). #144

Published by hand from the CI-packed tarballs (run 41431341552) because the repo's NPM_TOKEN secret is expired.

Commits
  • ecf3688 Context menus: right-click tabs (close / close others / close all), contextAr...
  • See full diff in compare view
Attestation changes

This version has no provenance attestation, while the previous version (0.11.1) was attested. Review the package versions before updating.


Updates tsdown from 0.23.0 to 0.23.7

Release notes

Sourced from tsdown's releases.

v0.23.7

[!NOTE] v0.23.6 was skipped on purpose: its release failed, so this release follows v0.23.5 directly.

Notes

rolldown-plugin-dts is now v0.30. Full details are in the rolldown-plugin-dts v0.30.0 release notes.

Migration

dts.entry only filters entries. Only entries that match get declaration files. A matching file that is not an entry no longer gets its own declaration file. To emit declarations for such a file, add it to entry. The filter now applies to .d.cts as well as .d.mts.

dts.entry is resolved from cwd. Patterns are relative to tsdown's cwd, the same as the top-level entry, instead of process.cwd(). This only matters when the two differ, e.g. in workspace builds. Set dts.cwd to override it.

dts.emitDtsOnly and dts.dtsInput are deprecated. Use dts.dtsOnly instead. The old names still work but log a warning.

Highlights

  • dts: An entry's file-level doc comment is kept in its declaration file.
  • dts: Declaration files no longer contain a dangling sourceMappingURL.
  • dts: CJS declaration builds no longer emit a throwaway JS chunk. With the tsc generator, they build one program for all entries.
  • tsgo (experimental): Diagnostics show code context in color terminals, and packages from project references and files outside the tsconfig directory now get declarations.
  • Agent skill: The npm package now ships a small tsdown skill. pnpm 12.11+ can link it into agent skill directories, and it points agents to the full skill on GitHub for the installed version.

   🚀 Features

    View changes on GitHub

v0.23.5

Notes

rolldown-plugin-dts is now v0.29. tsdown passes dts options through to it unchanged, so its deprecations show up in your config too. Full details are in the rolldown-plugin-dts v0.29.0 release notes.

Migration

tsc-only dts options move under dts.tsc. The top-level build, incremental, parallel, eager, newContext and vue options still work but log a deprecation warning. Setting the same option at both levels throws an error. emitJs stays at the top level.

 export default defineConfig({
   dts: {
-    vue: true,
+    tsc: { vue: true },
   },
 })

... (truncated)

Commits

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Nov 16, 2026
…th 6 updates

Bumps the npm-tui-minor-patch group with 6 updates in the /src/plugins/tui directory:

| Package | From | To |
| --- | --- | --- |
| [@opencode/plugin](https://github.com/anomalyco/opencode/tree/HEAD/packages/plugin) | `2.0.26` | `2.3.0` |
| [@opentui/core](https://github.com/anomalyco/opentui/tree/HEAD/packages/core) | `0.5.17` | `0.8.4` |
| [@opentui/solid](https://github.com/anomalyco/opentui/tree/HEAD/packages/solid) | `0.5.17` | `0.8.4` |
| [solid-js](https://github.com/solidjs/solid) | `1.9.12` | `1.9.19` |
| [@profullstack/hqtui](https://github.com/profullstack/hqtui/tree/HEAD/packages/hqtui) | `0.11.1` | `0.12.0` |
| [tsdown](https://github.com/rolldown/tsdown) | `0.23.0` | `0.23.7` |



Updates `@opencode/plugin` from 2.0.26 to 2.3.0
- [Release notes](https://github.com/anomalyco/opencode/releases)
- [Changelog](https://github.com/anomalyco/opencode/blob/dev/CHANGELOG.md)
- [Commits](https://github.com/anomalyco/opencode/commits/v2.3.0/packages/plugin)

Updates `@opentui/core` from 0.5.17 to 0.8.4
- [Release notes](https://github.com/anomalyco/opentui/releases)
- [Commits](https://github.com/anomalyco/opentui/commits/v0.8.4/packages/core)

Updates `@opentui/solid` from 0.5.17 to 0.8.4
- [Release notes](https://github.com/anomalyco/opentui/releases)
- [Commits](https://github.com/anomalyco/opentui/commits/v0.8.4/packages/solid)

Updates `solid-js` from 1.9.12 to 1.9.19
- [Release notes](https://github.com/solidjs/solid/releases)
- [Changelog](https://github.com/solidjs/solid/blob/main/CHANGELOG.md)
- [Commits](https://github.com/solidjs/solid/commits)

Updates `@profullstack/hqtui` from 0.11.1 to 0.12.0
- [Release notes](https://github.com/profullstack/hqtui/releases)
- [Commits](https://github.com/profullstack/hqtui/commits/v0.12.0/packages/hqtui)

Updates `tsdown` from 0.23.0 to 0.23.7
- [Release notes](https://github.com/rolldown/tsdown/releases)
- [Commits](rolldown/tsdown@v0.23.0...v0.23.7)

---
updated-dependencies:
- dependency-name: "@opencode/plugin"
  dependency-version: 2.2.7
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: npm-tui-minor-patch
- dependency-name: "@opentui/core"
  dependency-version: 0.8.4
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: npm-tui-minor-patch
- dependency-name: "@opentui/solid"
  dependency-version: 0.8.4
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: npm-tui-minor-patch
- dependency-name: "@profullstack/hqtui"
  dependency-version: 0.12.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-tui-minor-patch
- dependency-name: solid-js
  dependency-version: 1.9.19
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: npm-tui-minor-patch
- dependency-name: tsdown
  dependency-version: 0.23.7
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: npm-tui-minor-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot changed the title chore(deps): bump the npm-tui-minor-patch group in /src/plugins/tui with 6 updates chore(deps): bump the npm-tui-minor-patch group across 1 directory with 6 updates Nov 16, 2026
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/src/plugins/tui/npm-tui-minor-patch-9caeb01d52 branch from 4e5763c to 72f3ba3 Compare November 16, 2026 09:43

This branch has not been deployed

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

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants