Skip to content

Move CI onto Trunk Runners - #1237

Closed
trunk-runners-staging[bot] wants to merge 1 commit into
mainfrom
trunk-runners/migrate-01a16558-3101-7501-80f7-9b52cbe630bf
Closed

trunk-runners-staging[bot] wants to merge 1 commit into
mainfrom
trunk-runners/migrate-01a16558-3101-7501-80f7-9b52cbe630bf

Conversation

@trunk-runners-staging

Copy link
Copy Markdown

This pull request moves CI onto Trunk Runners.

What changed

  • .github/workflows/mirror_release_to_s3.yml
    • mirror: ubuntu-latest → Trunk Runners medium (high memory)
  • .github/workflows/promote_release.yml
    • promote: ubuntu-latest → Trunk Runners medium (high memory)
  • .github/workflows/pull_request.yml
    • dynamic-ci-filter: ubuntu-latest → Trunk Runners medium (high memory)
    • trunk_check_runner: ubuntu-latest → Trunk Runners medium (high memory)
    • build_pyo3: ubuntu-latest → Trunk Runners medium (high memory)
    • build_wasm: ubuntu-latest → Trunk Runners medium (high memory)
    • gate: ubuntu-latest → Trunk Runners medium (high memory)
  • .github/workflows/pyo3.yml
    • dynamic-ci-filter: ubuntu-latest → Trunk Runners medium (high memory)
    • get-date-sha: ubuntu-latest → Trunk Runners medium (high memory)
    • sdist: ubuntu-latest → Trunk Runners medium (high memory)
    • publish-annotation: ubuntu-latest → Trunk Runners medium (high memory)
    • gate: ubuntu-latest → Trunk Runners medium (high memory)
  • .github/workflows/release_cli.yml
    • tag_and_release: ubuntu-latest → Trunk Runners medium (high memory)
  • .github/workflows/release_ruby_gem.yml
    • ci-data: ubuntu-latest → Trunk Runners medium (high memory)
    • cross-gem: ubuntu-latest → Trunk Runners medium (high memory)
    • publish_ruby_gem: ubuntu-latest → Trunk Runners medium (high memory)
  • .github/workflows/ruby.yml
    • dynamic-ci-filter: ubuntu-latest → Trunk Runners medium (high memory)
    • build: ubuntu-latest → Trunk Runners medium (high memory)
    • build-ruby-gem: ubuntu-latest → Trunk Runners medium (high memory)
    • test-ruby-gem-uploads: ubuntu-latest → Trunk Runners medium (high memory)
    • gate: ubuntu-latest → Trunk Runners medium (high memory)
  • .github/workflows/smoke_test.yml
    • determine_releases: ubuntu-latest → Trunk Runners medium (high memory)
    • download_ruby_gem: ubuntu-latest → Trunk Runners medium (high memory)
    • test_ruby_gem_staging: ubuntu-latest → Trunk Runners medium (high memory)
    • test_ruby_gem_production: ubuntu-latest → Trunk Runners medium (high memory)
    • production-slack-workflow-status: ubuntu-latest → Trunk Runners medium (high memory)
    • staging-slack-workflow-status: ubuntu-latest → Trunk Runners medium (high memory)
  • .github/workflows/smoke_test_main.yml
    • build_ruby_gem: ubuntu-latest → Trunk Runners medium (high memory)
    • test_ruby_gem_staging: ubuntu-latest → Trunk Runners medium (high memory)
    • test_ruby_gem_production: ubuntu-latest → Trunk Runners medium (high memory)
    • production-slack-workflow-status: ubuntu-latest → Trunk Runners medium (high memory)
    • staging-slack-workflow-status: ubuntu-latest → Trunk Runners medium (high memory)
  • .github/workflows/wasm.yml
    • dynamic-ci-filter: ubuntu-latest → Trunk Runners medium (high memory)
    • build: ubuntu-latest → Trunk Runners medium (high memory)
    • gate: ubuntu-latest → Trunk Runners medium (high memory)

What we did not change, and why

Needs a size: runs-on is an expression (12 jobs)

build_release, test in .github/workflows/pull_request.yml; linux, linux-pytest, macos in .github/workflows/pyo3.yml; build_release, perform_smoke_test in .github/workflows/release_cli.yml; test-ruby-gem, test-musl-gem in .github/workflows/release_ruby_gem.yml; build_cli in .github/workflows/smoke_test.yml; build_cli, test_cli in .github/workflows/smoke_test_main.yml

How to roll back

Set the repository variable CI_RUNNER_OVERRIDE to hosted. Every job here falls straight back to the runner it used before — no second pull request, no revert. Each rewritten runs-on: carries that toggle inline, which is why the value looks the way it does.

What to watch

This pull request does not exercise every workflow it rewrote. These will not run on it — either they have no pull_request trigger, or its filters exclude a change to workflow files alone — so they get no signal until after merge:

  • .github/workflows/mirror_release_to_s3.yml
  • .github/workflows/promote_release.yml
  • .github/workflows/release_ruby_gem.yml
  • .github/workflows/smoke_test.yml
  • .github/workflows/smoke_test_main.yml

Watch their first post-merge run.

@trunk-io

trunk-io Bot commented Oct 22, 2026

Copy link
Copy Markdown

Merging to main in this repository is managed by Trunk.

  • To merge this pull request, check the box to the left or comment /trunk merge below.

After your PR is submitted to the merge queue, this comment will be automatically updated with its status. If the PR fails, failure details will also be posted here

@eltonkl
eltonkl deleted the trunk-runners/migrate-01a16558-3101-7501-80f7-9b52cbe630bf branch October 23, 2026 14:33
@codecov-commenter

codecov-commenter commented Oct 23, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 84.03%. Comparing base (83ef4c0) to head (e7d5216).

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1237      +/-   ##
==========================================
+ Coverage   83.86%   84.03%   +0.16%     
==========================================
  Files          74       74              
  Lines       17898    17898              
==========================================
+ Hits        15011    15040      +29     
+ Misses       2887     2858      -29     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@trunk-io

trunk-io Bot commented Oct 23, 2026 •

Copy link
Copy Markdown

Static Badge   Static Badge   Static Badge

View Full Report ↗︎ ⋅ Docs

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

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants