Distribution And Release
Orca ships @twelvehart/orcats on npm for normal project use and GitHub Release binaries for no-node_modules execution.
NPM package
Section titled “NPM package”npm i @twelvehart/orcatsnpm i -D typescriptbunx -p @twelvehart/orcats orcats --versionThe package provides the public TypeScript API and a Bun-backed orcats CLI shim.
Release assets
Section titled “Release assets”| Asset | Platform |
|---|---|
orcats-darwin-arm64.tar.gz | macOS Apple Silicon |
orcats-darwin-x64.tar.gz | macOS Intel |
orcats-linux-arm64.tar.gz | Linux arm64 glibc |
orcats-linux-x64.tar.gz | Linux x64 glibc |
Each tarball contains a single executable named orcats. SHA256SUMS.txt contains one checksum line per tarball.
Installer
Section titled “Installer”curl -fsSL https://github.com/ASRagab/orca-ts/releases/latest/download/install.sh | bashEnvironment variables:
| Variable | Meaning |
|---|---|
ORCA_VERSION | Install a specific GitHub Release version without the v prefix. |
ORCA_INSTALL_DIR | Destination directory for the executable. |
Release process
Section titled “Release process”Releases are tag-driven. A vX.Y.Z tag runs the release workflow, verifies the repo, publishes GitHub Release binaries plus install.sh, and publishes @twelvehart/orcats@X.Y.Z to npm through Trusted Publishing.
The npm package is published from GitHub Actions with OIDC. The workflow does not use NPM_TOKEN; maintainers configure npm trust for ASRagab/orca-ts and .github/workflows/release.yml before tagging.