release-beta.md wrongly claims the linux dist cannot be cross-built on macOS

Open Beginner friendly
#1,231 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
1-3 hours
Newbie friendliness
92/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
bun
Domain
documentation

Research direction

Edit .claude/commands/release-beta.md, starting with the note about macOS cross-building and the local Verdaccio sanity suite. Use the demonstrated Bun install/build flow as the reference, then document --target-index, Linux artifact validation in Debian, and how LLM-dependent phases behave without an API key.

Written by the indexing model from the issue text.

Description

Deferred from the v0.10.0 release review. Documentation fix, no code change.

.claude/commands/release-beta.md states that on a Mac you cannot cross-build the linux dist, and therefore that the local Verdaccio sanity suite "validates the current platform only". That note is why this gate has routinely been skipped locally and left to CI.

It is wrong. Demonstrated during the v0.10.0 release:

bun install --os='*' --cpu='*'     # pulls @altimateai/altimate-core-linux-arm64-gnu@0.7.0
cd packages/opencode
bun run script/build.ts --target-index=0 --skip-install   # linux-arm64

That produces a genuine ELF 64-bit LSB executable, ARM aarch64, which then published to Verdaccio and passed every phase inside the Debian container (install 13/0, extended resilience 14/0/1, security 16/0).

Two things worth folding into the doc along with the correction:

  • --targets takes OS names (linux, darwin, win32); use --target-index=N to build a single target and avoid building three linux binaries.
  • Without ANTHROPIC_API_KEY the LLM-dependent phases skip_test rather than fail, so the install/packaging/security coverage still runs.

This converts "CI will catch it" into a gate anyone can run before tagging — which matters, since it is the only gate that exercises the published artifact shape rather than the source tree.

Dominant language
TypeScript
Stars
813
Forks
134
Avg merge
2d 5h
Merged PRs (30d)
62

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AltimateAI/altimate-code

All issues in AltimateAI/altimate-code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.