Skip to content
pi upgrade check

feat(admin): spend per trigger and per repo, and the COSTS table cycle (issue #175) #275

Sign in to view logs

feat(admin): spend per trigger and per repo, and the COSTS table cycle (issue #175)

feat(admin): spend per trigger and per repo, and the COSTS table cycle (issue #175) #275

Re-run triggered August 12, 2026 07:39
@edgeheroedgehero
#177
feat/cost-trigger-repo-folds
Status Success
Total duration 1m 31s
Artifacts –

pi-upgrade-check.yml

on: pull_request
pins are exact (CONST-PI-VERSION-PINNED)
8s
pins are exact (CONST-PI-VERSION-PINNED)
no automatic merge (CONST-MERGE-NEVER-AUTOMATIC)
6s
no automatic merge (CONST-MERGE-NEVER-AUTOMATIC)
pinned assumptions still hold (offline, no API key)
1m 26s
pinned assumptions still hold (offline, no API key)
the job image holds its contract
2m 6s
the job image holds its contract
the admin extension survives latest pi (canary)
25s
the admin extension survives latest pi (canary)
host-pi mirrors survive latest pi (canary)
16s
host-pi mirrors survive latest pi (canary)
Fit to window
Zoom out
Zoom in

Annotations

1 warning
pinned assumptions still hold (offline, no API key)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-node@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/