chore(ci): match sibling Forgejo runner and bump checkout to v5 #7
Loading…
Reference in a new issue
No description provided.
Delete branch "chore/bump-runners-and-checkout"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Clear the Node.js 20 deprecation warning and align the Forgejo runner with the other a8n-run repos.
The deprecation warning is emitted by actions/checkout@v4, whose action runtime is Node 20. Bump checkout to v5 (Node 24) in both the Forgejo and GitHub test workflows to clear it.
Switch the Forgejo workflow off ubuntu-act-22.04 to vars.RUNS_ON_OPENSUSE_BASE_LATEST, the runner used by 169 of the sibling workflows. The ubuntu-act-* images grow large with little cleanup, so the shared openSUSE base keeps this repo consistent and avoids that disk pressure.
The GitHub workflow already runs on ubuntu-latest, which tracks the newest hosted image (currently 24.04), so only its checkout pin changed there.