Skip to content
GrammaTonic edited this page Mar 1, 2026 · 8 revisions

Base Image: Ubuntu Resolute (25.10 Pre-release)

This project uses ubuntu:resolute for the Chrome runner to ensure compatibility with the latest browser dependencies. CVE mitigation is performed via npm overrides, local installs, and automated Trivy scans. See README and DEPLOYMENT for details.

GitHub Actions Self-Hosted Runner Wiki

Welcome to the comprehensive documentation for the GitHub Actions Self-Hosted Runner project!

🎯 Latest Updates

πŸš€ Release v2.4.0 Available (March 1, 2026)

  • Image Versions: Standard Runner v2.4.0, Chrome Runner v2.4.0, Chrome-Go Runner v2.4.0
  • Base Image: Switched to ubuntu:resolute (25.10) across all Dockerfiles for latest browser dependencies
  • Browser Stack: Chrome for Testing 146.0.7680.31, Playwright 1.58.2, Cypress 15.11.0, Node.js 24.14.0 (LTS Krypton), npm 11.11.0
  • Go Toolchain: Go 1.26.0 in Chrome-Go runner
  • GitHub Actions Runner: Bumped to v2.331.0
  • Security Overrides: tar@7.5.9, brace-expansion@5.0.4, @isaacs/brace-expansion@5.0.1, glob@13.0.6, minimatch@10.2.4, diff@8.0.3
  • CI/CD Fix: Trivy scanner now installs via apt repository (fixes broken wget download); trivy-action pinned to 0.34.1
  • Playwright: Configured to use system Chrome binary via PLAYWRIGHT_CHROMIUM_EXECUTABLE_PATH
  • Quality Gates: Docker validation, security scans, and runner self-tests passing βœ…

πŸ”’ Critical Security Improvements (January 15, 2025)

  • Security Patches: βœ… VDB-216777/CVE-2020-36632, CVE-2025-9288, CVE-2024-37890 resolved
  • Performance: Optimized Docker images with comprehensive cache cleaning
  • CI/CD: Enhanced pipeline reliability with standardized Docker build contexts
  • Monitoring: Weekly Trivy security scans with automated SARIF reporting

βœ… Chrome Runner Production Ready (September 2024)

  • Status: βœ… Production Ready - All 10/10 CI/CD checks passing
  • Performance: 60% faster web UI tests with resource isolation
  • Latest Versions: Playwright 1.58.2, Cypress 15.11.0 with security patches
  • Documentation: Chrome Runner Guide

πŸ“Š Current Versions

Component Standard Runner Chrome Runner Chrome-Go Runner Security Status
Image Version v2.4.0 v2.4.0 v2.4.0 βœ… Latest
Base Image ubuntu:resolute ubuntu:resolute ubuntu:resolute βœ… Latest
GitHub Actions Runner v2.331.0 v2.331.0 v2.331.0 βœ… Latest
Node.js - 24.14.0 (Krypton) 24.14.0 (Krypton) βœ… Chrome Runner Only
npm - 11.11.0 11.11.0 βœ… Latest
Chrome for Testing - 146.0.7680.31 146.0.7680.31 βœ… Latest
Playwright - 1.58.2 1.58.2 βœ… Latest
Cypress - 15.11.0 15.11.0 βœ… Latest
Go - - 1.26.0 βœ… Chrome-Go Only

πŸ“‹ Full Version Details: Version Overview

πŸ“– Table of Contents

Getting Started

Specialized Runners

Configuration

πŸš€ Quick Start Options

🌐 For Web UI Testing

# Chrome Runner (Recommended for browser tests)
./scripts/build-chrome.sh --push
docker-compose -f docker/docker-compose.chrome.yml up -d

🐳 For General Workloads

# Standard Runner
docker build -t github-runner:latest ./docker
docker-compose up -d

πŸ”— Quick Links

Component Status Documentation
Chrome Runner βœ… Production Ready Chrome Runner Guide
Standard Runner βœ… Stable Installation Guide
CI/CD Pipeline βœ… Passing Production Deployment
Security Scanning βœ… Clean Common Issues

πŸš€ Quick Links

πŸ”— External Resources

πŸ“ Documentation Parity & Recent Improvements (2025-11-14)

  • Release v2.2.0 documentation refreshed across README, changelog, wiki, and release notes
  • npm tar@7.5.2 override documented for reproducible package installs and security posture
  • Chrome runner guidance updated for Playwright 1.58.2, Cypress 15.11.0, and Chrome 142.0.7444.162
  • Validation scripts and runner self-tests rerun to confirm Docker image health for release
  • Troubleshooting, quick start, and version tables synced with latest component inventory

See Chrome Runner Guide and Version Overview for full details.

πŸ“ Contributing to Documentation

Found something missing or incorrect? We welcome contributions to improve this documentation:

  1. Visit the main repository
  2. Open an issue or submit a pull request
  3. Help us keep the documentation accurate and up-to-date

Last updated: November 14, 2025