v0.4.0

What's new in v0.4.0: plugins

Forgecell can now use trackers, forges and reviewers other than GitHub through pinned MCP plugins (design: docs/design/2026-10-30-plugins-design.md).

• Plugin runtime. Plugins are pinned by SHA-256 in the Formula and run from a private copy. forgecell plugin list, plugin doctor and plugin test (contract checks, plus a read-only --live mode) let you inspect them.
• Keyed trackers. Labs that use a tracker plugin run the loop on keyed items, such as Jira-style keys, and the Lab UI's Issues view and loop work with them.
• Bundled plugins: GitLab (forge), Jira (tracker) and forgecomments, a reviewer that reads severity markers from review comments.
• Reviewer findings. forgecell findings --collect, fix rounds that revise the plan, a review gate before auto-push, and a Findings tab in the Lab UI.
• Contributor kit. forgecell plugin new scaffolds a Go, Python or TypeScript plugin. forgecell plugin pin computes the pins and prints the Formula plugins: line. The guide with a tested example tracker is lab/plugins/README.md.

Known limit: plugin pin refuses interpreters from Homebrew, because its prefix is group-writable. Use the system python3, or an interpreter under $HOME (pyenv, nvm or fnm). See the guide.

---

Native Forgecell CLI for macOS and Linux (amd64/arm64), with per-artifact SHA-256 files, MIT LICENSE and dependency notices. End users do not need Node, Go or source-repository access.

This is a draft release for review, not automatic publication. The rendered installer pins this exact version and its v-prefixed tag at DanielNetzer/forgecell. Approve public visibility and exact-head Actions results before draft review and approved publication. Verify anonymous install, upgrade and rollback before switching the documented legacy endpoint.

Installer activation smoke-checks the version and preserves Lab data. forgecell rollback restores the previous validated release. Running tickets requires Git, authenticated gh and a configured coding harness.

v0.3.1

Native Forgecell CLI for macOS and Linux (amd64/arm64), with per-artifact SHA-256 files, MIT LICENSE and dependency notices. End users do not need Node, Go or source-repository access.

This is a draft release for review, not automatic publication. The rendered installer pins this exact version and its v-prefixed tag at DanielNetzer/forgecell. Approve public visibility and exact-head Actions results before draft review and approved publication. Verify anonymous install, upgrade and rollback before switching the documented legacy endpoint.

Installer activation smoke-checks the version and preserves Lab data. forgecell rollback restores the previous validated release. Running tickets requires Git, authenticated gh and a configured coding harness.

v0.2.0-preview.2

Forgecell CLI preview, built from public source commit 801a9846fc9066dde985bb678348cac2bc89a249.

This is the first preview distributed from DanielNetzer/forgecell. Existing 0.2.0-preview.1 assets remain unchanged in the legacy release repository.

• Native macOS and Linux packages for arm64 and amd64; no Node, Go or source checkout needed for installation.
• Version-pinned install.sh, per-binary SHA-256 files, MIT LICENSE and dependency notices.
• Current core stores new local Lab records under ~/.forgecell/labs/. Existing Labs and approved Formulas are not silently migrated or rebound.
• Local ticket analysis, scope approval, coding/check evidence, reviewed draft-PR delivery and learning evidence. Merge, deployment and production verification remain operator actions.

Installation requires curl and standard shell/checksum tools. Running tickets additionally requires Git, authenticated GitHub CLI and an authenticated supported coding harness. Checksum files come from the same HTTPS endpoint; they are not independent signatures.

The exact source passed Linux/macOS CI. Release workflow 38026748067 passed full Go tests, vet, package builds and HTTPS install/upgrade/rollback tests. Four targets are cross-compiled; CI executes host architectures, not every architecture. Anonymous published-asset validation passed on macOS arm64: fresh and repeat installation, upgrade from 0.2.0-preview.1, rollback, and preservation of local Lab data. The installation command is available in the installation guide. This remains a prerelease.