Skip to content

ci: move lanes to self-hosted runners — never use GitHub-hosted - #141

Merged
Dvorinka merged 6 commits into
mainfrom
ci/self-hosted-runners
Nov 7, 2026
Merged

Dvorinka merged 6 commits into
mainfrom
ci/self-hosted-runners

Conversation

@Dvorinka

@Dvorinka Dvorinka commented Nov 7, 2026

Copy link
Copy Markdown
Owner

All lanes moved off GitHub-hosted runners to self-hosted. Linux → [self-hosted, linux, x64], Windows → [self-hosted, windows, x64] (hp-win11), macOS → [self-hosted, macos, x64] (osx-nab9). arm64 image lanes stay on ubuntu-24.04-arm — no ARM hardware in fleet and QEMU SIGILLs on node:20-alpine (documented in-file).

@vercel

vercel Bot commented Nov 7, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
relay-landing Ready Ready Preview Nov 7, 2026 3:40pm UTC

@mira-tdvorak

mira-tdvorak Bot commented Nov 7, 2026 •

Copy link
Copy Markdown

Mira PR Walkthrough

This PR migrates all CI build lanes from GitHub-hosted runners to self-hosted runners for Linux, Windows, and macOS (x64). ARM64 image lanes remain on ubuntu-24.04-arm due to lack of ARM hardware in the fleet and QEMU SIGILL issues with node:20-alpine. The only file change shown in metadata is a minor go.mod adjustment, likely a Go toolchain or dependency version bump related to the runner migration. However, the PR description implies broader GitHub Actions workflow changes that aren't reflected in the provided file list.

⚠️ Potential overlap with other open PRs — these may be stepping on this one:

  • #140 (merge-conflict risk) — Both PRs modify apps/web/package.json, so merging will cause a conflict in that file. Shared: apps/web/package.json
  • #139 (merge-conflict risk) — Both PRs modify go.mod, so merging will cause a conflict in that file. Shared: go.mod
  • #138 (merge-conflict risk) — Both PRs modify apps/desktop/go.mod and apps/web/package.json, so merging will cause conflicts in those files. Shared: apps/desktop/go.mod, apps/web/package.json

1 file reviewed · 1 comment (⚠️ 1 warning)


Comment @mira-tdvorak help to get the list of available commands and usage tips.

@mira-tdvorak mira-tdvorak 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.

Mira Review Summary

The workflow ployz-build.yml declares a 'runner' workflow_dispatch input at line 7 but the job at line 13 hardcodes runs-on, rendering the input unused. This makes the runner input ineffective for selecting runners. The issue is a configuration warning that should be addressed.

Key Issues

Issue Location
🔴 ployz-build.yml declares a 'runner' input but hardcodes runs-on, making the input useless .github/workflows/ployz-build.yml:13

Comment thread .github/workflows/ployz-build.yml Resolved
Comment thread .github/workflows/ployz-build.yml Resolved

@mira-tdvorak mira-tdvorak 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.

Mira Review Summary

No issues found in the provided diffs. The changes are routine dependency updates (golang.org/x/net v0.61.0 → v0.62.0 in both go.mod files, echo/v4 v4.15.3 → v4.16.1 and go-colorable v0.1.14 → v0.1.15 in apps/desktop/go.mod) and security hardening via npm overrides for decode-uri-component and node-forge in apps/mobile/package.json. All version bumps appear consistent and non-breaking. The PR title mentions CI runner changes but those workflow modifications were presumably addressed in the previous review round (referenced .github/workflows/ployz-build.yml lines already resolved).

Comment thread apps/desktop/go.mod Resolved

@mira-tdvorak mira-tdvorak 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.

Mira Review Summary

A security warning was flagged in apps/desktop/go.mod:21 for known vulnerabilities in github.com/labstack/echo/v4@v4

Comment thread apps/desktop/go.mod
github.com/gorilla/websocket v1.5.3 // indirect
github.com/jchv/go-winloader v0.0.0-20210711035445-715c2860da7e // indirect
github.com/labstack/echo/v4 v4.15.3 // indirect
github.com/labstack/echo/v4 v4.16.3 // indirect

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Security issue
⚠️ Warning

Known vulnerabilities in github.com/labstack/echo/v4@v4.16.3

OSV.dev reports 2 known vulnerabilities affecting github.com/labstack/echo/v4@v4.16.3, introduced by this PR:

  • GO-2026-6872 unknown: Rate Limiter Bypass via Spoofed X-Forwarded-For Header in Default Configuration in github.com/labstack/echo — fixed in 5.1.0
  • GO-2026-6875 unknown: Reverse Proxy Forwards Attacker-Supplied X-Real-IP to Upstream by Default in github.com/labstack/echo — fixed in 5.4.0

Upgrade to 5.1.0 or later.


Prompt for AI Agents
In apps/desktop/go.mod, upgrade the dependency github.com/labstack/echo/v4 from v4.16.3 to a non-vulnerable version (5.1.0, 5.4.0). Update any associated lockfile entries.

Not useful? Reply @mira-tdvorak reject to dismiss this suggestion.

@Dvorinka
Dvorinka merged commit ef4f533 into main Nov 7, 2026
8 checks passed
@Dvorinka
Dvorinka deleted the ci/self-hosted-runners branch November 7, 2026 16:45

This branch was successfully deployed

1 active deployment
Preview — 4fbfd275 Deployed Nov 7, 2026 by vercel[bot]
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.

2 participants