Skip to content

Releases: 1dao/codeoutline

v0.2.6

Choose a tag to compare

@1dao 1dao released this 21 Oct 16:36

Full Changelog: v0.2.5...v0.2.6

v0.2.4

Choose a tag to compare

@1dao 1dao released this 15 Oct 14:37

Full Changelog: v0.2.3...v0.2.4

v0.2.1

Choose a tag to compare

@1dao 1dao released this 13 Oct 13:08

Full Changelog: v0.2.0...v0.2.1

v0.2.0

Choose a tag to compare

@1dao 1dao released this 10 Oct 14:38

Full Changelog: v0.1.9...v0.2.0

v0.1.9

Choose a tag to compare

@1dao 1dao released this 03 Oct 18:15

Full Changelog: v0.1.8...v0.1.9

v0.1.8

Choose a tag to compare

@1dao 1dao released this 03 Oct 17:41

Full Changelog: v0.1.7...v0.1.8

v0.1.5

Choose a tag to compare

@1dao 1dao released this 02 Oct 15:44

Full Changelog: v0.1.4...v0.1.5

v0.1.4

Choose a tag to compare

@1dao 1dao released this 02 Oct 14:49

Full Changelog: v0.1.3...v0.1.4

v0.1.3

Choose a tag to compare

@1dao 1dao released this 02 Oct 11:37

CodeOutline can now update itself with signed releases.

Added

  • codeoutline update --check, codeoutline update and codeoutline update --rollback. Updates are installed under ~/.codeoutline/updates (the user profile on Windows).
  • serve checks for an update before it starts. A verified update applies to the new process; running services are not touched. If the check fails, the local version is used.
  • Every update is verified before it is activated: the signature against the public key shipped in the package, file hashes, platform, version, sequence number, and a runtime health check.
  • Set CODEOUTLINE_AUTO_UPDATE=0 to turn off automatic checks; manual codeoutline update still works.

Notes

  • Earlier versions do not contain the updater. Upgrade once through npm or GitHub Releases; later versions can then update themselves.
  • Self-updates do not change the version npm records. codeoutline --version reports the version that is actually running.
  • Rollback switches between the two installed versions; after the first update it returns to the npm-installed version.

Upgrade

npm install -g codeoutline@latest

简体中文

CodeOutline 现在可以通过签名发布自动更新。

新增

  • codeoutline update --check、codeoutline update 与 codeoutline update --rollback。更新安装在 ~/.codeoutline/updates(Windows 为用户目录下)。
  • serve 启动前检查更新。验证通过的更新作用于新启动的进程,已在运行的服务不受影响;检查失败时继续使用本地版本。
  • 每个更新在启用前都会校验:用安装包内置公钥验证签名,并检查文件哈希、平台、版本、序号,以及运行时自检。
  • 设置 CODEOUTLINE_AUTO_UPDATE=0 可关闭自动检查,手动 codeoutline update 仍然可用。

说明

  • 旧版本不包含更新器,需要通过 npm 或 GitHub Releases 升级一次,之后即可自动更新。
  • 自动更新不会改变 npm 记录的版本号,codeoutline --version 显示的是实际运行的版本。
  • 回滚在已安装的两个版本之间切换;第一次更新后回滚,会回到 npm 安装的版本。

升级

npm install -g codeoutline@latest

v0.1.2

Choose a tag to compare

@1dao 1dao released this 01 Oct 16:45

One local HTTP service can now serve every project on the machine.

Changed

  • A loopback serve --http started without --allow-root no longer limits projects to its start directory, so one shared service works for every session, even across drives. Only local processes can reach it, and they already have the user's file access. Stdio and remote HTTP keep their defaults (--project or the start directory).
  • The README now recommends one shared HTTP service instead of a stdio server per session, and a global install instead of npx -y, which keeps an npm process resident beside every server.

Fixed

  • An --allow-root path that does not exist at startup, such as an unmounted drive, aborted the service. It now logs a warning, and the path becomes accessible once it exists.

Upgrade

npm install -g codeoutline@latest

The native runtime is unchanged from 0.1.1; only the Lua implementation changed.


简体中文

一个本机 HTTP 服务现在可以服务本机所有项目。

变更

  • 本机监听的 serve --http 未传 --allow-root 时不再限制项目目录,一个共享服务即可服务所有会话,项目分布在不同盘上也可以。只有本机进程能连到它,这些进程本来就有用户的文件访问权限。stdio 与远程 HTTP 的默认范围不变(--project 或启动目录)。
  • README 改为推荐共享一个 HTTP 服务,而不是每个会话各启动一个 stdio 服务;安装改为全局安装,不再使用 npx -y,因为 npx 会在每个服务旁常驻一个 npm 进程。

修复

  • --allow-root 指向的目录在启动时不存在(如未挂载的盘)会导致服务启动失败。现在只输出警告,目录出现后即可访问。

升级

npm install -g codeoutline@latest

原生运行时与 0.1.1 相同,仅 Lua 实现有变化。