Skip to content

- Renaming packages based on purpose instead of types (#29) #135

- Renaming packages based on purpose instead of types (#29)

- Renaming packages based on purpose instead of types (#29) #135

Triggered via push November 7, 2024 21:57
Status Success
Total duration 2m 54s
Artifacts

go.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
test
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
check
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/