CI #53
piers-williamsci-tests.yml
on: schedule
rs-build-linux-x86_64
6m 5s
Matrix: dbt Plugin Tests
Python 3.14 Windows tests
3m 19s
rs-build-sdist
47s
ymlchecks
1m 13s
example tests
21s
dbt Plugin Python 3.12 Windows tests
1m 26s
pip install tests
0s
Matrix: linting
Matrix: rs-build-linux-exotic
Matrix: rs-build-macos
Matrix: rs-build-musllinux
Matrix: rs-build-windows
Matrix: dialect-tests
Matrix: Python Tests
Combine & check 100% coverage.
0s
Annotations
37 errors and 29 warnings
|
mypyc tests
Process completed with exit code 1.
|
|
docbuild tests
The strategy configuration was canceled because "linting.mypyc" failed
|
|
docbuild tests
The operation was canceled.
|
|
yamllint tests
The strategy configuration was canceled because "linting.mypyc" failed
|
|
yamllint tests
The operation was canceled.
|
|
Python 3.14 Windows tests
Process completed with exit code 1.
|
|
Python Tests (3.14, -rust) / py3.14
Process completed with exit code 1.
|
|
Python Tests (3.9) / py3.9
The strategy configuration was canceled because "python-version-tests._3_14_-rust" failed
|
|
Python Tests (3.12) / py3.12
The strategy configuration was canceled because "python-version-tests._3_14_-rust" failed
|
|
Python Tests (3.10) / py3.10
The strategy configuration was canceled because "python-version-tests._3_14_-rust" failed
|
|
Python Tests (3.12, -rust) / py3.12
The strategy configuration was canceled because "python-version-tests._3_14_-rust" failed
|
|
Python Tests (3.12, -rust) / py3.12
The operation was canceled.
|
|
Python Tests (3.13, -rust) / py3.13
The strategy configuration was canceled because "python-version-tests._3_14_-rust" failed
|
|
Python Tests (3.13, -rust) / py3.13
The operation was canceled.
|
|
Python Tests (3.11) / py3.11
The strategy configuration was canceled because "python-version-tests._3_14_-rust" failed
|
|
Python Tests (3.11) / py3.11
The operation was canceled.
|
|
Python Tests (3.10, -rust) / py3.10
The strategy configuration was canceled because "python-version-tests._3_14_-rust" failed
|
|
Python Tests (3.10, -rust) / py3.10
The operation was canceled.
|
|
Python Tests (3.11, -rust) / py3.11
The strategy configuration was canceled because "python-version-tests._3_14_-rust" failed
|
|
Python Tests (3.11, -rust) / py3.11
The operation was canceled.
|
|
Python Tests (3.9, -rust) / py3.9
The strategy configuration was canceled because "python-version-tests._3_14_-rust" failed
|
|
Python Tests (3.9, -rust) / py3.9
The operation was canceled.
|
|
Python Tests (3.14) / py3.14
The strategy configuration was canceled because "python-version-tests._3_14_-rust" failed
|
|
Python Tests (3.14) / py3.14
The operation was canceled.
|
|
Python Tests (3.13) / py3.13
The strategy configuration was canceled because "python-version-tests._3_14_-rust" failed
|
|
Python Tests (3.13) / py3.13
The operation was canceled.
|
|
CI
The strategy configuration was canceled because "python-version-tests._3_14_-rust" failed
|
|
CI
The strategy configuration was canceled because "python-version-tests._3_14_-rust" failed
|
|
CI
The strategy configuration was canceled because "python-version-tests._3_14_-rust" failed
|
|
CI
The strategy configuration was canceled because "python-version-tests._3_14_-rust" failed
|
|
CI
The strategy configuration was canceled because "python-version-tests._3_14_-rust" failed
|
|
CI
The strategy configuration was canceled because "python-version-tests._3_14_-rust" failed
|
|
CI
The strategy configuration was canceled because "python-version-tests._3_14_-rust" failed
|
|
CI
The strategy configuration was canceled because "python-version-tests._3_14_-rust" failed
|
|
CI
The strategy configuration was canceled because "python-version-tests._3_14_-rust" failed
|
|
CI
The strategy configuration was canceled because "python-version-tests._3_14_-rust" failed
|
|
CI
The strategy configuration was canceled because "python-version-tests._3_14_-rust" failed
|
|
rs-build-sdist
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/
|
|
dbt Plugin Tests (dbt170) / py3.12-dbt170
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/
|
|
dbt Plugin Tests (dbt190) / py3.12-dbt190
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/
|
|
dbt Plugin Tests (dbt180) / py3.12-dbt180
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/
|
|
dbt Plugin Tests (dbt1100) / py3.12-dbt1100
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/
|
|
rs-build-macos (macos-15, aarch64)
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/
|
|
rs-build-linux-x86_64
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/
|
|
rs-build-windows (windows-latest, x86)
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/
|
|
rs-build-musllinux (ubuntu-latest, x86_64)
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/
|
|
rs-build-musllinux (ubuntu-latest, x86)
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/
|
|
rs-build-musllinux (ubuntu-latest, armv7)
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/
|
|
rs-build-linux-exotic (armv7)
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/
|
|
rs-build-musllinux (ubuntu-latest, aarch64)
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/
|
|
rs-build-linux-exotic (aarch64)
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/
|
|
rs-build-linux-exotic (ppc64le)
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/
|
|
Python Tests (3.14, -rust) / py3.14
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-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/
|
|
rs-build-macos (macos-15-intel, x86_64)
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/
|
|
Python Tests (3.13, -rust) / py3.13
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-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/
|
|
Python Tests (3.10, -rust) / py3.10
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-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/
|
|
Python Tests (3.11, -rust) / py3.11
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-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/
|
|
Python Tests (3.9, -rust) / py3.9
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-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/
|
|
Dialect rules_suite-rust / py3.14
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, 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/
|
|
rs-build-windows (windows-latest, x64)
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/
|
|
Dialect rules_suite / py3.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/
|
|
rs-build-linux-exotic (s390x)
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/
|
|
Dialect parse_suite-rust / py3.14
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, 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/
|
|
rs-build-linux-exotic (x86)
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/
|
|
Dialect parse_suite / py3.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/
|
|
Dialect fix_suite-rust / py3.14
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
coverage-data-py3.12-dbt1100
|
1.65 KB |
sha256:903ed8598a14b0ba2d1eefe8c9ca668aa3afef2812b5a501f486a0582ea6e98b
|
|
|
coverage-data-py3.12-dbt170
|
1.64 KB |
sha256:f365f07d41ceec0aac81c1e3744a4ef002cf0144ffd985a0dcc079df1367ce7e
|
|
|
coverage-data-py3.12-dbt180
|
1.64 KB |
sha256:6dda8d36fc4ab8208a5be0004d9cddf46db4137b8c4c82dc13fbadc5284e8bfd
|
|
|
coverage-data-py3.12-dbt190
|
1.64 KB |
sha256:42df73e507fe43d636505c5ce0addd8f1f4ba7c2c727547323984794440b1739
|
|
|
coverage-data-py3.14-parse_suite
|
22.8 KB |
sha256:e9a8fda56e34f9faac36fd8960ab73986ce32e6918820cd2a1ede764bc314183
|
|
|
coverage-data-py3.14-parse_suite-rust
|
22.8 KB |
sha256:72524f028a3c1968d318c2941da594fbfbc08f9fc053f5f39e621d4c8a4ce668
|
|
|
coverage-data-py3.14-rules_suite
|
24.1 KB |
sha256:5f4e149186069e9b80a1a9c92eaaa4bdfaf18f80855ba26c7e1980b06bf2e4bd
|
|
|
coverage-data-py3.14-rules_suite-rust
|
24 KB |
sha256:3e24229da7f3c2638bb540c965bef68102fed0f3fe12ff2b245bbab2a2202d0c
|
|
|
wheels-linux-aarch64
|
241 MB |
sha256:6c7286680bb59c9ab93757b2541111e08c83258d867d4f4f6ff10d7d4261ad6e
|
|
|
wheels-linux-armv7
|
220 MB |
sha256:7267f403942ca867dffbef35f2b28a574f898947b20e3d5714244fa5a5d51694
|
|
|
wheels-linux-ppc64le
|
245 MB |
sha256:b308633da3f4d7f93900997a217b43edbbfdc253f37123797b57014c9a21fb0a
|
|
|
wheels-linux-s390x
|
250 MB |
sha256:0cf0d5c084ffcb52057a345ba889c0719aea9e5d7b8beff63205d01ddabe22ff
|
|
|
wheels-linux-x86
|
149 MB |
sha256:894790ff30969ca3df6d1066b53738d34eb42da97d9622c556b3975bf1f8ce9b
|
|
|
wheels-linux-x86_64
|
166 MB |
sha256:f525e09f25832046ddca4c259f3bb5b895af1bccbc403befb86a0346f268a2d6
|
|
|
wheels-macos-aarch64
|
18.4 MB |
sha256:24d24949292e918fd0d069db52940a71490caf51fca5cff30cf2fd33d1594ad5
|
|
|
wheels-macos-x86_64
|
17.9 MB |
sha256:9cd780f858a165b289a095e7feaff0d34b8b1895804d7adfad0d038de32b3d6b
|
|
|
wheels-musllinux-aarch64
|
243 MB |
sha256:15931e7e5c9d8d763d908d83d99b1a2f9e22f75372548458f6d47df627591894
|
|
|
wheels-musllinux-armv7
|
224 MB |
sha256:d4c2783798f2ef0d67963269315b8e20f774866a3ca36cf2025a0f197dc9d6e8
|
|
|
wheels-musllinux-x86
|
232 MB |
sha256:8facb47fe8b0cabdde603745abeda3c69ddc139fda37f8b32d2f6b19760f09a0
|
|
|
wheels-musllinux-x86_64
|
254 MB |
sha256:74fc4b3ce298368ab06d491e79c12f4026f8ea8fd725336048b3f3df1496dc78
|
|
|
wheels-sdist
|
188 KB |
sha256:54c1ac26a9386fbea855ae6cecd5f357255400e2e379451a20335dc60fba01fe
|
|
|
wheels-windows-x64
|
21.3 MB |
sha256:6d9cfe484f5dfdf17a1ba0358da6cc68cd363b28995523dcb16a721ab73231f5
|
|
|
wheels-windows-x86
|
4.08 MB |
sha256:0545ccd6ea2c5f76f336b00e2191b2b4ecd5726cf223eb345bb8491d730bec8b
|
|