Skip to content

chore: tracking placeholder for linux/arm64 service agents (Refs #346) - #348

Merged
antoinetoussaint-byte merged 2 commits into
mainfrom
issue-346-release-linux-arm64-for-all-service-agents-multi
Aug 23, 2026
Merged

chore: tracking placeholder for linux/arm64 service agents (Refs #346)#348
antoinetoussaint-byte merged 2 commits into
mainfrom
issue-346-release-linux-arm64-for-all-service-agents-multi

Conversation

@antoinetoussaint-byte

@antoinetoussaint-byte antoinetoussaint-byte commented Aug 23, 2026

Copy link
Copy Markdown
Contributor

Refs #346. (Deliberately not Closes — the actionable work is cross-repo; this PR must not auto-close the tracking issue.)

Status: tracking placeholder — empty diff

Core needs no code change for linux/arm64. Its agent downloader and every store (OCI/HTTP/Nix) already resolve assets via runtime.GOOS/runtime.GOARCH, and the CLI self-updater already handles EM_AARCH64/CpuArm64. On an arm64 Linux host, core already requests service-<name>_<version>_linux_arm64.tar.gz — the asset just 404s today because publishers don't emit it yet.

An earlier revision added a test to "pin" this, but the download path has no arch-dependent branching (GitHubAsset is a plain fmt.Sprintf), so the assertion was tautological and caught nothing the existing host-platform test doesn't. It was reverted; the branch now carries no diff and exists only to track #346 from this repo.

Remaining work (all cross-repo, none in core)

  • Add the linux-arm64 goreleaser build + cut a release in each service-* repo: service-go, service-python, service-nextjs, service-rust, service-swift, service-generic.
  • Bump the pins in cli pkg/sourceworkspace/source.go if versions roll.
  • Broaden the --platform linux/amd64 companion pin in cli companions.yaml once agents publish arm64.

Close this PR once the releases land, or repurpose the branch if a genuine core-side change surfaces.

antoinetoussaint-byte and others added 2 commits August 23, 2026 17:53
Core's downloader already resolves agent assets via runtime.GOOS/GOARCH,
so it targets service-<name>_<version>_linux_arm64.tar.gz on arm64 Linux
without change. No CI host builds on linux/arm64, so the existing
host-platform test never exercises that asset name.

Extract downloadURLForPlatform so the platform is a parameter, and add a
regression test asserting core requests the exact linux_arm64 asset the
service-* release matrices must publish.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…act (#346)"

This reverts the no-op change from 9ba33c9.

Self-review found the added test tautological: the download path has no
arch-dependent branching (GitHubAsset and the extracted helper are plain
fmt.Sprintf), so asserting linux/arm64 specifically catches nothing the
existing host-platform test doesn't — os and arch are interpolated
identically regardless of value. The downloadURLForPlatform extraction
existed only to feed that tautology, so it goes with it.

Core's downloader is already architecture-agnostic (runtime.GOOS/GOARCH),
so it needs no change for arm64 Linux. The actionable work for #346 lives
in the service-* release matrices and the cli pins, not this repo.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@antoinetoussaint-byte

Copy link
Copy Markdown
Contributor Author

Closing as no-op. Reverted to empty after self-review: core's downloader is already architecture-agnostic, so there was no non-tautological core-side change to make for #346. The actionable work (service-* releases + cli pins) is cross-repo — tracked in #346, which stays open. See the issue comment for the redirect.

@antoinetoussaint-byte antoinetoussaint-byte changed the title test: pin linux/arm64 service-agent downloader contract (#346) chore: tracking placeholder for linux/arm64 service agents (Refs #346) Aug 23, 2026
@antoinetoussaint-byte
antoinetoussaint-byte merged commit f16dc1e into main Aug 23, 2026
1 of 2 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