Skip to content
CI

chore: use github app token for release automation #9

Sign in to view logs

chore: use github app token for release automation

chore: use github app token for release automation #9

Triggered via pull request April 7, 2026 04:31
@quettabitquettabit
opened #4
qb/gh-app
Status Failure
Total duration 6m 43s
Artifacts 1

ci.yml

on: pull_request
Build s2-lite  /  Build s2-lite
5m 58s
Build s2-lite / Build s2-lite
Local Checks (code quality, unit tests, docs build)
21s
Local Checks (code quality, unit tests, docs build)
s2-cloud integration tests
49s
s2-cloud integration tests
Matrix: s2-lite integration tests / test
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 5 warnings
s2-lite integration tests / python
Process completed with exit code 1.
s2-lite integration tests / python
The process '/usr/bin/git' failed with exit code 128
s2-lite integration tests / python
couldn't find remote ref refs/pull/4/merge
s2-lite integration tests / python
couldn't find remote ref refs/pull/4/merge
s2-lite integration tests / python
couldn't find remote ref refs/pull/4/merge
Local Checks (code quality, unit tests, docs build)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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/
s2-cloud integration tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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/
s2-cloud integration tests
Failed to save: Unable to reserve cache with key setup-uv-2-x86_64-unknown-linux-gnu-ubuntu-24.04-unknown-pruned-3dafb565ea8897fdf0b0d874c2e9502904a8f265439d8bee38a484da47dbd832, another job may be creating this cache.
Build s2-lite / Build s2-lite
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4, arduino/setup-protoc@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/
s2-lite integration tests / python
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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/

Artifacts

Produced during runtime
Name Size Digest
server-binary Expired
10.5 MB
sha256:6bfa4c38c12d354c1ea85b58d7ad6f9fab1f5d043885fd89a1a9d2b7b4c56a77