Skip to content

feat(release): publish CLI archives to the fork's GitHub Release and update from it - #2

Merged
SeasonsChange422 merged 2 commits into
mainfrom
feat/fork-cli-release
Oct 14, 2026
Merged

SeasonsChange422 merged 2 commits into
mainfrom
feat/fork-cli-release

Conversation

@SeasonsChange422

Copy link
Copy Markdown
Member

Summary

The release job was gated to the upstream owner, so this fork never produced CLI archives, and multica update plus the install scripts only read upstream releases. Users therefore could not receive daemon-side fixes such as the Graph cancel stop-evidence fix shipped server-side in v0.1.2.

  • release.yml: run GoReleaser on this repository too, skipping Homebrew (the tap is upstream-only). The desktop job stays upstream-only.
  • .goreleaser.yml: bake the building repository into the CLI (cli.DefaultReleaseRepo) so multica update reads releases from where the binary was built.
  • update.go: MULTICA_RELEASE_REPO overrides the release repository at runtime.
  • install.sh / install.ps1: MULTICA_RELEASE_REPO selects the download repository; Homebrew is skipped when it is set.

Verification

  • New unit test for the default and the override; go test ./internal/cli -run 'ReleaseAPIURL|Update' passes.
  • bash -n scripts/install.sh passes.

Not verified

  • GoReleaser config was not run locally; the first release after merge is the real test.
  • install.ps1 was not executed.
  • The web /download page and landing install command still point upstream (not changed here).
  • Already-installed CLIs built upstream keep reading upstream releases until reinstalled or MULTICA_RELEASE_REPO is set.

Test plan

  • After merge, the next tag produces CLI archives and checksums.txt on this repository's Release
  • MULTICA_RELEASE_REPO=Time-Machine-Lab/Stein-AI multica update finds that release
  • The desktop and Homebrew steps are skipped on this repository

🤖 Generated with Claude Code

…update from it

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

The release job was gated to the upstream owner, so the fork never produced CLI archives, and `multica update` plus the install scripts read upstream releases only.

- release.yml: run GoReleaser on the fork (Homebrew skipped), keep desktop upstream-only
- goreleaser: bake the building repository into the CLI as the update source
- update.go: MULTICA_RELEASE_REPO overrides the release repository at runtime
- install.sh/install.ps1: MULTICA_RELEASE_REPO selects the release repository; Homebrew is skipped when set
…itory's releases

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Add a single RELEASE_REPO constant and use it for the latest-release fetch, the all-releases link and the install command (which now sets MULTICA_RELEASE_REPO).
@SeasonsChange422
SeasonsChange422 merged commit 5f5f88a into main Oct 14, 2026
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant