Skip to content

SCAR-84 Add info map and optional address field to service (#18) #69

SCAR-84 Add info map and optional address field to service (#18)

SCAR-84 Add info map and optional address field to service (#18) #69

Triggered via push April 15, 2026 20:10
Status Success
Total duration 2m 51s
Artifacts 3

ci.yaml

on: push
Matrix: call_ci / Create debian package with dh-virtualenv
Matrix: call_ci / Create debian package with FPM
Matrix: call_ci / Create debian package with wheel and venv
call_ci  /  Create wheel package
1m 8s
call_ci / Create wheel package
call_ci  /  Create release
7s
call_ci / Create release
Fit to window
Zoom out
Zoom in

Annotations

5 warnings and 5 notices
call_ci / Run tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: devcontainers/ci@v0.3, docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
call_ci / Create debian package with FPM (bookworm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, devcontainers/ci@v0.3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
call_ci / Create debian package with FPM (trixie)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, devcontainers/ci@v0.3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
call_ci / Create wheel package
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, devcontainers/ci@v0.3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
call_ci / Create release
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, softprops/action-gh-release@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
call_ci / Run tests
Ending action
call_ci / Run tests
This worflow is not triggered on a pull_request event, nor on a push event on a branch. Consequently, there's nothing to do. Exiting.
call_ci / Run tests
Generating comment for PR
call_ci / Run tests
HTTP Request: GET https://api.github.com/repos/EffectiveRange/python-hello "HTTP/1.1 200 OK"
call_ci / Run tests
Starting action

Artifacts

Produced during runtime
Name Size Digest
python-hello_fpm-deb_bookworm
31.8 KB
sha256:072493e9c278464933278318d0f9f44657be75b10ad6afa0f0f5b5481ff98c7c
python-hello_fpm-deb_trixie
30.7 KB
sha256:69377af2040dab5b0738897a120a339d78cb71cc6dc20f0b0db64d7e3058aa90
python-hello_wheel
11.3 KB
sha256:728c73e8b0c830d19052997fe545bb70a3e93651e6ffc3636cdde4c483ffc0e3