Skip to content

ci: pilot Peak x64 runners for same-repository PR checks - #1752

Open
peak-runners[bot] wants to merge 3 commits into
mainfrom
peak/onboarding
Open

peak-runners[bot] wants to merge 3 commits into
mainfrom
peak/onboarding

Conversation

@peak-runners

@peak-runners peak-runners Bot commented Oct 2, 2026 •

Copy link
Copy Markdown

Narrow the Peak onboarding pilot to build/test CI on peak-ubuntu-24.04-4 (Ubuntu 24.04, x64 only). No ARM migration.

  • Use Peak only for same-repository pull_request jobs: quality-checks in ci.yml, and the five SDK jobs in ci-python.yml (agent-framework-python, openai-sdk-python, cartesia-sdk-python, pipecat-sdk-python, livekit-sdk-python).
  • Route fork pull requests to GitHub-hosted ubuntu-latest instead of skipping them. Both workflows currently trigger only on pull requests; the expression also defaults non-PR events to GitHub-hosted runners.
  • Leave all eight publishing workflows and both Claude workflows on GitHub-hosted ubuntu-latest; retain npm OIDC/trusted publishing without adding tokens.
  • Preserve timeouts, matrices, path filters, concurrency, steps, permissions and environment, including main’s contents: read and FORCE_COLOR additions from fix(CI): add missing read permission and force color #1750.

Validation: actionlint v1.7.12 passes for all 12 onboarding workflows (external shellcheck/pyflakes disabled). Parsed YAML comparison confirms only six runs-on values differ from current main; all other workflows match main byte-for-byte. Static routing checks cover same-repository PRs, forks and non-PR fallback. Live CI results are separate from these checks.

Before adoption: confirm an enforced runner-group/provider admission boundary that prevents fork-controlled workflows from selecting Peak. The PR-controlled expression is routing, not an admission security boundary. Runner/group and fork-approval settings were inaccessible (403), so this PR does not claim a secure or merge-ready pilot. Provider isolation/cleanup and App installation grants remain owner followups.

Live CI at 4a7d1a9ad4e4ab24835b405639b6b12123e034ad: Quality Checks and Python SDK CI passed. All eleven jobs ran on Peak in runner group 6. Quality CI exercised frozen install, Memory Graph types/tests and Biome; Tools/AI SDK/playground conditional steps were skipped because this PR only changes workflows. The ten Python matrix jobs exercised builds, dependency/import checks and tests. No fork test PR, release/Claude validation or ARM run was performed.

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Oct 2, 2026 •

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Preview URL Updated (UTC)
✅ Deployment successful!
View logs
supermemory-app 4a7d1a9 Commit Preview URL

Branch Preview URL
Oct 02 2026, 07:35 PM

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Oct 2, 2026 •

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Updated (UTC)
✅ Deployment successful!
View logs
supermemory-mcp 4a7d1a9 Oct 02 2026, 07:35 PM

@MaheshtheDev
MaheshtheDev self-requested a review October 2, 2026 19:09
@capy-ai capy-ai Bot changed the title Run CI on Peak ci: pilot Peak x64 runners for same-repository PR checks Oct 2, 2026

This branch has not been deployed

No deployments
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