Skip to content

.github/workflows: Migrate workflows to Blacksmith runners - #159

Merged
paperbenni merged 1 commit into
mainfrom
blacksmith-migration-6a5b6d6
Aug 8, 2026
Merged

.github/workflows: Migrate workflows to Blacksmith runners#159
paperbenni merged 1 commit into
mainfrom
blacksmith-migration-6a5b6d6

Conversation

@blacksmith-sh

@blacksmith-sh blacksmith-sh Bot commented Aug 8, 2026

Copy link
Copy Markdown
Contributor

This PR has been automatically generated by a team member in your GitHub organization using Blacksmith's Migration Wizard. This PR changes the following:

  1. Your selected workflows will now run on Blacksmith's 2x faster hardware (e.g., runs-on: blacksmith-4vcpu-ubuntu-2204). Learn more about the different instances available to choose from.
  2. Your jobs running on Blacksmith will now have all official GitHub and popular third-party cache actions automatically interact with our 4x faster, colocated cache. Learn more about Blacksmith's actions cache.
  3. Your GitHub Actions will now actually be observable. Learn more about Blacksmith's logging and other observability features.
  4. Your Docker builds will now automatically share their Docker layer cache, resulting in up to 40x faster builds. Learn more about Blacksmith's Docker layer caching.

Summary by Sourcery

CI:

  • Update all release, CI, and sync workflows to run on blacksmith-4vcpu-ubuntu-2404 runners instead of self-hosted infrastructure.

@sourcery-ai

sourcery-ai Bot commented Aug 8, 2026

Copy link
Copy Markdown
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

.github workflows are migrated from self-hosted runners to Blacksmith-managed runners by updating the runs-on configuration across several release and CI workflows.

File-Level Changes

Change Details Files
Migrate release workflow jobs from self-hosted runners to Blacksmith runners.
  • Update runs-on value for the build job to use blacksmith-4vcpu-ubuntu-2404.
  • Update runs-on value for the cross-compile job to use blacksmith-4vcpu-ubuntu-2404.
  • Update runs-on value for the pkgbuild job to use blacksmith-4vcpu-ubuntu-2404.
  • Update runs-on value for the deb packaging job to use blacksmith-4vcpu-ubuntu-2404.
  • Update runs-on value for the release publishing job to use blacksmith-4vcpu-ubuntu-2404.
.github/workflows/release.yml
Migrate release-plz workflow jobs from self-hosted runners to Blacksmith runners.
  • Update runs-on value for the release-plz-release job to use blacksmith-4vcpu-ubuntu-2404.
  • Update runs-on value for the release-plz-pr job to use blacksmith-4vcpu-ubuntu-2404.
.github/workflows/release-plz.yml
Migrate CI workflow test job from self-hosted runners to Blacksmith runners.
  • Update runs-on value for the Arch Linux test job to use blacksmith-4vcpu-ubuntu-2404.
.github/workflows/ci.yml
Migrate sync-pkgbuild workflow job from self-hosted runners to Blacksmith runners.
  • Update runs-on value for the sync job to use blacksmith-4vcpu-ubuntu-2404.
.github/workflows/sync-pkgbuild.yml

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@paperbenni
paperbenni merged commit f0eeabb into main Aug 8, 2026
4 checks passed

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've left some high level feedback:

  • Since these jobs previously ran on self-hosted runners, double-check whether any implicit host-level dependencies (custom tools, mounted volumes, preinstalled SDKs, or environment variables) were provided by your self-hosted machines; if so, they should either be moved into the container images or explicitly recreated on the Blacksmith runner.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- Since these jobs previously ran on self-hosted runners, double-check whether any implicit host-level dependencies (custom tools, mounted volumes, preinstalled SDKs, or environment variables) were provided by your self-hosted machines; if so, they should either be moved into the container images or explicitly recreated on the Blacksmith runner.

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

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