Skip to content
CI

feat: make AForge exec the default runtime #302

Sign in to view logs

feat: make AForge exec the default runtime

feat: make AForge exec the default runtime #302

Triggered via pull request August 15, 2026 03:39
@AbirAbbasAbirAbbas
opened #137
agent/aforge-exec-default
Status Success
Total duration 2m 25s
Artifacts –

ci.yml

on: pull_request
test
2m 21s
test
go
1m 5s
go
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
go
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-go@v5. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
go
The process '/usr/bin/git' failed with exit code 128
test
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-python@v5. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
test
The process '/usr/bin/git' failed with exit code 128