Skip to content

release: migrate fork CI to GitHub-hosted runners #8

Closed

Description

@ag-jin

Problem

PR #7 cannot run CI: the current CI workflow has remained queued for more than two hours and no job step has started. The fork has no configured runner capacity for the custom blacksmith-* labels used by .github/workflows/ci.yml.

Scope

  • Change only .github/workflows/ci.yml.
  • Replace the three Linux CI job labels with ubuntu-24.04.
  • Replace the mobile static-analysis label with macos-15, matching the fork desktop release workflow's supported macOS baseline.
  • Add a focused workflow contract test for the runner mapping.

Acceptance Criteria

  • Check, Test, and Release Smoke use ubuntu-24.04.
  • Mobile Native Static Analysis uses macos-15.
  • The focused test fails if ci.yml refers to blacksmith and asserts all four job runner labels.
  • The migration PR's CI jobs acquire a runner and emit job logs.
  • No release, deployment, signing, package identity, or repository runner settings are changed.

Dependency

This ticket blocks #2 because its draft PR cannot complete CI until the fork uses runners it can acquire.

Test Seam

The public seam is the .github/workflows/ci.yml workflow contract. Verify it with a focused test that reads the workflow as a release-operated artifact, not by testing a YAML parser implementation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions