Skip to content

v1.4.0 Ready

Choose a tag to compare

View all tags
@MrOrangeJJ MrOrangeJJ released this 06 Apr 01:46
· 131 commits to main since this release
v1.4.0
9db5e53

English

v1.4.0 focuses on making long-lived state and Windows workflows more trustworthy: GyShell now stores conversation history in SQLite with a one-time automatic migration, older Windows PowerShell environments get more reliable command completion tracking with cleaner rendered output, resource monitoring can be paused per machine/source and remembers that choice, and terminal search no longer loses its target after tab switches or remounts. This release also explicitly improves support for Windows Server 2016 environments.

Highlights You Will Notice

  • SQLite-backed conversation history
    • the first launch after upgrading automatically detects legacy gyshell-chat-history.json and gyshell-ui-history.json, migrates them before the app continues, and keeps timestamped backup copies instead of deleting them
    • backend chat history and UI transcript history now live in one SQLite database, which should make larger history inventories feel steadier to browse, rename, and delete
    • startup now shows a dedicated migration progress barrier when old history needs conversion, so you can see what GyShell is doing instead of guessing whether launch is stuck
  • Much more reliable Windows PowerShell command execution
    • older local Windows PowerShell terminals and Windows-over-SSH sessions now use a sidecar tracking path to detect when a command really finished
    • GyShell now specifically targets troublesome older Windows hosts such as Windows Server 2016, where shell prompt noise and PTY behavior are more likely to break command tracking
    • command results render as a cleaner prompt + command + output transcript, avoiding stray shellhost fragments and VT noise that used to leak into captured output on some Windows hosts
    • packaged Windows desktop builds also include safer node-pty runtime handling, reducing install/builds that launch but have broken PTY behavior
  • Per-source monitor pause/resume
    • each monitored local machine or SSH target can now be paused or resumed independently from the monitor panel
    • the toggle is remembered across restarts and follows the resolved source identity, so reconnecting to the same host does not force you to reconfigure monitoring
    • this makes it easier to leave monitor panels open without continuously polling every source
  • Terminal find that stays attached
    • terminal Ctrl/Cmd+F search now keeps talking to the current xterm runtime after tab switches, rebinds, and layout remounts
    • match counts and navigation stay in sync with the active tab instead of silently targeting a stale terminal instance

Compatibility / Upgrade Notes

  • GyShell intentionally blocks startup while the migration runs, so the app does not open against half-migrated history.
  • After a successful migration, the old JSON history files are preserved as timestamped backup files.
  • Windows Server 2016 is a named support target in this release: the Windows command-tracking and transcript-cleanup work in v1.4.0 is especially meant to improve reliability on older PowerShell-based server environments.

中文

v1.4.0 重点在于让长期状态和 Windows 工作流更可信：GyShell 现在会把会话历史统一存进 SQLite，并在升级后自动做一次迁移；旧版 Windows PowerShell 环境下的命令完成判断和输出回显更稳；资源监控可以按机器/来源单独暂停并记住设置；终端搜索也不会再在切标签或重挂载后丢失目标。这次版本也明确加强了对 Windows Server 2016 环境的支持。

你会直接感知到的升级

  • 基于 SQLite 的会话历史存储
    • 升级后的首次启动会自动检测旧的 gyshell-chat-history.json 与 gyshell-ui-history.json，在应用继续启动前完成迁移，并把旧文件保留为带时间戳的备份
    • 后端会话历史和 UI 对话历史现在统一存进一个 SQLite 数据库，较大的历史列表在浏览、重命名、删除时会更稳
    • 当需要转换旧历史时，启动阶段会显示专门的迁移进度界面，你可以明确知道 GyShell 正在做什么，而不是怀疑应用卡住了
  • Windows PowerShell 命令执行稳定性明显提升
    • 较旧的本地 Windows PowerShell 终端，以及通过 SSH 连接到 Windows 的 PowerShell 会话，现在都会使用更稳的 sidecar 跟踪路径来判断命令何时真正结束
    • 这次改动特别照顾 Windows Server 2016 这类较老的 Windows 主机，重点解决这类环境里更常见的提示符噪声、PTY 行为不稳定、命令完成判断不准等问题
    • 命令结果会以更干净的“提示符 + 命令 + 输出”形式呈现，减少某些 Windows 主机上常见的 shellhost 噪声和 VT 控制序列污染
    • 打包后的 Windows 桌面版也补上了更稳的 node-pty 运行时处理，降低“应用能启动但 PTY 行为异常”的安装/打包问题
  • 按来源暂停或恢复监控
    • 现在可以直接在监控面板中，按本机或 SSH 目标分别暂停/恢复资源监控
    • 这个开关会跨重启保留，并跟随解析后的来源身份，所以重新连回同一台机器时不需要重新设置
    • 这样你可以把监控面板常开，但只持续采样你真正关心的来源
  • 终端搜索终于能稳定跟住当前标签页
    • 终端里的 Ctrl/Cmd+F 现在在切标签、重新绑定、布局重挂载之后，仍然会作用在当前 xterm 实例上
    • 命中数量和前后跳转也会始终和当前活动标签保持同步，不会再悄悄指向过期终端

兼容性 / 升级说明

  • 迁移过程中 GyShell 会主动阻塞启动，避免应用在历史只迁移了一半时就继续运行。
  • 迁移成功后，旧的 JSON 历史文件不会直接删除，而是保留为带时间戳的备份文件。
  • Windows Server 2016 是这次版本明确照顾的目标环境之一：v1.4.0 里关于 Windows 命令跟踪和输出清洗的工作，尤其就是为了提升这类较老 PowerShell 服务器环境下的可靠性。
Assets 11
Loading