[v3-2-test] Fix flaky test_migration_stairway by retrying each migrat… #32538
potiukci-amd-arm.yml
on: push
Matrix: Build CI images / build-ci-images
Matrix: Airflow CTL tests / distributions-tests
Basic tests
/
Breeze unit tests
1m 2s
Basic tests
/
Breeze integration tests
1m 26s
Basic tests
/
Scripts tests
19s
Basic tests
/
React UI tests
1m 42s
Basic tests
/
Check translation completeness
26s
Basic tests
/
Static checks: basic checks only
Basic tests
/
Test git clone on Windows
20s
Basic tests
/
Test Airflow release commands
5m 56s
Basic tests
/
Test Airflow standalone commands
26s
Go SDK tests
38s
Matrix: Generate constraints / generate-constraints-matrix
Matrix: MySQL tests: core / tests
Waiting for pending jobs
Matrix: MySQL tests: providers / tests
Waiting for pending jobs
Matrix: Non-DB tests: core / tests
Matrix: Non-DB tests: providers / tests
Matrix: Postgres tests: core / tests
Matrix: Postgres tests: providers / tests
Matrix: Sqlite tests: core / tests
Matrix: Sqlite tests: providers / tests
Matrix: Task SDK tests / distributions-tests
Matrix: Low dep tests:core / tests
Matrix: Low dep tests: providers / tests
Matrix: Additional CI image checks / Push Early Image Cache / push-ci-image-cache
Waiting for pending jobs
Matrix: Additional CI image checks / Push Early Image Cache / push-prod-image-cache
Waiting for pending jobs
Matrix: CI image checks / Build documentation
Matrix: provider distributions tests / prepare-install-verify-provider-distributions
Waiting for pending jobs
Matrix: provider distributions tests / providers-compatibility-tests-matrix
Waiting for pending jobs
Matrix: Helm tests / tests-helm
Waiting for pending jobs
Matrix: Integration and System Tests / tests-core-integration
Matrix: Integration and System Tests / tests-providers-integration
Matrix: Special tests / Latest Boto test: core / tests
Matrix: Special tests / Latest Boto test: providers / tests
Matrix: Special tests / Latest SQLAlchemy test: providers / tests
Matrix: Special tests / Latest SQLAlchemy test: core / tests
Matrix: Special tests / Min SQLAlchemy test: providers / tests
Matrix: Special tests / Min SQLAlchemy test: core / tests
Matrix: Special tests / Pendulum2 test: core / tests
Matrix: Special tests / Pendulum2 test: providers / tests
Matrix: Special tests / Quarantined test: core / tests
Matrix: Special tests / Quarantined test: providers / tests
Matrix: tests-special / tests-system-core / tests
Additional CI image checks
/
Check that image builds quickly
CI image checks
/
Static checks
28m 12s
CI image checks
/
Test Python API client
7m 4s
MyPy providers checks
Integration and System Tests
/
System Tests
6m 32s
Helm tests
/
Release Helm
Build PROD images
/
Build Airflow and provider distributions
3m 45s
CI image checks
/
Publish documentation and validate versions
5m 43s
Summarize warnings
0s
Matrix: Build PROD images / build-prod-images
Additional PROD image tests
/
...
/
Build Airflow and provider distributions
Additional PROD image tests
/
...
/
Build Airflow and provider distributions
38s
Additional PROD image tests
/
Test examples of PROD image building
3m 10s
Additional PROD image tests
/
Docker Compose quick start with PROD image verifying
4m 27s
Additional PROD image tests
/
Task SDK integration tests with PROD image
3m 56s
Additional PROD image tests
/
...
/
Regular e2e test
9m 58s
Additional PROD image tests
/
...
/
Remote logging e2e test
4m 32s
Additional PROD image tests
/
...
/
Elasticsearch remote logging e2e test
4m 28s
Additional PROD image tests
/
...
/
XCom object storage backend e2e test
4m 31s
Additional PROD image tests
/
Airflow CTL integration tests with PROD image
5m 17s
Additional PROD image tests
/
...
/
test-ui-e2e-tests
Additional PROD image tests
/
...
/
test-ui-e2e-tests
Additional PROD image tests
/
...
/
test-ui-e2e-tests
Matrix: Kubernetes tests / tests-kubernetes
Matrix: Additional PROD image tests / PROD image extra checks (main) / pip-image / build-prod-images
Waiting for pending jobs
Matrix: Additional PROD image tests / PROD image extra checks (release) / pip-image / build-prod-images
Matrix: Finalize tests / dependency-upgrade-summary
Waiting for pending jobs
Matrix: finalize-tests / push-buildx-cache-to-github-registry / push-ci-image-cache
Waiting for pending jobs
Matrix: finalize-tests / push-buildx-cache-to-github-registry / push-prod-image-cache
Waiting for pending jobs
Notify Slack
0s
Annotations
47 errors and 87 warnings
|
Additional PROD image tests / PROD image extra checks (release) / pip-image / Build PROD pip image 3.10
Canceling since a higher priority waiting request for ci-amd-arm-refs/heads/v3-2-test exists
|
|
Additional PROD image tests / PROD image extra checks (release) / pip-image / Build PROD pip image 3.10
The operation was canceled.
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.12-v1.32.8-true
Canceling since a higher priority waiting request for ci-amd-arm-refs/heads/v3-2-test exists
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.12-v1.32.8-true
The operation was canceled.
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.11-v1.31.12-true
Canceling since a higher priority waiting request for ci-amd-arm-refs/heads/v3-2-test exists
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.11-v1.31.12-true
The operation was canceled.
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.10-v1.35.0-true
Canceling since a higher priority waiting request for ci-amd-arm-refs/heads/v3-2-test exists
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.10-v1.35.0-true
The operation was canceled.
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.10-v1.30.13-true
Canceling since a higher priority waiting request for ci-amd-arm-refs/heads/v3-2-test exists
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.10-v1.30.13-true
The operation was canceled.
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.13-v1.33.4-false
Canceling since a higher priority waiting request for ci-amd-arm-refs/heads/v3-2-test exists
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.13-v1.33.4-false
The operation was canceled.
|
|
Kubernetes tests / K8S System:CeleryExecutor-3.10-v1.30.13-false
Canceling since a higher priority waiting request for ci-amd-arm-refs/heads/v3-2-test exists
|
|
Kubernetes tests / K8S System:CeleryExecutor-3.10-v1.30.13-false
The operation was canceled.
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.14-v1.34.0-true
Canceling since a higher priority waiting request for ci-amd-arm-refs/heads/v3-2-test exists
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.14-v1.34.0-true
The operation was canceled.
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.10-v1.35.0-false
Canceling since a higher priority waiting request for ci-amd-arm-refs/heads/v3-2-test exists
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.10-v1.35.0-false
The operation was canceled.
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.11-v1.31.12-false
Canceling since a higher priority waiting request for ci-amd-arm-refs/heads/v3-2-test exists
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.11-v1.31.12-false
The operation was canceled.
|
|
Kubernetes tests / K8S System:CeleryExecutor-3.12-v1.32.8-true
Canceling since a higher priority waiting request for ci-amd-arm-refs/heads/v3-2-test exists
|
|
Kubernetes tests / K8S System:CeleryExecutor-3.11-v1.31.12-true
Canceling since a higher priority waiting request for ci-amd-arm-refs/heads/v3-2-test exists
|
|
Kubernetes tests / K8S System:CeleryExecutor-3.14-v1.34.0-true
Canceling since a higher priority waiting request for ci-amd-arm-refs/heads/v3-2-test exists
|
|
Kubernetes tests / K8S System:CeleryExecutor-3.12-v1.32.8-true
The operation was canceled.
|
|
Kubernetes tests / K8S System:CeleryExecutor-3.11-v1.31.12-true
The operation was canceled.
|
|
Kubernetes tests / K8S System:CeleryExecutor-3.14-v1.34.0-true
The operation was canceled.
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.14-v1.34.0-false
Canceling since a higher priority waiting request for ci-amd-arm-refs/heads/v3-2-test exists
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.14-v1.34.0-false
The operation was canceled.
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.13-v1.33.4-true
Canceling since a higher priority waiting request for ci-amd-arm-refs/heads/v3-2-test exists
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.13-v1.33.4-true
The operation was canceled.
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.12-v1.32.8-false
Canceling since a higher priority waiting request for ci-amd-arm-refs/heads/v3-2-test exists
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.12-v1.32.8-false
The operation was canceled.
|
|
Kubernetes tests / K8S System:CeleryExecutor-3.10-v1.35.0-true
Canceling since a higher priority waiting request for ci-amd-arm-refs/heads/v3-2-test exists
|
|
Kubernetes tests / K8S System:CeleryExecutor-3.10-v1.35.0-true
The operation was canceled.
|
|
Kubernetes tests / K8S System:CeleryExecutor-3.11-v1.31.12-false
Canceling since a higher priority waiting request for ci-amd-arm-refs/heads/v3-2-test exists
|
|
Kubernetes tests / K8S System:CeleryExecutor-3.11-v1.31.12-false
The operation was canceled.
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.10-v1.30.13-false
Canceling since a higher priority waiting request for ci-amd-arm-refs/heads/v3-2-test exists
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.10-v1.30.13-false
The operation was canceled.
|
|
Kubernetes tests / K8S System:CeleryExecutor-3.13-v1.33.4-true
Canceling since a higher priority waiting request for ci-amd-arm-refs/heads/v3-2-test exists
|
|
Kubernetes tests / K8S System:CeleryExecutor-3.13-v1.33.4-true
The operation was canceled.
|
|
Kubernetes tests / K8S System:CeleryExecutor-3.10-v1.30.13-true
Canceling since a higher priority waiting request for ci-amd-arm-refs/heads/v3-2-test exists
|
|
Kubernetes tests / K8S System:CeleryExecutor-3.10-v1.30.13-true
The operation was canceled.
|
|
Tests
Canceling since a higher priority waiting request for ci-amd-arm-refs/heads/v3-2-test exists
|
|
Tests
Canceling since a higher priority waiting request for ci-amd-arm-refs/heads/v3-2-test exists
|
|
Tests
Canceling since a higher priority waiting request for ci-amd-arm-refs/heads/v3-2-test exists
|
|
Tests
Canceling since a higher priority waiting request for ci-amd-arm-refs/heads/v3-2-test exists
|
|
Tests
Canceling since a higher priority waiting request for ci-amd-arm-refs/heads/v3-2-test exists
|
|
Basic tests / React UI tests
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. 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/
|
|
Build CI images / Build CI linux/arm64 image 3.10
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. 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/
|
|
Build CI images / Build CI linux/arm64 image 3.11
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. 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/
|
|
Build CI images / Build CI linux/arm64 image 3.12
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. 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/
|
|
Build CI images / Build CI linux/arm64 image 3.13
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. 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/
|
|
Build CI images / Build CI linux/arm64 image 3.14
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. 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/
|
|
Non-DB tests: core / Non-DB-core::3.13:Core...Serialization
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Non-DB tests: core / Non-DB-core::3.11:Core...Serialization
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Non-DB tests: core / Non-DB-core::3.14:Core...Serialization
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Non-DB tests: core / Non-DB-core::3.10:Core...Serialization
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Non-DB tests: core / Non-DB-core::3.12:API...CLI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Special tests / System test: / System-core:SystemTest:14:3.10:API...CLI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Special tests / Quarantined test: core / Qrnt-core:Postgres:14:3.10:Core...Serialization
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Special tests / Quarantined test: core / Qrnt-core:Postgres:14:3.10:API...CLI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Non-DB tests: core / Non-DB-core::3.12:Core...Serialization
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Non-DB tests: core / Non-DB-core::3.13:API...CLI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Non-DB tests: core / Non-DB-core::3.11:API...CLI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Integration and System Tests / Integration core redis
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Integration and System Tests / System Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Non-DB tests: core / Non-DB-core::3.10:API...CLI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Special tests / System test: / System-core:SystemTest:14:3.10:Core...Serialization
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Non-DB tests: core / Non-DB-core::3.14:API...CLI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Integration and System Tests / Integration core otel
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Sqlite tests: core / DB-core:Sqlite:3.13:Core...Serialization
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Sqlite tests: core / DB-core:Sqlite:3.11:Core...Serialization
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Sqlite tests: core / DB-core:Sqlite:3.12:Core...Serialization
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Sqlite tests: core / DB-core:Sqlite:3.14:Core...Serialization
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Postgres tests: core / DB-core:Postgres:18:3.14:Core...Serialization
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Low dep tests:core / All-core:LowestDeps:14:3.14:Core...Serialization
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Postgres tests: core / DB-core:Postgres:15:3.11:Core...Serialization
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Special tests / Min SQLAlchemy test: core / DB-core:MinSQLAlchemy-Postgres:14:3.10:Core...Serialization
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Special tests / Latest SQLAlchemy test: core / DB-core:LatestSQLAlchemy-Postgres:14:3.10:Core...Serialization
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Postgres tests: core / DB-core:Postgres:17:3.13:Core...Serialization
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Low dep tests:core / All-core:LowestDeps:14:3.13:Core...Serialization
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Sqlite tests: core / DB-core:Sqlite:3.10:Core...Serialization
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Postgres tests: core / DB-core:Postgres:16:3.12:Core...Serialization
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Special tests / Latest Boto test: core / All-core:LatestBoto-Postgres:14:3.10:Core...Serialization
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
CI image checks / Static checks
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. 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/
|
|
Low dep tests:core / All-core:LowestDeps:14:3.12:Core...Serialization
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Special tests / Pendulum2 test: core / All-core:Pendulum2-Postgres:14:3.10:Core...Serialization
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Build PROD images / Build PROD Regular image 3.10
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. 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/
|
|
Low dep tests:core / All-core:LowestDeps:14:3.11:Core...Serialization
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Low dep tests:core / All-core:LowestDeps:14:3.10:Core...Serialization
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Postgres tests: core / DB-core:Postgres:14:3.10:Core...Serialization
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Sqlite tests: core / DB-core:Sqlite:3.14:API...CLI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Postgres tests: core / DB-core:Postgres:18:3.14:API...CLI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Sqlite tests: core / DB-core:Sqlite:3.11:API...CLI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Sqlite tests: core / DB-core:Sqlite:3.12:API...CLI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Postgres tests: core / DB-core:Postgres:15:3.11:API...CLI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Sqlite tests: core / DB-core:Sqlite:3.13:API...CLI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Low dep tests:core / All-core:LowestDeps:14:3.14:API...CLI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Special tests / Latest SQLAlchemy test: core / DB-core:LatestSQLAlchemy-Postgres:14:3.10:API...CLI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Postgres tests: core / DB-core:Postgres:16:3.12:API...CLI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Postgres tests: core / DB-core:Postgres:17:3.13:API...CLI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Special tests / Min SQLAlchemy test: core / DB-core:MinSQLAlchemy-Postgres:14:3.10:API...CLI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Low dep tests:core / All-core:LowestDeps:14:3.11:API...CLI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Sqlite tests: core / DB-core:Sqlite:3.10:API...CLI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Special tests / Latest Boto test: core / All-core:LatestBoto-Postgres:14:3.10:API...CLI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Special tests / Pendulum2 test: core / All-core:Pendulum2-Postgres:14:3.10:API...CLI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Low dep tests:core / All-core:LowestDeps:14:3.12:API...CLI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Low dep tests:core / All-core:LowestDeps:14:3.13:API...CLI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Postgres tests: core / DB-core:Postgres:14:3.10:API...CLI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Build PROD images / Build PROD Regular image 3.11
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. 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/
|
|
Low dep tests:core / All-core:LowestDeps:14:3.10:API...CLI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
Build PROD images / Build PROD Regular image 3.13
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. 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/
|
|
Build PROD images / Build PROD Regular image 3.12
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. 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/
|
|
Build PROD images / Build PROD Regular image 3.14
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. 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/
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.12-v1.32.8-true
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.11-v1.31.12-true
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.10-v1.35.0-true
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.10-v1.30.13-true
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.13-v1.33.4-false
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
Kubernetes tests / K8S System:CeleryExecutor-3.10-v1.30.13-false
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.14-v1.34.0-true
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.10-v1.35.0-false
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.11-v1.31.12-false
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
Kubernetes tests / K8S System:CeleryExecutor-3.12-v1.32.8-true
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
Kubernetes tests / K8S System:CeleryExecutor-3.11-v1.31.12-true
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
Kubernetes tests / K8S System:CeleryExecutor-3.14-v1.34.0-true
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.14-v1.34.0-false
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.13-v1.33.4-true
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.12-v1.32.8-false
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
Kubernetes tests / K8S System:CeleryExecutor-3.10-v1.35.0-true
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
Kubernetes tests / K8S System:CeleryExecutor-3.11-v1.31.12-false
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
Kubernetes tests / K8S System:KubernetesExecutor-3.10-v1.30.13-false
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
Kubernetes tests / K8S System:CeleryExecutor-3.13-v1.33.4-true
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
|
Kubernetes tests / K8S System:CeleryExecutor-3.10-v1.30.13-true
No files were found with the provided path: /tmp/kind_logs_*. No artifacts will be uploaded.
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
airflow-docs
|
41.7 MB |
sha256:f3dbe83341adf1f80aeb931783da9620ca205f9b5dfc9e6091d4230353213b16
|
|
|
cache-prek-v9-linux_arm64-python3.10.20-uv0.11.8-757f121b564d8c2d6da7cfc052a73a7b924f8facd3d9972455f5c679c6ed393e-v3-2-test
Expired
|
248 MB |
sha256:952181f0bb0dfadb980449165ae410e573a7fb8d0a87a3d765ccc86d54735e64
|
|
|
cache-ui-node-modules-v1-Linux--v3-2-test
Expired
|
50.2 MB |
sha256:38aac06a9803501f2641e81b7e72627459e3151c5ddf529da9900e0e0a4014de
|
|
|
ci-cache-mount-save-v3-linux_arm64-3.10-v3-2-test
Expired
|
469 MB |
sha256:c57505978a20c316559fa36b20c4a72f211636d64b6d3164c4439ab110c03dd9
|
|
|
ci-cache-mount-save-v3-linux_arm64-3.11-v3-2-test
Expired
|
461 MB |
sha256:244fa7b31c87a3437efd510dc0cc7c280b49c344c6738469d8344a88f0a8cc5c
|
|
|
ci-cache-mount-save-v3-linux_arm64-3.12-v3-2-test
Expired
|
461 MB |
sha256:2ca1548a099b772391dd02fe3cb1de68e25689de8dda496c5dac1a76b8e09508
|
|
|
ci-cache-mount-save-v3-linux_arm64-3.13-v3-2-test
Expired
|
460 MB |
sha256:9bd23caee700b0cb82e2b745419805f9f3aa911997189054f88c07a813518b42
|
|
|
ci-cache-mount-save-v3-linux_arm64-3.14-v3-2-test
Expired
|
461 MB |
sha256:9a8e246d99c3df25457bb35b50902e71d2440681e6f58fb70c86f27f1b0700b4
|
|
|
ci-image-save-v3-linux_arm64-3.10-v3-2-test
Expired
|
2.27 GB |
sha256:5a95dd6d1fbe16b3c3b604bccbd5a03882c0de51feccfc0e91bac984f8a0e0f3
|
|
|
ci-image-save-v3-linux_arm64-3.11-v3-2-test
Expired
|
2.27 GB |
sha256:a8173ce96eb7892595251be3a0c0dfea3ab8808e4363d6353492e9496ea81f38
|
|
|
ci-image-save-v3-linux_arm64-3.12-v3-2-test
Expired
|
2.27 GB |
sha256:0e08ea2d6b45cc9370f00958e39d892c1d9bdeaa4328349cbfae7d1cddd36e1d
|
|
|
ci-image-save-v3-linux_arm64-3.13-v3-2-test
Expired
|
2.26 GB |
sha256:f408f2a6d593e591e59d2779913a1c293eebec39d257dd39ef95cbe1b650da8a
|
|
|
ci-image-save-v3-linux_arm64-3.14-v3-2-test
Expired
|
2.18 GB |
sha256:4a521e4f0d0b8abf16de9d0292c77f3229bb41d686df5457cb121e3b47e4be2b
|
|
|
constraints-3.10
|
14.7 KB |
sha256:6fbf7b6a1a4fa5a67fe464112398c878854fbb68d88ebaaeb8df3bfb8b66e10e
|
|
|
constraints-3.11
|
14.7 KB |
sha256:7f54a40683d7d8a4cee3a5eb9a3f01ba15b26a35854b93fab74b09c34a839d18
|
|
|
constraints-3.12
|
14.7 KB |
sha256:7740af8095f3f4899095ff6224e3eaeb90df7e6c828f8d4d7af56f377c6a32ab
|
|
|
constraints-3.13
|
14.6 KB |
sha256:04efdec9d15ff7ac260ef2bf26a3540d746f44db52699af367c86e4410590c45
|
|
|
constraints-3.14
|
14.4 KB |
sha256:c7f4a96b5e8c3a738c5f8d8e9d9d6135981675c63d01edd413b3f8d151995e4f
|
|
|
e2e-test-logs-basic
|
313 KB |
sha256:daf12cb300edf2414474978454e695c1eac343305d7323479967493fd8ab1603
|
|
|
e2e-test-logs-remote_log
|
20.9 KB |
sha256:62a03b67a7a9277b61f893de539b50c19baf49e602fd86092d3fe0570c923d48
|
|
|
e2e-test-logs-remote_log_elasticsearch
|
29.7 KB |
sha256:f8ae1c54c3a6b29ffa5de89285f014a89c098f3ae3e80705b0a815f61c02e331
|
|
|
e2e-test-logs-xcom_object_storage
|
31.2 KB |
sha256:f4bb0b60c5bb8397db1216f3fbad39e2220cc950fd23e199b075cc354f3ebd67
|
|
|
prod-image-save-v3-linux_arm64-3.10-v3-2-test
Expired
|
630 MB |
sha256:a95f8a715a91885bc69e9a0e80b6b38b75f70ee58d19adee5add6a2b0c159f07
|
|
|
prod-image-save-v3-linux_arm64-3.11-v3-2-test
Expired
|
629 MB |
sha256:9958896e9bb600e87870a3d10cd19591d8919fc9e515a9afffb5fffce6021b3e
|
|
|
prod-image-save-v3-linux_arm64-3.12-v3-2-test
Expired
|
625 MB |
sha256:5c447fc8465841fb18f1dcb6e735aecb4dfb5632e779e9292f060c3b55bf282d
|
|
|
prod-image-save-v3-linux_arm64-3.13-v3-2-test
Expired
|
616 MB |
sha256:0f778ef880c71479bd9ad5a89a3ccb64afafc7eb76f7e4ec4ca9b306b0f4e92a
|
|
|
prod-image-save-v3-linux_arm64-3.14-v3-2-test
Expired
|
538 MB |
sha256:c0edce60333911df83c509bc25f7a2afbf36d09933079070146b570d4a552b41
|
|
|
prod-packages
|
5.37 MB |
sha256:4b6bfe1614378be8eceaf4f69c8a3ac062d9d3fbd7d1382ea313005c642fa760
|
|
|
slack-state-inventory-v3-2-test
|
209 Bytes |
sha256:c0787c4eac39d45250333258a8fad33fd15e80e6f7f58b4c68687c20cc813d4e
|
|
|
test-warnings-core-API...CLI-All-LatestBoto-Postgres-postgres-14-3.10
|
40.1 KB |
sha256:67bd09c74bab168a898a7d5929e43f31c4b05e00557941dcb4cc73a5d11d79ba
|
|
|
test-warnings-core-API...CLI-All-LowestDeps-sqlite-14-3.10
|
33.5 KB |
sha256:f4137539554f7303469c1bd6549d98a60a97c7e5061789d6b18789f3ecfa14e5
|
|
|
test-warnings-core-API...CLI-All-LowestDeps-sqlite-14-3.11
|
33.5 KB |
sha256:3f10441213ea83e93033cfe999b2fa94003af976d18a01d00680096a7dfe0a25
|
|
|
test-warnings-core-API...CLI-All-LowestDeps-sqlite-14-3.12
|
58.9 KB |
sha256:ea8741f7c0464416274f119e4921a23db6141727cac0a1bdfa50e84a063f2d6e
|
|
|
test-warnings-core-API...CLI-All-LowestDeps-sqlite-14-3.13
|
68.3 KB |
sha256:57d443b75b065a47ce0218165972fbde4711cfe81497b7adff5af71c26d39307
|
|
|
test-warnings-core-API...CLI-All-LowestDeps-sqlite-14-3.14
|
33.8 KB |
sha256:694b12b7cef547d518ce38892b12f1d829516d85e4a6cbeab06b67f173b90e3b
|
|
|
test-warnings-core-API...CLI-All-Pendulum2-Postgres-postgres-14-3.10
|
39.9 KB |
sha256:075d989ede07a62f264faf300bccac4ea1f5a88d9ac394c7b9bd0add970b47b3
|
|
|
test-warnings-core-API...CLI-DB-LatestSQLAlchemy-Postgres-postgres-14-3.10
|
35.6 KB |
sha256:f80837a752719935b049948d36c00e5f3de264a116895ed73221355fcbcf26c6
|
|
|
test-warnings-core-API...CLI-DB-MinSQLAlchemy-Postgres-postgres-14-3.10
|
35.6 KB |
sha256:32741d41ac9b12dfff2cf85759cffb87eeb743312b50119311a130f0bd0fdb37
|
|
|
test-warnings-core-API...CLI-DB-Postgres-postgres-14-3.10
|
35.6 KB |
sha256:1b66b796a69c28646f06f7d2babc83720109e0955affbbdd11ecb0e5f608348a
|
|
|
test-warnings-core-API...CLI-DB-Postgres-postgres-15-3.11
|
35.1 KB |
sha256:2f93844226570971dcbad110f19fba1bab6dcd83ce1a46213fbdb1eb79600219
|
|
|
test-warnings-core-API...CLI-DB-Postgres-postgres-16-3.12
|
33.3 KB |
sha256:949142298ee000c4c26725b307c5f533a6d879a8a39359e949714e6fea947a71
|
|
|
test-warnings-core-API...CLI-DB-Postgres-postgres-17-3.13
|
33.3 KB |
sha256:7418d54cdaca95b6cef43e3d2b48920a514ff7d7440cf923ad158873b4f832ef
|
|
|
test-warnings-core-API...CLI-DB-Postgres-postgres-18-3.14
|
33.2 KB |
sha256:3e76cc715185f2eadb6d136922b03d65b7bc32b867b6cbecdfeac5b5c79b07d0
|
|
|
test-warnings-core-API...CLI-DB-Sqlite-sqlite--3.10
|
35.7 KB |
sha256:f3ef4de9387c387705cd7a76fd7f5d8d1f7ac13d08970407fdd1bcaf7f3dd2d1
|
|
|
test-warnings-core-API...CLI-DB-Sqlite-sqlite--3.11
|
35.2 KB |
sha256:01642ae7ca79fda545dd83be7594b9b1781d36433e602223d5ef99df6c4c06d8
|
|
|
test-warnings-core-API...CLI-DB-Sqlite-sqlite--3.12
|
33.4 KB |
sha256:054b6c8dba3052612794220c54edaf3deb23991a1316114012405412188b3553
|
|
|
test-warnings-core-API...CLI-DB-Sqlite-sqlite--3.13
|
33.4 KB |
sha256:0175a9da0014d673f16fb73ee266b5ebce450ac4915f32d2c80c45592b100602
|
|
|
test-warnings-core-API...CLI-DB-Sqlite-sqlite--3.14
|
33.3 KB |
sha256:f1fb8b62ba5e2139f43f18193bd669b8e425c9b21747ec7a734b72320d485434
|
|
|
test-warnings-core-API...CLI-Non-DB--sqlite--3.10
|
5.28 KB |
sha256:ae6096e2abeb1b0479146cc76f7e4dbab10f2fed1ec02973fbd3e0ea1e43aa99
|
|
|
test-warnings-core-API...CLI-Non-DB--sqlite--3.11
|
4.71 KB |
sha256:0f3a871c9fb58d214b591d98dceba2987e9d32d5bebeeebe08dedbbcc1568a2f
|
|
|
test-warnings-core-API...CLI-Non-DB--sqlite--3.12
|
2.89 KB |
sha256:3c445a2b42920bb072d4192a8207bf100b73771b39c880685e170e66a6b565e2
|
|
|
test-warnings-core-API...CLI-Non-DB--sqlite--3.13
|
2.9 KB |
sha256:328f6064dab32d9522e2a8efe5a16cfe23d30a8c154591c90d0e46d5d3223513
|
|
|
test-warnings-core-API...CLI-Non-DB--sqlite--3.14
|
2.89 KB |
sha256:39c9c105a8ede3a5d6274f6e0037ffd97f24ce7de0f3a3d59a529d2dd39c0f84
|
|
|
test-warnings-core-API...CLI-Quarantined-Postgres-postgres-14-3.10
|
468 Bytes |
sha256:ef8092662771d643094e2468890d515218de269c39b7ecbce4834f36b31a0ea5
|
|
|
test-warnings-core-Core...Serialization-All-LatestBoto-Postgres-postgres-14-3.10
|
10 KB |
sha256:33c68335fe1a69769d105381d163acb26c336f3c941a517beaa1e7508dbbc218
|
|
|
test-warnings-core-Core...Serialization-All-LowestDeps-sqlite-14-3.10
|
9.69 KB |
sha256:7b717c6c58ab6f2e5b21ec05060e95d3424ecb3e4a6ed6770227adf04fc42973
|
|
|
test-warnings-core-Core...Serialization-All-LowestDeps-sqlite-14-3.11
|
9.67 KB |
sha256:9852645e08bd3f9b84b1e366db115aeb47aeb7001d75544181a9379dc87b3663
|
|
|
test-warnings-core-Core...Serialization-All-LowestDeps-sqlite-14-3.12
|
10.9 KB |
sha256:904f44b51bbc6e2eea47551c979279196847846ab0a31c473f670b665153bc0a
|
|
|
test-warnings-core-Core...Serialization-All-LowestDeps-sqlite-14-3.13
|
11 KB |
sha256:9c5d633d57cede93cbbd187a9d7df3c98ac853209a37a9d06d6945300680471b
|
|
|
test-warnings-core-Core...Serialization-All-LowestDeps-sqlite-14-3.14
|
10.1 KB |
sha256:ddc303705c2977d079a6b9d28d6973aaf7960a2eaaed4e7c29bd3fd11d32b7e7
|
|
|
test-warnings-core-Core...Serialization-All-Pendulum2-Postgres-postgres-14-3.10
|
10 KB |
sha256:6e508fce45dc1c0a66d86b7e9cd5e4f8c44f1b97f1582e505ddbe0ae970f0c55
|
|
|
test-warnings-core-Core...Serialization-DB-LatestSQLAlchemy-Postgres-postgres-14-3.10
|
8.35 KB |
sha256:a09a7e21a70fcdf577b8adb61d61e8857c3eea4dd94b347b0046185d31a5b87a
|
|
|
test-warnings-core-Core...Serialization-DB-MinSQLAlchemy-Postgres-postgres-14-3.10
|
8.36 KB |
sha256:a135e3de983b82092818091e41bdfdb850860c2174427804f60fe069f24279fe
|
|
|
test-warnings-core-Core...Serialization-DB-Postgres-postgres-14-3.10
|
8.34 KB |
sha256:c701b18d185572f5fb87718fd475b2f559df600f7a2c3fd0e56bc427cc7d798d
|
|
|
test-warnings-core-Core...Serialization-DB-Postgres-postgres-15-3.11
|
8.35 KB |
sha256:fdfa6c8c7381e51ed3fdb6085bf25f4285d6c94770f4899362538fb504ee24ff
|
|
|
test-warnings-core-Core...Serialization-DB-Postgres-postgres-16-3.12
|
9.33 KB |
sha256:b452c258605bd369b75eedcb99f187a1e783b742e95254d55efe77e885e9e035
|
|
|
test-warnings-core-Core...Serialization-DB-Postgres-postgres-17-3.13
|
9.32 KB |
sha256:6de72208c4a1dea1553bec69e03e67a949cc9eded4f20b28e5f2efae5ba0cb08
|
|
|
test-warnings-core-Core...Serialization-DB-Postgres-postgres-18-3.14
|
8.8 KB |
sha256:3b23e5c6b5bda2e652c51514246f31d2d564be64c23e9d42f02a428587ab565f
|
|
|
test-warnings-core-Core...Serialization-DB-Sqlite-sqlite--3.10
|
8.54 KB |
sha256:3571071f182ac2f622384d5be270e8140ca90bed5e120c1b38dde5986e736929
|
|
|
test-warnings-core-Core...Serialization-DB-Sqlite-sqlite--3.11
|
8.51 KB |
sha256:fa4b1adc95775062a49c9ab74a4de66c02eba3ae073e09584689d69a7db8708b
|
|
|
test-warnings-core-Core...Serialization-DB-Sqlite-sqlite--3.12
|
9.59 KB |
sha256:e6abd4f3cc35bebaa73f720eeda0d443fbb4246949ad31ce5333153366c3b36d
|
|
|
test-warnings-core-Core...Serialization-DB-Sqlite-sqlite--3.13
|
9.59 KB |
sha256:e25bbdc1552f4c426d1712a9baaa4ad5ea393ce748da9e5d803b264012771ef2
|
|
|
test-warnings-core-Core...Serialization-DB-Sqlite-sqlite--3.14
|
9.03 KB |
sha256:e66d08e7f47c2abaf573a8d35611c3874e7c27a0db92155db613b1f1d2ac30bc
|
|
|
test-warnings-core-Core...Serialization-Non-DB--sqlite--3.10
|
2.36 KB |
sha256:2b82c798d7f5f130583776b02804888c26ef109769334e13c3e327887820ee39
|
|
|
test-warnings-core-Core...Serialization-Non-DB--sqlite--3.11
|
2.36 KB |
sha256:2cb26b43e2c6e65458c6e5f8e8b653893e56d1dcc25048e6791b0e9ae311aade
|
|
|
test-warnings-core-Core...Serialization-Non-DB--sqlite--3.12
|
2.35 KB |
sha256:a1dc1fa5a26e9c4fd7a328a522eb38da778bc6a18c035a5519ed40f83b4e5422
|
|
|
test-warnings-core-Core...Serialization-Non-DB--sqlite--3.13
|
2.37 KB |
sha256:0baa5c65397ca8ae86097b6dfb88b2276cf33cdedc08bdd264d98b0c2c42d44c
|
|
|
test-warnings-core-Core...Serialization-Non-DB--sqlite--3.14
|
2.36 KB |
sha256:5803be2bc7d4f8ed316452304cfc66fc3996d94d21bbe8f1be70961494efc225
|
|
|
test-warnings-core-Core...Serialization-Quarantined-Postgres-postgres-14-3.10
|
468 Bytes |
sha256:92de120ae88985daa74d27f6cf92e7f4b3d8b88bc265b9b449b791e3b9e1482b
|
|