Skip to content

v0.4.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 03 Nov 17:18
· 9 commits to main since this release
v0.4.0
721ef75
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

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.

Assets 14
Loading