Distribution

This chapter documents how Symposium is released and distributed across platforms.

Release Orchestration

Releases are triggered by release-plz, which:

1. Creates a release PR when changes accumulate on main
2. When merged, publishes to crates.io and creates GitHub releases with tags

The symposium-acp-agent-v* tag triggers the binary release workflow.

Distribution Channels

release-plz creates tag
        ↓
┌───────────────────────────────────────┐
│         GitHub Release                │
│  - Binary archives (all platforms)    │
│  - VSCode .vsix files                 │
│  - Source reference                   │
└───────────────────────────────────────┘
        ↓
┌─────────────┬─────────────┬───────────┐
│  crates.io  │   VSCode    │    Zed    │
│             │ Marketplace │Extensions │
│             │ + Open VSX  │           │
└─────────────┴─────────────┴───────────┘

crates.io

The Rust crates are published directly by release-plz. Users can install via:

cargo install symposium-acp-agent

VSCode Marketplace / Open VSX

Platform-specific extensions are built and published automatically. Each platform gets its own ~7MB extension containing only that platform’s binary.

See VSCode Packaging for details.

Zed Extensions

The Zed extension (zed-extension/) points to GitHub release archives. Publishing requires submitting a PR to the zed-industries/extensions repository.

Direct Download

Binary archives are attached to each GitHub release for direct download:

• symposium-darwin-arm64.tar.gz
• symposium-darwin-x64.tar.gz
• symposium-linux-x64.tar.gz
• symposium-linux-arm64.tar.gz
• symposium-linux-x64-musl.tar.gz
• symposium-windows-x64.zip

Supported Platforms

Secrets Required

The release workflow requires these GitHub secrets: