Skip to content

CI: GitHub-hosted CI, releases on our hardware ([simien] leaves CI) - #18

Merged
samifouad merged 2 commits into
mainfrom
claude/ci-off-simien-34
Nov 10, 2026
Merged

samifouad merged 2 commits into
mainfrom
claude/ci-off-simien-34

Conversation

@samifouad

@samifouad samifouad commented Nov 10, 2026 •

Copy link
Copy Markdown
Member

CI on GitHub-hosted, releases on our hardware (ci-release group)

Sami, 10 Nov: public-ci runs on GitHub, releases on our hardware. This repo is public, and self-hosted runners refuse public repos (a fork PR must never run on our machines), except the ci-release runner group, which admits only release jobs in addiscorp/mirab and zegadb/zega, pg_zega and earth. Fork-PR runs need approval org-wide. [simien] stops hosting CI VMs (its RAM runs a local AI model), which ends mirab-linux-arm64.

Part of addiscorp/infra#34.

What

  • ci.yml test → ubuntu-24.04 (GitHub-hosted); the job sets up Node 24 itself.
  • publish.yml is unchanged: npm trusted publishing (OIDC) on ubuntu-24.04, which only works on GitHub-hosted runners (APS 11).

Evidence

Workflow-only change; this PR's own run is the test for its CI jobs. The release jobs run on the next canary or release. actionlint: no errors in lines this PR touches.

-claude

@samifouad samifouad changed the title CI: move off [simien]'s mirab-linux-arm64 to host-linux-x64 CI: GitHub-hosted runners (public repo; [simien] leaves CI) Nov 10, 2026
@samifouad samifouad changed the title CI: GitHub-hosted runners (public repo; [simien] leaves CI) CI: GitHub-hosted CI, releases on our hardware ([simien] leaves CI) Nov 10, 2026
@samifouad
samifouad merged commit dcc117e into main Nov 10, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant