Edge API key expiry reminder workflow (ChatGPTBox-dev/chatGPTBox)
The Edge API key expiry reminder workflow from ChatGPTBox-dev/chatGPTBox, explained and optimized by Latchkey.
CI health: C - fair
Point runs-on at Latchkey and get caching, job timeouts, self-healing for flaky steps, and up to 58% lower cost, applied automatically.
What it does
This is the Edge API key expiry reminder workflow from the ChatGPTBox-dev/chatGPTBox 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: Edge API key expiry reminder
on:
schedule:
- cron: '0 3 * * 1'
workflow_dispatch:
permissions:
contents: read
jobs:
check-edge-api-key-expiry:
runs-on: ubuntu-latest
env:
EDGE_API_KEY_EXPIRES_AT: ${{ secrets.EDGE_API_KEY_EXPIRES_AT }}
steps:
- name: Checkout
uses: actions/checkout@v7
- name: Setup Node.js
uses: actions/setup-node@v6
with:
node-version: 22
- name: Check Edge API key expiry
run: node scripts/check-edge-api-key-expiry.mjs
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: Edge API key expiry reminder on: schedule: - cron: '0 3 * * 1' workflow_dispatch: permissions: contents: read jobs: check-edge-api-key-expiry: timeout-minutes: 30 runs-on: latchkey-small env: EDGE_API_KEY_EXPIRES_AT: ${{ secrets.EDGE_API_KEY_EXPIRES_AT }} steps: - name: Checkout uses: actions/checkout@v7 - name: Setup Node.js uses: actions/setup-node@v6 with: cache: 'npm' node-version: 22 - name: Check Edge API key expiry run: node scripts/check-edge-api-key-expiry.mjs
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 useslatchkey-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.
This workflow runs 1 job per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.