Skip to content

Use the orka CLI name for Orka 4.0, keep 3.x builds working - #78

Merged
celanthe merged 2 commits into
mainfrom
update/orka-cli-rename
Oct 27, 2026
Merged

celanthe merged 2 commits into
mainfrom
update/orka-cli-rename

Conversation

@celanthe

@celanthe celanthe commented Oct 8, 2026 •

Copy link
Copy Markdown
Collaborator

Orka 4.0 renames the CLI from orka3 to orka and moves its artifacts to the orka/ S3 path (OK-6390). Tracked in DI-753.

Changes

  • pkg/orka/client.go calls orka through one cliBinary constant.
  • Dockerfile: downloads from orka/ for 4.x and orka3/ for 3.x, based on ORKA_VERSION, and installs as orka with an orka3 symlink. Default is now 4.0.0 (was 3.1.0).
  • Fixes the linux/arm64 image shipping an x86 CLI. The download now uses TARGETARCH.
  • CI, README, examples/.env use orka and 4.0.0.

Testing

go vet, go build, and go test pass. Ran the download step against the 3.6.3 amd64 and arm64 artifacts. The 4.0.0 artifacts are published.

Merge

Orka 4.0 is out (the 4.0 docs are live), so this can merge as soon as it's reviewed. CI tags images from a single ORKA_VERSION, so 3.6 customers need either a 3.x image line or a note on which image goes with which Orka version.

GitLab and Buildkite: macstadium/orka-integrations#71.

🤖 Generated with Claude Code

Orka 4.0 renames the CLI from orka3 to orka and moves its artifacts to the
orka/ S3 path (OK-6390). The client calls orka through one constant. The
Dockerfile picks the path from ORKA_VERSION, installs the build as orka with
an orka3 symlink, and downloads the CLI for TARGETARCH instead of always
amd64, which put an x86 binary in the arm64 image. Default and CI CLI
version is now 4.0.0. Tracked in DI-753.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@celanthe celanthe changed the title Use the orka CLI name for Orka 4.0, keep 3.x builds working HOLD: Use the orka CLI name for Orka 4.0, keep 3.x builds working Oct 9, 2026
@celanthe

celanthe commented Oct 9, 2026 •

Copy link
Copy Markdown
Collaborator Author

HOLD, pending the OK-6390 decision (targeted Wednesday Oct 14). Resolved 19 October: the rename landed. See the update below.

The orka3 to orka rename is proposed, not decided. As of Oct 9 the CLI still builds as orka3 on releases/cluster/4.0 and master, and no OK-6390 commit exists. Please don't review or merge until the rename is confirmed and lands in code. The release-notes side is held separately in macstadium/macstadium-docs#406.

@celanthe celanthe changed the title HOLD: Use the orka CLI name for Orka 4.0, keep 3.x builds working HOLD until 4.0: Use the orka CLI name for Orka 4.0, keep 3.x builds working Oct 19, 2026
@celanthe

celanthe commented Oct 19, 2026 •

Copy link
Copy Markdown
Collaborator Author

Hold lifted. OK-6390 landed (monorepo-dev#25278), so this is ready for review and merges with Orka 4.0 on 28 October. The 4.0.0 linux/amd64 and linux/arm64 tarballs the Dockerfile downloads are published. PR CI skips the deploy job, so that path first runs after merge.

@celanthe
celanthe marked this pull request as ready for review October 19, 2026 14:10
@celanthe
celanthe requested a review from a team as a code owner October 19, 2026 14:10
@celanthe celanthe changed the title HOLD until 4.0: Use the orka CLI name for Orka 4.0, keep 3.x builds working Use the orka CLI name for Orka 4.0, keep 3.x builds working Oct 27, 2026

@spikeburton spikeburton left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The description's arm64 bullet is stale, since #79 already merged that fix. When this is released, I'd note which image tag goes with which Orka version.

@celanthe
celanthe merged commit 566652a into main Oct 27, 2026
2 checks passed
@celanthe
celanthe deleted the update/orka-cli-rename branch October 27, 2026 19:25
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.

2 participants