Skip to content

refactor: introduce controlchannel implementation (#51) #133

refactor: introduce controlchannel implementation (#51)

refactor: introduce controlchannel implementation (#51) #133

Triggered via push January 15, 2024 17:31
Status Success
Total duration 45s
Artifacts

build.yml

on: push
short-tests
25s
short-tests
gosec
34s
gosec
coverage-threshold
27s
coverage-threshold
integration
34s
integration
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
short-tests
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-go@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
coverage-threshold
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-go@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
gosec
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
integration
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-go@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/