diff --git a/.changeset/aux-deadlines.md b/.changeset/aux-deadlines.md deleted file mode 100644 index 1ebaf18f3bcc..000000000000 --- a/.changeset/aux-deadlines.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -"@reddb-io/redcode": minor -"@reddb-io/redcode-core": patch ---- - -Bound the model calls a turn makes that are not the turn itself - -Naming a session and compacting the conversation both call a provider outside the step loop, where the turn's inactivity watchdog cannot see them: one runs before any step handle exists, the other creates a processor of its own. A provider that stopped answering during either held the turn open with nothing on screen and no error. Both now give up — naming after two minutes, compacting after ten — and say so. A session keeping its default name is a far smaller loss than a turn that never starts. Configurable via `experimental.aux_timeout`. diff --git a/.changeset/busy-status.md b/.changeset/busy-status.md deleted file mode 100644 index b2637adff401..000000000000 --- a/.changeset/busy-status.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -"@reddb-io/redcode": minor -"@reddb-io/redcode-schema": minor ---- - -Say what a busy session is actually doing - -`session.status` reported `busy` as a bare tag, so the TUI had to reverse-engineer the phase from message parts and every other client got nothing at all. `busy` now carries an optional phase (preparing, thinking, writing, tool, compacting), the tool being run, the step number, and when the phase started. The fields are additive: readers that discriminate on `type` alone are unaffected. The TUI uses them for the window the parts cannot describe — before the first byte arrives — and shows the step number, so a turn on its eighth step no longer looks the same as one that just started. diff --git a/.changeset/loop-guard.md b/.changeset/loop-guard.md deleted file mode 100644 index 6538aeb79327..000000000000 --- a/.changeset/loop-guard.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -"@reddb-io/redcode": minor -"@reddb-io/redcode-core": patch ---- - -Notice when the model is repeating itself, and say so instead of asking the user - -The old detector compared the last three parts of a single assistant message and required byte-identical serialized input, so one interleaved reasoning part — which reasoning models emit constantly — reset it permanently, a loop spanning steps was invisible, and when it did fire it asked a question whose wait had no bound: the only defence against a loop was itself a way to hang. It now looks across the whole turn, counts only calls that returned the same result (identical calls with different results are polling, and are left alone), and answers the repeated call itself with a correction quoting the model's own arguments and the answer it keeps ignoring. If the correction changes nothing, the turn ends. Nobody is asked anything. Configurable via `experimental.loop_guard`; a `doom_loop: "allow"` permission rule still turns it off. diff --git a/.changeset/mise-detection.md b/.changeset/mise-detection.md deleted file mode 100644 index a252683c2b4f..000000000000 --- a/.changeset/mise-detection.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -"@reddb-io/redcode": patch ---- - -Only treat an install as mise-managed when Redcode itself came from mise - -The check matched any `mise/installs` path in the running executable, so a machine whose Bun comes from mise reported every Redcode install as mise-managed — and self-update would then try `mise upgrade` on a tool mise does not have. It now matches Redcode's own install directory. diff --git a/.changeset/reconnect-record-order.md b/.changeset/reconnect-record-order.md deleted file mode 100644 index 60173c783c39..000000000000 --- a/.changeset/reconnect-record-order.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -"@reddb-io/redcode-app": patch ---- - -Re-arm the timeline offset watch however the mutation batch is ordered - -A batch that carries both the removal and the re-insertion of the scroll element can present them in either order, and the reconnect was decided record by record: with the addition first, it was judged before the removal had been seen, so the element returned to the page with nothing watching its offset. The batch is now judged as a whole. diff --git a/.changeset/stalls-loops-and-verbosity.md b/.changeset/stalls-loops-and-verbosity.md deleted file mode 100644 index a5d63c75c544..000000000000 --- a/.changeset/stalls-loops-and-verbosity.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"@reddb-io/redcode": minor ---- - -Stop turns from stalling or looping in silence: a turn now has a hard step ceiling, a stream that goes quiet is aborted whatever content type it uses, auto-compaction can no longer paste your prompt back into the transcript over and over, the TUI re-reads the session after the event stream reconnects instead of waiting on a message it never received, and the status line says when nothing has arrived for a while rather than spinning as if it were working. diff --git a/.changeset/step-budget.md b/.changeset/step-budget.md deleted file mode 100644 index 0abfda43c778..000000000000 --- a/.changeset/step-budget.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -"@reddb-io/redcode": minor -"@reddb-io/redcode-core": patch ---- - -Ask for a report before the step ceiling instead of cutting the turn off at it - -The turn ceiling was a cliff: at step 200 the turn stopped and everything the model had worked out but not yet written down went with it, leaving the user told to "send another message to continue" with nothing to base it on. The last steps before the wall are now spent the way `agent.steps` already spends its own: tools off, a summary of what was done, what is left, and what to do next. The wall itself is unchanged, for a model that will not yield. Configurable via `experimental.turn_steps`. diff --git a/.changeset/tool-deadlines.md b/.changeset/tool-deadlines.md deleted file mode 100644 index ed6cd140bbf4..000000000000 --- a/.changeset/tool-deadlines.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -"@reddb-io/redcode": minor -"@reddb-io/redcode-core": patch ---- - -Stop a tool that never returns instead of letting it hold the turn open - -Most tools carry no bound of their own, so a read on a dead mount or an MCP call to a process that went away kept a turn running with no output and no error — and the turn's inactivity watchdog could not help, because a tool in flight is deliberately counted as work. Tool calls now have a ten minute backstop, reported to the model as an ordinary tool failure it can react to. Tools that legitimately take as long as they take are exempt (`shell`, `bash`, `question`, `task`), and time spent waiting on a permission prompt is not charged against the tool. Configurable via `experimental.tool_timeout`, `false` to disable. diff --git a/.changeset/turn-inactivity-watchdog.md b/.changeset/turn-inactivity-watchdog.md deleted file mode 100644 index 99ffce6adbad..000000000000 --- a/.changeset/turn-inactivity-watchdog.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"@reddb-io/redcode": minor ---- - -End a turn that has stopped producing anything, where nobody is watching to end it themselves. Time a tool spends running or a permission spends awaiting an answer does not count as silence, so a long build is never mistaken for a provider that went away. In the TUI and the desktop app the turn is reported rather than ended, since a person is there to read it and press escape; a scripted run, an editor speaking ACP or a scheduled job ends it. Configurable through `experimental.turn_stall`, or `false` to disable. diff --git a/package.json b/package.json index 0e2042fd1805..f89aab5393ad 100644 --- a/package.json +++ b/package.json @@ -1,7 +1,7 @@ { "$schema": "https://json.schemastore.org/package.json", "name": "@reddb-io/redcode-workspace", - "version": "0.13.4", + "version": "0.14.0", "description": "RedDB's AI-powered development tool", "private": true, "type": "module", diff --git a/packages/app/CHANGELOG.md b/packages/app/CHANGELOG.md new file mode 100644 index 000000000000..ca3b8197ab54 --- /dev/null +++ b/packages/app/CHANGELOG.md @@ -0,0 +1,18 @@ +# @reddb-io/redcode-app + +## 1.18.19 + +### Patch Changes + +- 872f6da: Re-arm the timeline offset watch however the mutation batch is ordered + + A batch that carries both the removal and the re-insertion of the scroll element can present them in either order, and the reconnect was decided record by record: with the addition first, it was judged before the removal had been seen, so the element returned to the page with nothing watching its offset. The batch is now judged as a whole. + +- Updated dependencies [78d1b03] +- Updated dependencies [82bb18a] +- Updated dependencies [8c43207] +- Updated dependencies [603d8c7] +- Updated dependencies [86b2250] + - @reddb-io/redcode-core@1.18.19 + - @reddb-io/redcode-schema@1.19.0 + - @reddb-io/redcode-session-ui@1.18.19 diff --git a/packages/app/package.json b/packages/app/package.json index fb5317bf0ec7..ca9b375d4e40 100644 --- a/packages/app/package.json +++ b/packages/app/package.json @@ -1,6 +1,6 @@ { "name": "@reddb-io/redcode-app", - "version": "1.18.18", + "version": "1.18.19", "description": "", "type": "module", "exports": { diff --git a/packages/cli/CHANGELOG.md b/packages/cli/CHANGELOG.md new file mode 100644 index 000000000000..ff67ea4529b3 --- /dev/null +++ b/packages/cli/CHANGELOG.md @@ -0,0 +1,13 @@ +# @reddb-io/redcode-cli + +## 1.18.19 + +### Patch Changes + +- Updated dependencies [78d1b03] +- Updated dependencies [8c43207] +- Updated dependencies [603d8c7] +- Updated dependencies [86b2250] + - @reddb-io/redcode-core@1.18.19 + - @reddb-io/redcode-server@1.18.19 + - @reddb-io/redcode-tui@1.18.19 diff --git a/packages/cli/package.json b/packages/cli/package.json index 4133a9dc91ee..b8d56fff2b2d 100644 --- a/packages/cli/package.json +++ b/packages/cli/package.json @@ -1,7 +1,7 @@ { "$schema": "https://json.schemastore.org/package.json", "name": "@reddb-io/redcode-cli", - "version": "1.18.18", + "version": "1.18.19", "type": "module", "license": "MIT", "bin": { diff --git a/packages/client/CHANGELOG.md b/packages/client/CHANGELOG.md new file mode 100644 index 000000000000..618546573c62 --- /dev/null +++ b/packages/client/CHANGELOG.md @@ -0,0 +1,9 @@ +# @reddb-io/redcode-client + +## 1.18.19 + +### Patch Changes + +- Updated dependencies [82bb18a] + - @reddb-io/redcode-schema@1.19.0 + - @reddb-io/redcode-protocol@1.18.19 diff --git a/packages/client/package.json b/packages/client/package.json index 3805ef00a571..dbe8dd43b44d 100644 --- a/packages/client/package.json +++ b/packages/client/package.json @@ -1,7 +1,7 @@ { "$schema": "https://json.schemastore.org/package.json", "name": "@reddb-io/redcode-client", - "version": "1.18.18", + "version": "1.18.19", "private": true, "type": "module", "license": "MIT", diff --git a/packages/core/CHANGELOG.md b/packages/core/CHANGELOG.md new file mode 100644 index 000000000000..5148b9d14426 --- /dev/null +++ b/packages/core/CHANGELOG.md @@ -0,0 +1,25 @@ +# @reddb-io/redcode-core + +## 1.18.19 + +### Patch Changes + +- 78d1b03: Bound the model calls a turn makes that are not the turn itself + + Naming a session and compacting the conversation both call a provider outside the step loop, where the turn's inactivity watchdog cannot see them: one runs before any step handle exists, the other creates a processor of its own. A provider that stopped answering during either held the turn open with nothing on screen and no error. Both now give up — naming after two minutes, compacting after ten — and say so. A session keeping its default name is a far smaller loss than a turn that never starts. Configurable via `experimental.aux_timeout`. + +- 8c43207: Notice when the model is repeating itself, and say so instead of asking the user + + The old detector compared the last three parts of a single assistant message and required byte-identical serialized input, so one interleaved reasoning part — which reasoning models emit constantly — reset it permanently, a loop spanning steps was invisible, and when it did fire it asked a question whose wait had no bound: the only defence against a loop was itself a way to hang. It now looks across the whole turn, counts only calls that returned the same result (identical calls with different results are polling, and are left alone), and answers the repeated call itself with a correction quoting the model's own arguments and the answer it keeps ignoring. If the correction changes nothing, the turn ends. Nobody is asked anything. Configurable via `experimental.loop_guard`; a `doom_loop: "allow"` permission rule still turns it off. + +- 603d8c7: Ask for a report before the step ceiling instead of cutting the turn off at it + + The turn ceiling was a cliff: at step 200 the turn stopped and everything the model had worked out but not yet written down went with it, leaving the user told to "send another message to continue" with nothing to base it on. The last steps before the wall are now spent the way `agent.steps` already spends its own: tools off, a summary of what was done, what is left, and what to do next. The wall itself is unchanged, for a model that will not yield. Configurable via `experimental.turn_steps`. + +- 86b2250: Stop a tool that never returns instead of letting it hold the turn open + + Most tools carry no bound of their own, so a read on a dead mount or an MCP call to a process that went away kept a turn running with no output and no error — and the turn's inactivity watchdog could not help, because a tool in flight is deliberately counted as work. Tool calls now have a ten minute backstop, reported to the model as an ordinary tool failure it can react to. Tools that legitimately take as long as they take are exempt (`shell`, `bash`, `question`, `task`), and time spent waiting on a permission prompt is not charged against the tool. Configurable via `experimental.tool_timeout`, `false` to disable. + +- Updated dependencies [82bb18a] + - @reddb-io/redcode-schema@1.19.0 + - @reddb-io/redcode-llm@1.18.19 diff --git a/packages/core/package.json b/packages/core/package.json index 432290e69d13..0f2304610f29 100644 --- a/packages/core/package.json +++ b/packages/core/package.json @@ -1,6 +1,6 @@ { "$schema": "https://json.schemastore.org/package.json", - "version": "1.18.18", + "version": "1.18.19", "name": "@reddb-io/redcode-core", "type": "module", "license": "MIT", diff --git a/packages/enterprise/CHANGELOG.md b/packages/enterprise/CHANGELOG.md new file mode 100644 index 000000000000..4d3c1a801c5e --- /dev/null +++ b/packages/enterprise/CHANGELOG.md @@ -0,0 +1,12 @@ +# @reddb-io/redcode-enterprise + +## 1.18.19 + +### Patch Changes + +- Updated dependencies [78d1b03] +- Updated dependencies [8c43207] +- Updated dependencies [603d8c7] +- Updated dependencies [86b2250] + - @reddb-io/redcode-core@1.18.19 + - @reddb-io/redcode-session-ui@1.18.19 diff --git a/packages/enterprise/package.json b/packages/enterprise/package.json index 943f13531be9..0ddf43daafcb 100644 --- a/packages/enterprise/package.json +++ b/packages/enterprise/package.json @@ -1,6 +1,6 @@ { "name": "@reddb-io/redcode-enterprise", - "version": "1.18.18", + "version": "1.18.19", "private": true, "type": "module", "license": "MIT", diff --git a/packages/llm/CHANGELOG.md b/packages/llm/CHANGELOG.md new file mode 100644 index 000000000000..d9ba54326266 --- /dev/null +++ b/packages/llm/CHANGELOG.md @@ -0,0 +1,8 @@ +# @reddb-io/redcode-llm + +## 1.18.19 + +### Patch Changes + +- Updated dependencies [82bb18a] + - @reddb-io/redcode-schema@1.19.0 diff --git a/packages/llm/package.json b/packages/llm/package.json index 2f051df7eaab..cab44a3aa6a7 100644 --- a/packages/llm/package.json +++ b/packages/llm/package.json @@ -1,6 +1,6 @@ { "$schema": "https://json.schemastore.org/package.json", - "version": "1.18.18", + "version": "1.18.19", "name": "@reddb-io/redcode-llm", "type": "module", "license": "MIT", diff --git a/packages/protocol/CHANGELOG.md b/packages/protocol/CHANGELOG.md new file mode 100644 index 000000000000..2702305c971b --- /dev/null +++ b/packages/protocol/CHANGELOG.md @@ -0,0 +1,8 @@ +# @reddb-io/redcode-protocol + +## 1.18.19 + +### Patch Changes + +- Updated dependencies [82bb18a] + - @reddb-io/redcode-schema@1.19.0 diff --git a/packages/protocol/package.json b/packages/protocol/package.json index 60ddcb21e74e..aa5d2d82e188 100644 --- a/packages/protocol/package.json +++ b/packages/protocol/package.json @@ -1,7 +1,7 @@ { "$schema": "https://json.schemastore.org/package.json", "name": "@reddb-io/redcode-protocol", - "version": "1.18.18", + "version": "1.18.19", "private": true, "type": "module", "license": "MIT", diff --git a/packages/redcode/CHANGELOG.md b/packages/redcode/CHANGELOG.md index 1b7ff1631d1f..b06a318bff20 100644 --- a/packages/redcode/CHANGELOG.md +++ b/packages/redcode/CHANGELOG.md @@ -1,5 +1,45 @@ # opencode +## 0.14.0 + +### Minor Changes + +- 78d1b03: Bound the model calls a turn makes that are not the turn itself + + Naming a session and compacting the conversation both call a provider outside the step loop, where the turn's inactivity watchdog cannot see them: one runs before any step handle exists, the other creates a processor of its own. A provider that stopped answering during either held the turn open with nothing on screen and no error. Both now give up — naming after two minutes, compacting after ten — and say so. A session keeping its default name is a far smaller loss than a turn that never starts. Configurable via `experimental.aux_timeout`. + +- 82bb18a: Say what a busy session is actually doing + + `session.status` reported `busy` as a bare tag, so the TUI had to reverse-engineer the phase from message parts and every other client got nothing at all. `busy` now carries an optional phase (preparing, thinking, writing, tool, compacting), the tool being run, the step number, and when the phase started. The fields are additive: readers that discriminate on `type` alone are unaffected. The TUI uses them for the window the parts cannot describe — before the first byte arrives — and shows the step number, so a turn on its eighth step no longer looks the same as one that just started. + +- 8c43207: Notice when the model is repeating itself, and say so instead of asking the user + + The old detector compared the last three parts of a single assistant message and required byte-identical serialized input, so one interleaved reasoning part — which reasoning models emit constantly — reset it permanently, a loop spanning steps was invisible, and when it did fire it asked a question whose wait had no bound: the only defence against a loop was itself a way to hang. It now looks across the whole turn, counts only calls that returned the same result (identical calls with different results are polling, and are left alone), and answers the repeated call itself with a correction quoting the model's own arguments and the answer it keeps ignoring. If the correction changes nothing, the turn ends. Nobody is asked anything. Configurable via `experimental.loop_guard`; a `doom_loop: "allow"` permission rule still turns it off. + +- 071c47d: Stop turns from stalling or looping in silence: a turn now has a hard step ceiling, a stream that goes quiet is aborted whatever content type it uses, auto-compaction can no longer paste your prompt back into the transcript over and over, the TUI re-reads the session after the event stream reconnects instead of waiting on a message it never received, and the status line says when nothing has arrived for a while rather than spinning as if it were working. +- 603d8c7: Ask for a report before the step ceiling instead of cutting the turn off at it + + The turn ceiling was a cliff: at step 200 the turn stopped and everything the model had worked out but not yet written down went with it, leaving the user told to "send another message to continue" with nothing to base it on. The last steps before the wall are now spent the way `agent.steps` already spends its own: tools off, a summary of what was done, what is left, and what to do next. The wall itself is unchanged, for a model that will not yield. Configurable via `experimental.turn_steps`. + +- 86b2250: Stop a tool that never returns instead of letting it hold the turn open + + Most tools carry no bound of their own, so a read on a dead mount or an MCP call to a process that went away kept a turn running with no output and no error — and the turn's inactivity watchdog could not help, because a tool in flight is deliberately counted as work. Tool calls now have a ten minute backstop, reported to the model as an ordinary tool failure it can react to. Tools that legitimately take as long as they take are exempt (`shell`, `bash`, `question`, `task`), and time spent waiting on a permission prompt is not charged against the tool. Configurable via `experimental.tool_timeout`, `false` to disable. + +- de65b16: End a turn that has stopped producing anything, where nobody is watching to end it themselves. Time a tool spends running or a permission spends awaiting an answer does not count as silence, so a long build is never mistaken for a provider that went away. In the TUI and the desktop app the turn is reported rather than ended, since a person is there to read it and press escape; a scripted run, an editor speaking ACP or a scheduled job ends it. Configurable through `experimental.turn_stall`, or `false` to disable. + +### Patch Changes + +- 95297f3: Only treat an install as mise-managed when Redcode itself came from mise + + The check matched any `mise/installs` path in the running executable, so a machine whose Bun comes from mise reported every Redcode install as mise-managed — and self-update would then try `mise upgrade` on a tool mise does not have. It now matches Redcode's own install directory. + +- Updated dependencies [82bb18a] + - @reddb-io/redcode-schema@1.19.0 + - @reddb-io/redcode-server@1.18.19 + - @reddb-io/redcode-tui@1.18.19 + - @reddb-io/redcode-llm@1.18.19 + - @reddb-io/redcode-protocol@1.18.19 + ## 0.13.4 ### Patch Changes diff --git a/packages/redcode/package.json b/packages/redcode/package.json index d4a65da3069a..40ece9f8c330 100644 --- a/packages/redcode/package.json +++ b/packages/redcode/package.json @@ -1,6 +1,6 @@ { "$schema": "https://json.schemastore.org/package.json", - "version": "0.13.4", + "version": "0.14.0", "name": "@reddb-io/redcode", "type": "module", "license": "MIT", diff --git a/packages/schema/CHANGELOG.md b/packages/schema/CHANGELOG.md new file mode 100644 index 000000000000..14a54d0d0a09 --- /dev/null +++ b/packages/schema/CHANGELOG.md @@ -0,0 +1,9 @@ +# @reddb-io/redcode-schema + +## 1.19.0 + +### Minor Changes + +- 82bb18a: Say what a busy session is actually doing + + `session.status` reported `busy` as a bare tag, so the TUI had to reverse-engineer the phase from message parts and every other client got nothing at all. `busy` now carries an optional phase (preparing, thinking, writing, tool, compacting), the tool being run, the step number, and when the phase started. The fields are additive: readers that discriminate on `type` alone are unaffected. The TUI uses them for the window the parts cannot describe — before the first byte arrives — and shows the step number, so a turn on its eighth step no longer looks the same as one that just started. diff --git a/packages/schema/package.json b/packages/schema/package.json index a1387be14af0..db7ef9a4c97a 100644 --- a/packages/schema/package.json +++ b/packages/schema/package.json @@ -1,7 +1,7 @@ { "$schema": "https://json.schemastore.org/package.json", "name": "@reddb-io/redcode-schema", - "version": "1.18.18", + "version": "1.19.0", "private": true, "type": "module", "license": "MIT", diff --git a/packages/sdk-next/CHANGELOG.md b/packages/sdk-next/CHANGELOG.md new file mode 100644 index 000000000000..70d2347315d5 --- /dev/null +++ b/packages/sdk-next/CHANGELOG.md @@ -0,0 +1,13 @@ +# @reddb-io/redcode-sdk-next + +## 1.18.19 + +### Patch Changes + +- Updated dependencies [78d1b03] +- Updated dependencies [8c43207] +- Updated dependencies [603d8c7] +- Updated dependencies [86b2250] + - @reddb-io/redcode-core@1.18.19 + - @reddb-io/redcode-client@1.18.19 + - @reddb-io/redcode-server@1.18.19 diff --git a/packages/sdk-next/package.json b/packages/sdk-next/package.json index 388310312d0a..71d45ac58f95 100644 --- a/packages/sdk-next/package.json +++ b/packages/sdk-next/package.json @@ -1,7 +1,7 @@ { "$schema": "https://json.schemastore.org/package.json", "name": "@reddb-io/redcode-sdk-next", - "version": "1.18.18", + "version": "1.18.19", "private": true, "type": "module", "license": "MIT", diff --git a/packages/server/CHANGELOG.md b/packages/server/CHANGELOG.md new file mode 100644 index 000000000000..6bbd3d7067ac --- /dev/null +++ b/packages/server/CHANGELOG.md @@ -0,0 +1,12 @@ +# @reddb-io/redcode-server + +## 1.18.19 + +### Patch Changes + +- Updated dependencies [78d1b03] +- Updated dependencies [8c43207] +- Updated dependencies [603d8c7] +- Updated dependencies [86b2250] + - @reddb-io/redcode-core@1.18.19 + - @reddb-io/redcode-protocol@1.18.19 diff --git a/packages/server/package.json b/packages/server/package.json index b79b6f2cbe45..73160c08f905 100644 --- a/packages/server/package.json +++ b/packages/server/package.json @@ -1,7 +1,7 @@ { "$schema": "https://json.schemastore.org/package.json", "name": "@reddb-io/redcode-server", - "version": "1.18.18", + "version": "1.18.19", "private": true, "type": "module", "license": "MIT", diff --git a/packages/session-ui/CHANGELOG.md b/packages/session-ui/CHANGELOG.md new file mode 100644 index 000000000000..d6ac2737e14a --- /dev/null +++ b/packages/session-ui/CHANGELOG.md @@ -0,0 +1,11 @@ +# @reddb-io/redcode-session-ui + +## 1.18.19 + +### Patch Changes + +- Updated dependencies [78d1b03] +- Updated dependencies [8c43207] +- Updated dependencies [603d8c7] +- Updated dependencies [86b2250] + - @reddb-io/redcode-core@1.18.19 diff --git a/packages/session-ui/package.json b/packages/session-ui/package.json index fa01b162f421..8af12cfff89a 100644 --- a/packages/session-ui/package.json +++ b/packages/session-ui/package.json @@ -1,6 +1,6 @@ { "name": "@reddb-io/redcode-session-ui", - "version": "1.18.18", + "version": "1.18.19", "private": true, "type": "module", "license": "MIT", diff --git a/packages/tui/CHANGELOG.md b/packages/tui/CHANGELOG.md new file mode 100644 index 000000000000..d4f6cb23c531 --- /dev/null +++ b/packages/tui/CHANGELOG.md @@ -0,0 +1,11 @@ +# @reddb-io/redcode-tui + +## 1.18.19 + +### Patch Changes + +- Updated dependencies [78d1b03] +- Updated dependencies [8c43207] +- Updated dependencies [603d8c7] +- Updated dependencies [86b2250] + - @reddb-io/redcode-core@1.18.19 diff --git a/packages/tui/package.json b/packages/tui/package.json index 2d80bc2d4f91..99cfb1951c0f 100644 --- a/packages/tui/package.json +++ b/packages/tui/package.json @@ -1,7 +1,7 @@ { "$schema": "https://json.schemastore.org/package.json", "name": "@reddb-io/redcode-tui", - "version": "1.18.18", + "version": "1.18.19", "private": true, "type": "module", "license": "MIT",