Arcadible GitHub Release Tools
Helper commands for the Arcadible Release workflow on GitHub Actions.
Docs · Arcadible CLI · Arcadible · Studio
When arc deploy git pushes a release tag, the Arcadible Release workflow builds the game on GitHub Actions. It installs this package alongside the Arcadible CLI, on Node.js 24, and runs its arctool-* commands between the CLI's. You don't need to install it yourself.
| Command | What it does |
|---|---|
arctool-assert-tag <manifest> <tag> | Checks that the tag is arcadible/release/v<version>, with the manifest's |
arctool-assert-dir <dir> | Checks that the build wrote the deploy directory, a folder |
arctool-put-version <manifest> | Outputs version, the manifest's |
arctool-put-prerelease <manifest> | Outputs prerelease, whether the version is a prerelease |
arctool-put-build <manifest> | Outputs build, the build command on one line, or nothing without one |
arctool-put-deploy-dir <manifest> | Outputs deploy_dir |
arctool-put-cache <manifest> | Outputs cache, the package manager whose lockfile is beside the manifest |
arctool-install-deps <dir> | Installs the project's dependencies exactly as its lockfile pins them |
arctool-put-artifact <file> | Checks that arc pack wrote the package, and outputs artifact, its path |
<manifest> is the file arc inspect --json writes. <file> is the package arc pack wrote. Each put command writes its value to the step's GITHUB_OUTPUT. arctool-install-deps runs npm ci, or pnpm or Yarn through corepack, and does nothing without a lockfile. A command that fails says why on stderr, and exits 1.
License
Apache-2.0