Skip to content

SwarmForge v0.1.3

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 09 Oct 02:08
v0.1.3
45c29d3

SwarmForge v0.1.3

This release packages the GitHub repository authorization and onboarding changes already on public master, adds the reviewed public documentation, and fixes MCP version reporting. It retains the existing self-hosted OpenCode/Freestyle execution model. Phase 2 cloud accounts, CLI linking, worker enrollment, and unpublished Phase 1 runtime changes are excluded.

Changes since v0.1.2

  • GitHub OAuth repository access: swarmforge github login uses GitHub Device Flow, verifies repository push access, and stores repository-bound credentials privately. Initialization can opt into authenticated clone and verified branch push with github-oauth mode. This requires your OAuth App Client ID with Device Flow enabled and uses GitHub's broad repo scope; see the access and revocation details.
  • Clearer setup and developer onboarding: the README explains distributed workers, current harness/model/provider support, architecture, task handoff, licensing, and installation troubleshooting. The release quickstart selects a dedicated configuration. CONTRIBUTING.md provides local tests without provider credentials, and the snapshot checklist documents guest tools, systemd, filesystem, and networking requirements.
  • Consistent release identity: MCP server and CLI-client handshakes use the application/build version instead of reporting a fixed 0.1.0.
  • Stable dashboard revisions after OAuth discovery: credential-screening metadata is synchronized before a dashboard revision is captured, so an unchanged poll stays unchanged after newly discovered repository credentials are recorded.
  • Regression coverage: dedicated tests cover GitHub authorization scope, polling, denial, credential permissions, repository binding, and push access. HTTP tests verify version reporting during real MCP handshakes.

The public base is 9f2953e73a5ebc2c0af20bb6e166c5980fb0a089. Documentation was adapted from fec66971536cb117b36c85faabd98883d6491cb2 in integration commit b0798b3; GitHub OAuth regression tests were selectively imported from d284bf33e11a7a431d2d49db8e43572accd4e7d0 in 821dea9, with the permission assertion corrected before release. The dashboard fix backports only the self-hosted runtime and regression-test hunks from b93e64f90348cf992f1b7c29532c66999bc46cf2; its cloud test changes are excluded. See the full comparison.

Install or upgrade

Linux x64 with glibc, Bash, curl, GNU tar, and coreutils are required. Bun is embedded in the executable; it is not required on the installation host.

curl -fsSL https://getswarmforge.tech/install -o install-swarmforge.sh
bash install-swarmforge.sh --version 0.1.3 --install-only

For a new deployment, follow the README quickstart. For an upgrade, keep the existing database, artifact storage, environment/configuration files, and instance ID. Installation does not restart a running server. Restart swarmforge serve deliberately and reconnect MCP clients to load the new executable and tools.

Workers still require your prepared Freestyle snapshot and a reachable OpenAI-compatible tool-calling model endpoint. VM and inference charges are separate from the coordinator installation.

Artifacts and checksums

Required release assets:

  • swarmforge-v0.1.3-linux-x64-glibc.tar.gz
  • swarmforge-v0.1.3-linux-x64-glibc.tar.gz.sha256
  • SHA256SUMS
  • metadata-0.1.3.json
  • LICENSE

Download the archive and its external checksum together, then run:

sha256sum -c swarmforge-v0.1.3-linux-x64-glibc.tar.gz.sha256

The archive contains exactly swarmforge, SHA256SUMS, and metadata-0.1.3.json. After extraction, sha256sum -c SHA256SUMS verifies the executable. Metadata records the version, build commit, platform, runtime options, and checksum. swarmforge --version reports 0.1.3; help reports the build commit and license URL. SHA-256 verifies content integrity; the installer does not verify a publisher signature.

Validation scope

Release checks use Bun 1.4.2: frozen dependency installation, TypeScript/Biome, the ordinary regression suite (592 passed, 2 skipped, 0 failed; 3,661 assertions), standalone compilation, packaging, tag/version validation, and archive verification. Skips are the opt-in live infrastructure smoke test and an absence-only lifecycle placeholder. Installation checks run the executable without Bun or a checkout on PATH. Local readiness, terminal initialization, dedicated configuration selection, server startup, status, and MCP discovery use disposable credentials and a local VM-inventory fixture.

These checks do not certify a customer's snapshot or exercise live model inference, GitHub authorization, Git push, or remote worker provisioning. Run the documented first task against your own infrastructure before assigning coding work.

Licensing

The unmodified PolyForm Small Business License 1.0.0 remains in force. Permitted business use requires both fewer than 100 employees and independent contractors and prior-tax-year total revenue below US$1,000,000 in 2019 dollars, adjusted for inflation under the license's specified CPI series. Controlled and commonly controlled organizations are included in its company definition. Business use outside those permissions requires separate permission. This is source-available software; third-party components retain their own licenses.

Assets 7
Loading