Skip to content

Open-source Grok Bot alternative for named AI teammates. Local-first desktop, web, and mobile clients with per-bot tools, instructions, and memory. Independent fork of T3 Code.

5.4 KB
Raw Blame

CI quality gates

For Akeru Bot maintainers.

.github/workflows/ci.yml runs on each ready pull request revision. Draft pull requests do not use a runner. A new revision cancels the older run for that pull request. Maintainers can also dispatch the workflow manually for diagnostics. Every job uses a 4-vCPU tenki-standard-medium-4c-8g Linux runner, billed per second, and the jobs run in parallel. Issue-label, PR-vouch, and PR-size jobs also use Tenki Linux runners through GitHub Actions.

  • Static checks and builds. The job rejects external local dependencies, installs the committed lockfile, checks lint and formatting, runs workspace type checks, validates the plugin directory and contribution policy, builds the desktop pipeline, checks the preload output, builds the marketing site, tests the resource monitor, and checks release-only configuration. On a dispatched run it also authorizes the version-branch revision.
  • Package tests. Tests the shipped desktop and shared packages. Relay and mobile-production packages are excluded.
  • Server tests (1/4 to 4/4). Four Vitest shards split the complete server suite by file. Each shard still runs its files one at a time (fileParallelism: false), because running server files in parallel on one machine causes load-sensitive flakes. The suite excludes orchestrationEngine.integration.test.ts until the executor stack restores its test adapter and stops the fixture from calling OpenAI with a test credential.
  • Repository checks. Waits for the jobs above and passes only when all of them passed.

The repository ruleset requires the Repository checks result before a pull request can merge. Direct pushes to main cannot bypass this gate. Release workflows start after the validated revision lands on main; version packaging is separate from pull-request CI. The version workflow runs pnpm release:version and maintains one rolling Version Packages pull request with Git and gh, finding it by its changeset-release/main head branch. CI also requires every ordinary pull request to contain a real or empty changeset, so release intent cannot be lost after merge. Changesets consumes those files in the version pull request and keeps the four product package versions synchronized. Only the repository-owned Changesets branch and bot-authored pull request can bypass the marker check or change those stable versions. Updates to that branch dispatch CI against the exact pull request head SHA; empty-only changesets do not dispatch a version branch.

.github/workflows/installer-tests.yml runs focused Windows PowerShell 5.1 tests when the Windows installer changes. It checks checksum rejection, per-invocation temporary files, failure cleanup, and the bootstrap under Restricted execution policy. Downloads and installer launches use fixtures; this job does not install Akeru Bot.

.github/workflows/release-smoke.yml is a manual, non-publishing artifact smoke workflow. It uses a 4-vCPU Tenki runner for Linux and GitHub-hosted Apple Silicon macOS and Windows runners. It builds a Developer ID signed macOS arm64 app. Electron-builder notarizes and staples the app before it packages the DMG. The workflow then submits and staples the DMG as a separate object. It checks both objects with Apple's verification tools. Windows and Linux artifacts stay unsigned. The workflow also builds and dry-runs the CLI package and checks the marketing site. It uploads desktop artifacts for seven days. It does not create a GitHub release, publish a package, or deploy a site.

Merging a stable version change to main starts the stable release workflow. A push that changes a watched manifest without changing the stable version exits successfully before any release build starts. A manual dispatch for an existing stable tag still fails. A Tenki Linux runner plus GitHub-hosted Apple Silicon macOS and Windows runners build the advertised desktop targets before the workflow creates the vX.Y.Z tag and GitHub Release. The final job verifies the exact asset names and SHA256SUMS, then starts the next Version Packages update. Version automation waits for the current stable tag before it prepares another version. A stable release fails before building when the macOS signing credentials are absent, so an unsigned DMG can never publish as the latest stable release. Scheduled nightlies and Windows builds without credentials still produce unsigned artifacts. Unsigned macOS builds still replace Electron's linker-signed stub with a sealed ad-hoc signature and fail the release if codesign --verify fails or the identifier is not dev.leodoes.akeru. Complete credentials use the existing Developer ID, notarization, and Azure Trusted Signing paths.

The same workflow runs at minute 17 every three hours for nightly releases. It skips the build when main still points at the commit from the latest successful nightly. Otherwise it builds the same three desktop targets under a semver prerelease version and creates a GitHub prerelease that cannot replace the latest stable release. Linux preflight, build, and publication jobs use Tenki; native macOS and Windows builds remain on the required GitHub-hosted runners.

See the release smoke runbook for the exact validation path.