Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .printing-press.json
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
{
"api_name": "local-offload",
"cli_name": "local-offload",
"version": "0.229.0",
"version": "0.230.0",
"printing_press_version": "hand-built-2026-06-12",
"generated_at": "2026-06-12",
"description": "Local offload harness - delegate grunt work (summarize/classify/extract/triage, plus vision, OCR, transcription and media generation) to a free local Gemma-family cascade via llama.cpp; MCP + CLI; the cascade never calls cloud and defers to the caller instead. The opt-in offload_nim tool is the only remote model surface; the opt-in offload_browse lane drives the operator's own browser with typed choices from a loopback decision endpoint the operator runs.",
Expand Down
9 changes: 9 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,15 @@ Releases before 0.190.0 are archived verbatim under [docs/changelog/](docs/chang

## [Unreleased]

## [0.230.0] - 2026-11-11 - release: 0.230.0

### Fixed - a Windows swap sees a node started through a junction

- **Why.** On Windows, llama-swap's live directory is a junction into its generation directory (`<home>/llama-swap` -> `<home>/llama-swap-versions/<id>`). The process finder compared the path CIM reports, which is the path the process was started through (the junction), with the generation path the swap names, by spelling. The two never matched. Measured on a Windows node: the swap restarted llama-swap, and both the post-restart check and the rollback's check reported "no process appeared" against a running node.
- **What it does.** The finder fetches processes by file name and then matches a path by the file it names (`os.SameFile`). It still accepts an exact spelling. A junction or symlink on either side, or a short 8.3 name, now matches. A process whose path the OS will not give is still returned as unreadable, as before. The Linux finder already resolved links.
- **Where.** `internal/nodeswap/deps_windows.go` (`findProcessesByExeWindows`, `sameExecutable`).
- **Check.** One Windows test starts a real process through a junction and asks the finder for both the junction path and the generation path. On the old code it fails ("not found in []"); with the fix it passes.

## [0.229.0] - 2026-11-11 - release: 0.229.0

### Fixed - an engine swap run under `gpu reserve` no longer waits for its own lease
Expand Down
2 changes: 1 addition & 1 deletion VERSION
Original file line number Diff line number Diff line change
@@ -1 +1 @@
0.229.0
0.230.0
6 changes: 0 additions & 6 deletions changes/unreleased/fix-windows-finder-follows-junctions.md

This file was deleted.

2 changes: 1 addition & 1 deletion internal/buildinfo/buildinfo.go
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ import (
// `version` const aliases it (keeping the VERSION-file agreement test in
// main_test.go binding), and fleet/pipeline stampers read it directly so no
// plumbing carries it through config.
const Version = "0.229.0"
const Version = "0.230.0"

var (
buildOnce sync.Once
Expand Down
Loading