Skip to content

patchloom: v0.9.0

Latest
Latest

Choose a tag to compare

View all tags
@patchloom-release patchloom-release released this 28 Sep 20:14
patchloom-v0.9.0
d661f1f
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Patchloom for VS Code 0.9.0

This release follows Patchloom CLI 0.37.0. Configure MCP lists the larger tool set, and a path that leaves the workspace through a symlinked folder is rejected.

Highlights

Recommended CLI is now 0.37.0. Configure MCP offers 66 tools, or a 12-tool core pack.

If a folder inside the workspace is a symlink to a directory outside it, a file that does not exist yet under that link is treated as outside the workspace. A missing file in a real folder inside the workspace is still accepted.

Minimum supported CLI remains 0.3.0. No settings migration is required.

New features

  • CLI 0.37.0 in Configure MCP. Full inventory is 66 tools, including notebook_edit and operation_schema. The core pack is 12 tools: the previous 11 plus operation_schema. The extension still talks to Patchloom over stdio. Notebook cell edits stay on the CLI and MCP; there is no new command-palette action for them (#285).
  • Troubleshooting for CLI 0.36 and 0.37. SEARCH/REPLACE matches when one side uses CRLF and the other uses LF. Extra stars after a Begin Patch marker are ignored. Setting a .properties or .ini value writes the text you typed, without added quotes. Replacing a markdown section keeps a body line that repeats the heading. A plan read can include the whole file's sha256, and a mismatched expected_sha256 is reported as stale. Tidying a directory includes dotfiles and still skips .git (#285).

Bug fixes

  • A missing file under a linked folder looked inside the workspace. If a directory in the workspace is a symlink to a folder outside it, a path to a file that does not exist yet under that link is now outside the workspace. Existing files that resolve outside stay outside. A missing file in a real in-workspace directory stays inside (#284).
  • Packaging the extension requires Node.js 22. @vscode/vsce 4 and Open VSX publishing need Node.js 22. The extension now says so in engines.node, so a package step on Node.js 20 fails on your machine instead of only in CI. The editor requirement is still VS Code 1.90 (#282, #277).

Numbers

Metric Previous Current
Extension version 0.8.0 0.9.0
Recommended CLI 0.35.0 (minimum still 0.3.0) 0.37.0 (minimum still 0.3.0)
MCP tools (CLI full / core) 64 / 11 66 / 12

Upgrading

  1. Update the extension to 0.9.0 (VS Code Marketplace, Open VSX, or .vsix from the GitHub Release).
  2. Update the Patchloom CLI using the channel that matches how the extension resolved it (see Patchloom: Show Status, Source):
# Managed install (extension storage): command palette
# Patchloom: Update Patchloom

# PATH via Scoop (preferred Windows PATH channel)
scoop update patchloom

# PATH via Homebrew
brew upgrade patchloom

# npm / cargo / shell installer: see README Install section
  1. Confirm with Patchloom: Show Status that the detected CLI is 0.37.0 or newer (0.3.0+ still runs; 0.37.0 is recommended). The 66-tool inventory and the 12-tool core pack need CLI 0.37.0+.
  2. Optional: run Patchloom: Configure MCP and choose Full or Core.

Install

Full changelog

patchloom-v0.8.0...patchloom-v0.9.0

Assets 4
Loading