DiffRail v0.2.1
Publication-ready packaging for the existing change-boundary checker. No policy format or checker behavior changes.
What's included
- Matching CLI and plugin versions, updated installation commands, and release packaging checks.
- Branded listing metadata for portable plugins and Cursor, with explicit CLI and local repository requirements.
- Standalone CLI archives for Windows x64, Linux x64, macOS Intel, and macOS Apple Silicon. Git is required; Rust is not required to run these binaries.
- A skills-only plugin ZIP containing manifests, the skill, documentation, and the listing icon. It does not install the CLI or include an MCP server.
- SHA256SUMS for the downloadable archives.
- Cross-platform release builds and isolated installation smoke tests.
Install the CLI
Download the archive matching your platform below, verify its SHA-256 against SHA256SUMS, extract it, and put the executable on your PATH. On macOS and Linux, retain executable permissions (chmod +x diffrail if needed).
The Linux archive requires GNU/glibc 2.35 or newer; Alpine/musl is not supported by that archive. Downloads are unsigned and not notarized, so Windows or macOS may request approval before running them.
Alternatively, with Git and Rust 1.85 or newer:
cargo install --git https://github.com/beriktassuly/diffrail --tag v0.2.1 --locked
diffrail --versionThe crates.io package is published separately. This release does not claim that cargo install diffrail or official plugin-directory listings are already available.
Plugin installation
Install the CLI first. Claude Code users can add beriktassuly/diffrail as a marketplace and install diffrail@diffrail. Codex users can run:
codex plugin marketplace add beriktassuly/diffrail --ref v0.2.1
codex plugin add diffrail@diffrailFor Cursor, local installation and official marketplace submission are described in the README. The release ZIP can be used for a skills-only plugin submission; approval and public listing are separate from this GitHub release.
Limits
DiffRail checks file boundaries. It is not a sandbox, does not authenticate task assignment, and does not detect semantic conflicts or replace tests. A failing CI check blocks merge only when the repository requires that status check.