GitFerry v0.4.2

Changelog

0.4.2 — 3 November 2026

• Ship Codex CLI registration instructions and a copyable TOML configuration, plus agent-assisted installation prompts for Codex and Claude Code.
• Clarify package installation, MCP registration, reconnection, and verification of tool discovery.
• Allow up to five minutes for npm processing after an accepted publication before failing release verification; retries preserve the exact published artifact.
• Update pinned npm/client examples and public release links to 0.4.2.

0.4.1 — 3 November 2026

• Publish through GitHub Actions using the configured npm trusted publisher, alongside MCP Registry metadata and checksummed GitHub release assets.
• Update public release links, npm installation instructions, and Claude Code, VS Code, Windows, and offline MCP setup examples.
• Stabilize slow Windows CI runs with longer timeouts for two Git integration tests that launch multiple processes.
• Document the trusted publisher scope and release maintenance procedure.

0.4.0 — 3 November 2026

• Separate MCP tool registration into an importable server factory; add architecture/deployment guides, client configuration examples, and an optional stdio Docker image.
• Prepare GitFerry for public npm distribution and MCP Registry discovery as io.github.mayank1307/gitferry.
• Support local stdio MCP through gitferry-mcp and gitferry mcp, with pack, inspect, and apply tools.
• Build fresh standalone CLI and MCP bundles whenever packing a release; ship installation, demo, and security documentation with npm.
• Add version/schema checks, isolated package installation checks, and CI for Node 22/24 on Linux, macOS, and Windows.
• Add a version-tag release workflow with npm and MCP Registry OIDC publishing, checksummed offline artifacts, and safe retries.
• Update MCP SDK, validation, compression, and test dependencies to patched versions.
• Harden bundle input validation, resource limits, repository writes, and concurrent apply behavior.

Node 22 or newer and Git 2.32 or newer are required. Existing bundle formats remain supported; malformed or unsafe bundles may now be rejected. Checksums establish integrity rather than sender identity. See SECURITY.md for scope and limitations.

GitFerry v0.4.1

Changelog

0.4.1 — 3 November 2026

• Publish through GitHub Actions using the configured npm trusted publisher, alongside MCP Registry metadata and checksummed GitHub release assets.
• Update public release links, npm installation instructions, and Claude Code, VS Code, Windows, and offline MCP setup examples.
• Stabilize slow Windows CI runs with longer timeouts for two Git integration tests that launch multiple processes.
• Document the trusted publisher scope and release maintenance procedure.

0.4.0 — 3 November 2026

• Separate MCP tool registration into an importable server factory; add architecture/deployment guides, client configuration examples, and an optional stdio Docker image.
• Prepare GitFerry for public npm distribution and MCP Registry discovery as io.github.mayank1307/gitferry.
• Support local stdio MCP through gitferry-mcp and gitferry mcp, with pack, inspect, and apply tools.
• Build fresh standalone CLI and MCP bundles whenever packing a release; ship installation, demo, and security documentation with npm.
• Add version/schema checks, isolated package installation checks, and CI for Node 22/24 on Linux, macOS, and Windows.
• Add a version-tag release workflow with npm and MCP Registry OIDC publishing, checksummed offline artifacts, and safe retries.
• Update MCP SDK, validation, compression, and test dependencies to patched versions.
• Harden bundle input validation, resource limits, repository writes, and concurrent apply behavior.

Node 22 or newer and Git 2.32 or newer are required. Existing bundle formats remain supported; malformed or unsafe bundles may now be rejected. Checksums establish integrity rather than sender identity. See SECURITY.md for scope and limitations.

GitFerry v0.4.0

GitFerry 0.4.0 brings portable Git change bundles to MCP clients, with local tools for packing, inspecting, and applying bundles across offline repositories.

Highlights

• Local stdio MCP server with pack_changes, inspect_bundle, and apply_bundle, available through gitferry-mcp or gitferry mcp.
• Named change selections and tracked-file snapshots for seeding or syncing another checkout.
• Reusable MCP server factory, deployment guides, client configuration examples, and an optional Docker image.
• Fresh standalone CLI and MCP bundles for offline installation.
• Hardened archive validation, resource limits, repository writes, local QR endpoints, and concurrent apply behavior.
• Cross-platform CI, version/schema checks, isolated package installation checks, and checksummed release artifacts.

Installation

npm install -g gitferry@0.4.0

Requires Node.js 22 or newer and Git 2.32 or newer. For offline use, download gitferry.cjs and/or gitferry-mcp.cjs below and run them with Node. SHA256SUMS covers every attached artifact. Existing bundle formats remain supported.

npm package · MCP Registry record

Checksums detect corruption, not sender identity. Review bundles before applying them; see SECURITY.md for trust boundaries and limitations.