Skip to content

ServerFS v0.23.0

Choose a tag to compare

@github-actions github-actions released this 26 Oct 07:55

ServerFS v0.23.0 — Deterministic Repo Ops

v0.23.0 adds a generic, deterministic repository-operations surface for opted-in Linux ServerFS workdirs. The new capability is deliberately separate from Agent delegation: ChatGPT or another MCP client can finish bounded repository work without receiving a shell and without submitting a server-side AI Agent task.

Highlights

  • Four public Repo Ops tools: inspect_repo, run_repo_action, commit_repo_changes, and push_repo.
  • Independent per-workdir gate via WORKDIR_XX_REPO_OPS_ENABLED=true; Repo Ops can be enabled while Agent mode remains disabled.
  • Deterministic named actions use operator-owned fixed policy, mandatory SHA-256 integrity pins, a narrow child environment, bounded execution, and the shared writer lease.
  • Hardened Git commit/push paths: explicit commit paths only, no pre-existing staged state, external content filters rejected, hooks/signing disabled on the deterministic path, and push restricted to the derived current upstream with one exact refspec.
  • Fixed npm release actions are supported for operator-configured npm/package.json repositories: release_tag can create/push a validated release tag at the captured clean main HEAD after matching the root package.json version, and publish_npm can dispatch one fixed GitHub Actions publication workflow without exposing generic Git/workflow arguments. These built-ins are intentionally narrower than the repository-generic Repo Ops surface.
  • No Agent fallback: Repo Ops never selects a model/runtime, creates an Agent task/session, or invokes a provider adapter.

Security boundary

Repo Ops does not add a generic shell, command executor, caller-controlled executable/argv/environment, arbitrary remote/ref selection, or force semantics. All caller paths pass ServerFS policy, the Host Bridge independently confines host paths, and every named action verifies operator-pinned repository inputs immediately before execution while holding the existing writer lease.

The v0.23.0 Repo Ops release scope is Linux Host Bridge deployments. Native Windows/macOS Repo Ops enablement is not claimed. Existing Windows/macOS filesystem and Agent deployment contracts remain supported and were regression-tested for this release.

Validation

Release acceptance includes:

  • Linux user-scoped bootstrap/internal E2E: PASS;
  • public ChatGPT MCP Repo Ops E2E: PASS (actions → status → named validation → explicit diff → explicit-file commit → current-upstream push) with no Agent task;
  • complete root project Ruff/format/test gate: PASS;
  • complete Agent Bridge Ruff/format/test gate: PASS;
  • Agent Skills/Plugin, MCP Registry, Compose and MCP conformance gates: PASS;
  • Windows Native and Windows Agent workflows: PASS;
  • macOS Native MCP and Agent Bridge workflows: PASS;
  • post-documentation-freeze Astro/GitHub Pages build and deploy: PASS.

Detailed evidence is tracked in docs/v0.23.0-linux-repo-ops-bootstrap-acceptance-2026-10-26.md and docs/v0.23.0-release-checklist-2026-10-26.md.

Upgrade notes

Production Linux deployments should pin ghcr.io/ntlx/serverfs_mcp:0.23.0. Repo Ops remains disabled unless explicitly enabled for a workdir. Enabling Repo Ops requires the authenticated Host Bridge transport (compose.agent.yml on Linux) but does not require enabling an Agent runtime.

When configuring named actions, treat integrity-pin updates as an explicit operator review decision. Do not automatically refresh a pin in the same task that changed the pinned repository code.

The published release attaches the product wheel, Agent Bridge wheel, Windows native abi3 wheel, and the skills-only serverfs-plugin-v0.23.0.zip; their SHA-256 values were appended automatically to the GitHub Release body by the tag workflow.

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.0-py3-none-any.whl ServerFS env c81f834aeaf43bd548954b660cdb447a50af9ec16ef3f9cc822c88f769720ed5
serverfs_windows_native-0.23.0-cp312-abi3-win_amd64.whl ServerFS env 69310a0d326bad11e32cd9b2154b2b4baef3c8ae96de72fc893731817713c95b
serverfs_agent_bridge-0.23.0-py3-none-any.whl Agent Bridge env c781b21f4ffa6ebc29a6b5095824fb3ba5ff5594ae039c3fb9decf73ec54acc6

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.0/serverfs_mcp-0.23.0-py3-none-any.whl https://github.com/NTLx/ServerFS_MCP/releases/download/v0.23.0/serverfs_windows_native-0.23.0-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.0/serverfs_agent_bridge-0.23.0-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.0/serverfs_windows_native-0.23.0-cp312-abi3-win_amd64.whl" --sha256 69310a0d326bad11e32cd9b2154b2b4baef3c8ae96de72fc893731817713c95b