Repository navigation
Use the orka CLI name for Orka 4.0, keep 3.x builds working - #78
Conversation
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>
|
|
|
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 |
# Conflicts: # Dockerfile
spikeburton
left a comment
There was a problem hiding this comment.
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.
Orka 4.0 renames the CLI from
orka3toorkaand moves its artifacts to theorka/S3 path (OK-6390). Tracked in DI-753.Changes
pkg/orka/client.gocallsorkathrough onecliBinaryconstant.orka/for 4.x andorka3/for 3.x, based onORKA_VERSION, and installs asorkawith anorka3symlink. Default is now4.0.0(was3.1.0).linux/arm64image shipping an x86 CLI. The download now usesTARGETARCH.examples/.envuseorkaand4.0.0.Testing
go vet,go build, andgo testpass. Ran the download step against the 3.6.3amd64andarm64artifacts. 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