Releases: FFatTiger/lore
Releases · FFatTiger/lore
Release list
v1.3.23
Highlights
- Added an interactive, default-No risk confirmation before sending an API token to a non-loopback server over plain HTTP.
- Added
--allow-insecure-httpfor explicit parameter-mode approval when insecure HTTP is unavoidable.
Fixed
- Kept token transport secure by default: non-loopback HTTP remains blocked unless separately authorized, and
--yesdoes not imply approval. - Ensured insecure HTTP authorization applies only to the current run and is never persisted to Lore configuration.
Changes
- Documented the insecure HTTP risk, the explicit flag, and the safer HTTPS default in the CLI and project READMEs.
- Added regression coverage for interactive approval and rejection, parameter mode,
--yes, transport validation, and non-persistence; the CLI suite now contains 182 tests.
Full Changelog: v1.3.22...v1.3.23
v1.3.22
Highlights
- Added first-class Windows support to the
npx @loremem/cliinstaller, validated on both Windows and Ubuntu. (changes)
Fixed
- Fixed Windows command detection and execution for npm-installed
.cmdand.batagent CLIs. (changes) - Fixed Windows installations requiring external
curl,unzip, Bash, or Unix symlink tooling; artifacts now use Node-native download and ZIP extraction, and Pi uses a Windows directory junction. (changes) - Fixed Claude Code and Codex hook commands for Windows paths and user directories containing spaces. (changes)
- Fixed the interactive reinstall flow incorrectly showing “Cancelled” when a runtime was detected but no plugin had completed installation. (fix)
Changes
- Added Windows and Ubuntu CLI gates before npm publication, including typechecking, 173 tests, and production builds. (workflow)
- Added automated npm prerelease and stable publication through GitHub Releases.
- Updated release version synchronization to include the CLI manifest and lockfile. (release script)
Full Changelog: v1.3.21...v1.3.22
v1.3.22-pre.4
Highlights
- Fixed Windows Pi installation and the interactive reinstall flow when no plugin has completed installation yet. (changes)
Fixed
- Fixed Windows installs incorrectly calling system
unzip; release artifacts now use Node-native download and ZIP extraction in production. (fix) - Fixed “Update selected plugins” incorrectly showing “Cancelled” when a runtime such as Pi was detected but no plugin had been installed successfully. (fix)
Changes
- Added regression coverage for the production artifact path and the no-installed-plugins interactive flow.
- Bumped all runtime, plugin, server, and CLI manifests to
1.3.22-pre.4. (release)
Full Changelog: v1.3.22-pre.3...v1.3.22-pre.4
v1.3.22-pre.3
Highlights
- Completed Windows support and cross-platform validation for the
npx @loremem/cliinstaller. (changes)
Fixed
- Fixed the final Windows Codex cache-path normalization case and Windows command-shim regression uncovered by the GitHub Actions matrix. (fix)
Changes
- Validated CLI typechecking, 172 tests, and production builds on both Ubuntu and Windows before this prerelease.
- Bumped all runtime, plugin, server, and CLI manifests to
1.3.22-pre.3for npm prerelease publication through GitHub Actions. (release)
Full Changelog: v1.3.22-pre.2...v1.3.22-pre.3
v1.3.22-pre.2
Highlights
- Completed the cross-platform CLI validation pass for Windows and Ubuntu before npm publication. (changes)
Fixed
- Fixed Codex installer tests and hook path generation across Windows path separators and command shims. (fix)
- Fixed platform-specific test assumptions around POSIX file modes and Windows-invalid quoted path segments. (fix)
- Fixed legacy hook installation tests so their explicit environment includes the generated Codex executable. (fix)
Changes
- Disabled matrix fail-fast so Ubuntu and Windows always report complete validation results.
- Made manual CLI workflow runs validation-only; npm publication remains tied to GitHub Release events.
Full Changelog: v1.3.22-pre.1...v1.3.22-pre.2
v1.3.22-pre.1
Highlights
- Added first-class Windows support to the
npx @loremem/cliinstaller and validated the CLI on both Ubuntu and Windows runners. (changes)
Fixed
- Fixed command detection so installer operations use their explicitly supplied
PATHinstead of accidentally depending on commands installed on the host or CI runner. (fix) - Fixed the non-interactive update regression test by providing its own cross-platform Pi command shim, making local and GitHub Actions results deterministic. (test)
Changes
- Bumped all runtime, plugin, server, and CLI manifests to
1.3.22-pre.1for an end-to-end prerelease and npm publishing verification. (release)
Full Changelog: v1.3.22-pre.0...v1.3.22-pre.1
v1.3.22-pre.0
Highlights
- Added first-class Windows support to the
npx @loremem/cliinstaller, including Windows command shims, native artifact handling, and Pi extension junction installation. (changes)
Fixed
- Fixed agent CLI detection and process launching on Windows where npm-installed tools are exposed through
.cmdor.batshims. (changes) - Fixed installation on Windows systems without Unix
curl,unzip, Bash, or symlink tooling by using Node-based downloads, ZIP extraction, and directory junctions. (changes) - Fixed Claude Code and Codex lifecycle hook commands for Windows paths, shell syntax, and user directories containing spaces. (changes)
Changes
- Added Ubuntu and Windows CLI validation before npm publication, with prereleases published under the npm
predist-tag. (workflow) - Added ZIP traversal protection and expanded cross-platform regression coverage for downloads, command shims, Pi installation, and hook definitions. (tests)
- Updated the release script to keep the CLI manifest and lockfile aligned with repository release versions. (release script)
Full Changelog: v1.3.21...v1.3.22-pre.0
v1.3.21
Highlights
- 发布 Lore
v1.3.21:交互式安装器采用新的 Clack 终端体验与 figlet 品牌横幅。(978231b)
Fixed
- 升级
@clack/prompts至^1.7.0,修复旧版本在含 CJK 文本和 ANSI 颜色时计算显示宽度错误、导致状态框边框错位的问题。(978231b) - 交互式流程中按
Ctrl+C或 Esc 现在会以退出码 130 正常退出,不再输出Error: Aborted调用栈。(978231b)
Changes
@loremem/cli、GitHub Release 和运行时 artifacts 统一版本为1.3.21。(d4e99be)- 安装器使用 figlet
ANSI Shadow品牌横幅,并将状态信息压缩为连接与运行时摘要;完整详情可通过loremem status查看。(978231b)
Full Changelog: v1.3.15...v1.3.21
v1.3.15
Highlights
- Promotes the OpenCode 1.18.3 native integration to the stable
v1.3.15release, including the exact tenlore_*tools, system Boot context, and per-prompt Recall. (OpenCode integration)
Fixed
- Prevents duplicate Lore MCP tools when Claude compatibility layers import legacy Lore MCP configuration into OpenCode. (runtime MCP suppression)
- Prevents duplicate Claude Lore lifecycle hooks while preserving JSONC comments, unrelated settings, user overrides, and reversible uninstall state. (installer compatibility fix)
Changes
- Publishes all plugin and runtime manifests as stable version
1.3.15. (release commit) - Keeps
LORE_OPENCODE_ALLOW_MCP=1as the explicit escape hatch for users who intentionally want legacy Lore MCP imports alongside the native plugin. (documentation)
Full Changelog: v1.3.13...v1.3.15
v1.3.15-pre.4
Highlights
- OpenCode 1.18.3 now keeps the exact ten native
lore_*tools while suppressing duplicate Lore integrations imported through Claude compatibility layers. - Native Boot system context and per-prompt Recall were validated end-to-end against production SaaS with a single
client_type=opencodeprompt query.
Fixed
- Remove legacy Lore
/api/mcpentries from OpenCode's merged runtime configuration without affecting non-Lore MCP servers. - Prevent
oh-my-openagentand legacyoh-my-opencodefrom importing the Claude Lore plugin lifecycle hooks alongside the native OpenCode integration. - Preserve JSONC comments, unrelated settings, user overrides, and reversible rollback state when applying the narrow compatibility edit.
- Make release asset uploads immutable by refusing to overwrite an existing asset.
Changes
- The OpenCode installer records its compatibility edit under
~/.lore/opencode-compat.jsonand restores it during uninstall when the user has not changed the value afterward. LORE_OPENCODE_ALLOW_MCP=1opts out of both runtime MCP filtering and the installer compatibility edit.- OpenCode prerelease documentation and managed plugin version now point to
v1.3.15-pre.4.