react@next integration workflow (necolas/react-native-web)

The react@next integration workflow from necolas/react-native-web, explained and optimized by Latchkey.

What it does

This is the react@next integration workflow from the necolas/react-native-web repository, a real project running GitHub Actions. It is shown here with attribution under its MIT license.

Below, Latchkey shows a faster, safer version produced by its optimization engine.

The workflow

name: react@next integration

on:
  schedule:
    # Run every Monday at 12:00 (see https://crontab.guru)
    - cron: '0 12 * * 1'

jobs:
  react-next:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v3
    - uses: actions/setup-node@v3
      with:
        node-version: 16
    - run: npm install
    # Update react-native-web to use react@next
    - run: npm install --force react@next react-dom@next -w react-native-web
    # Run the unit tests
    - run: npm run unit

The same workflow, on Latchkey

Estimated ~20% faster on cache hits, plus fewer wasted runs and a safer supply chain. Added and changed lines are highlighted.

name: react@next integration
 
on:
  schedule:
    # Run every Monday at 12:00 (see https://crontab.guru)
    - cron: '0 12 * * 1'
 
jobs:
  react-next:
    timeout-minutes: 30
    runs-on: latchkey-small
    steps:
    - uses: actions/checkout@v3
    - uses: actions/setup-node@v3
      with:
        cache: 'npm'
        node-version: 16
    - run: npm install
    # Update react-native-web to use react@next
    - run: npm install --force react@next react-dom@next -w react-native-web
    # Run the unit tests
    - run: npm run unit
 

What changed

• Run on Latchkey managed runners with one line (runs-on), which apply the fixes below automatically and self-heal transient failures. This example uses latchkey-small; pick the runner size that fits the job.
• Cache dependency installs on the setup step so they are served from cache.
• Add a job timeout so a hung step cannot burn hours of runner time.

What Latchkey heals here

This workflow has steps that commonly fail on transient issues (network, registries, flaky browsers). On Latchkey managed runners they are detected, retried, and self-healed instead of failing your build:

• Dependency installs

This workflow runs 1 job per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.

Actions used in this workflow