Skip to content

ServerFS v0.23.3

Choose a tag to compare

@github-actions github-actions released this 29 Oct 15:01

ServerFS v0.23.3 — Release-Gated Native Windows Repo Ops

ServerFS v0.23.3 is the release-hygiene patch that completes the v0.23 Windows native Repo Ops rollout as a fully gated stable release.

The Windows product behavior introduced in v0.23.2 is retained unchanged: validated native Windows 11 x64 Repo Ops remains independently gated from Agent delegation, current-user/non-elevated, local-NTFS constrained, and fail-closed. v0.23.3 fixes the publication process defect exposed by v0.23.2, where root Ruff failures could coexist with a published GitHub Release because tag-time publication ran independently from the full cross-platform validation matrix.

Stable-release gate closure

Starting with v0.23.3, ServerFS stable publication is dispatch-first rather than tag-first:

  • the Release workflow is started explicitly on main with the intended vMAJOR.MINOR.PATCH tag;
  • the exact candidate SHA must pass Linux/Container + Agent Bridge + MCP conformance, Windows Native, Windows Agent, macOS Native, and Pages build gates;
  • after the gates complete, origin/main is checked again and any intervening main advance fails closed;
  • only the fully validated SHA may receive the lightweight stable tag;
  • wheels, the Agent Plugin, GitHub Release, and stable GHCR tags are downstream of that tag creation;
  • ordinary tag pushes no longer act as independent stable-release publishers.

This converts release discipline from a maintainer convention into an executable repository contract.

Windows Repo Ops baseline

v0.23.3 preserves the v0.23.2 native Windows containment and public MCP contract:

  • NTFS reparse points/junctions are rejected before Repo Ops execution;
  • Repo Ops children are assigned to the Bridge-owned Windows Job Object before execution;
  • timeout/cancellation/output-overflow cleanup proves descendant-tree termination before writer-lease release;
  • uncertain cleanup fails closed and preserves the writer lease until Bridge generation restart;
  • Git-for-Windows runs non-interactively with hardened fixed configuration;
  • the public surface remains exactly inspect_repo, run_repo_action, commit_repo_changes, and push_repo, with no generic shell or caller-controlled executable/argv/environment/remote/ref/force surface;
  • Repo Ops never falls back to Agent delegation.

The original Windows live acceptance remains recorded in v0.23.2 Windows Repo Ops acceptance. v0.23.3 publication additionally requires the full exact-SHA release matrix to be green before tag creation.

Platform boundary

  • Linux Host Bridge Repo Ops: v0.23.0+
  • Validated native Apple Silicon macOS Repo Ops: v0.23.1+
  • Validated native Windows 11 x64 Repo Ops: v0.23.2+

v0.23.3 does not expand the supported platform boundary; it makes that already validated Windows capability a clean, fully gated stable release.

Windows installation assets (Python >= 3.12; no Rust/MSVC/Docker required)

The three release wheels install into two isolated environments, matching the
frozen ServerFS/Agent-Bridge process boundary (the supervisor selects the Bridge
interpreter through SERVERFS_BRIDGE_PYTHON; the packages never share one dependency
graph):

file installs into sha256
serverfs_mcp-0.23.3-py3-none-any.whl ServerFS env 0bb4b845c5423603bf39ec74ee3e3fbbedd08ad640627caf9c0732443d9058fa
serverfs_windows_native-0.23.3-cp312-abi3-win_amd64.whl ServerFS env 5eb16aa74cd34ca20e234981adaf1dff7235f7898eeee446632afd6d38103c23
serverfs_agent_bridge-0.23.3-py3-none-any.whl Agent Bridge env 9acdd747df3bd06a5f443ab1f62c89b8619776cb7aca01c8ac7421b32f8b29d3

ServerFS environment (product + native kernel):

uv venv --python 3.12 .venv-serverfs
uv pip install --python .venv-serverfs/Scripts/python.exe https://github.com/NTLx/ServerFS_MCP/releases/download/v0.23.3/serverfs_mcp-0.23.3-py3-none-any.whl https://github.com/NTLx/ServerFS_MCP/releases/download/v0.23.3/serverfs_windows_native-0.23.3-cp312-abi3-win_amd64.whl

Agent Bridge environment (Bridge + provider SDKs; it must NOT contain the product):

uv venv --python 3.12 .venv-bridge
uv pip install --python .venv-bridge/Scripts/python.exe https://github.com/NTLx/ServerFS_MCP/releases/download/v0.23.3/serverfs_agent_bridge-0.23.3-py3-none-any.whl

Point the ServerFS supervisor at the Bridge interpreter (set this in the environment
that starts serverfs supervisor; it is not a provider setting and does not belong in
[agent] config):

$env:SERVERFS_BRIDGE_PYTHON = "<path>\.venv-bridge\Scripts\python.exe"

Verified native-wheel storage alternative:

serverfs bootstrap native-wheel --url "https://github.com/NTLx/ServerFS_MCP/releases/download/v0.23.3/serverfs_windows_native-0.23.3-cp312-abi3-win_amd64.whl" --sha256 5eb16aa74cd34ca20e234981adaf1dff7235f7898eeee446632afd6d38103c23