chore(deps): lock file maintenance #599
ci.yaml
on: push
pre
7s
Matrix: tests
β
Result
3s
π Upload Coverage
0s
Matrix: π Upload test results
Annotations
27 errors and 78 warnings
|
β¨ Lint
Process completed with exit code 1.
|
|
π¬ unit on 3.13
Process completed with exit code 1.
|
|
π¬ unit-no-extras on 3.12
Process completed with exit code 1.
|
|
π¬ unit on 3.12
Process completed with exit code 1.
|
|
π¬ unit on 3.11
Process completed with exit code 1.
|
|
π¬ unit-no-extras on 3.10
Process completed with exit code 1.
|
|
π¬ unit-no-extras on 3.13
Process completed with exit code 1.
|
|
π¬ unit on 3.10
Process completed with exit code 1.
|
|
π¬ unit on 3.14
Process completed with exit code 1.
|
|
π¬ unit-no-extras on 3.14
Process completed with exit code 1.
|
|
π¬ integration-sqlite on 3.13
Process completed with exit code 1.
|
|
π¬ integration-sqlite on 3.11
Process completed with exit code 1.
|
|
π¬ integration-sqlite on 3.10
Process completed with exit code 1.
|
|
π¬ unit-no-extras on 3.11
Process completed with exit code 1.
|
|
π¬ integration-mysql on 3.11
Process completed with exit code 1.
|
|
π¬ integration-mysql on 3.12
Process completed with exit code 1.
|
|
π¬ integration-mysql on 3.10
Process completed with exit code 1.
|
|
π¬ integration-sqlite on 3.14
Process completed with exit code 1.
|
|
π¬ integration-sqlite on 3.12
Process completed with exit code 1.
|
|
π¬ integration-mysql on 3.13
Process completed with exit code 1.
|
|
π¬ integration-mysql on 3.14
Process completed with exit code 1.
|
|
π¬ integration-postgres on 3.14
Process completed with exit code 1.
|
|
π¬ integration-postgres on 3.13
Process completed with exit code 1.
|
|
π¬ integration-postgres on 3.10
Process completed with exit code 1.
|
|
π¬ integration-postgres on 3.11
Process completed with exit code 1.
|
|
π¬ integration-postgres on 3.12
Process completed with exit code 1.
|
|
β
Result
Process completed with exit code 1.
|
|
pre
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: fkirc/skip-duplicate-actions@f75f66ce1886f00957d99748a42c724f4330bdcf. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
π» Generate test matrix
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
β¨ Lint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
π¬ unit on 3.13
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
π¬ unit on 3.13
No files were found with the provided path: junit-unit-3.13.xml. No artifacts will be uploaded.
|
|
π¬ unit on 3.13
No files were found with the provided path: .coverage.unit-3.13. No artifacts will be uploaded.
|
|
π¬ unit-no-extras on 3.12
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
π¬ unit-no-extras on 3.12
No files were found with the provided path: junit-unit-no-extras-3.12.xml. No artifacts will be uploaded.
|
|
π¬ unit-no-extras on 3.12
No files were found with the provided path: .coverage.unit-no-extras-3.12. No artifacts will be uploaded.
|
|
π¬ unit on 3.12
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
π¬ unit on 3.12
No files were found with the provided path: junit-unit-3.12.xml. No artifacts will be uploaded.
|
|
π¬ unit on 3.12
No files were found with the provided path: .coverage.unit-3.12. No artifacts will be uploaded.
|
|
π¬ unit on 3.11
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
π¬ unit on 3.11
No files were found with the provided path: junit-unit-3.11.xml. No artifacts will be uploaded.
|
|
π¬ unit on 3.11
No files were found with the provided path: .coverage.unit-3.11. No artifacts will be uploaded.
|
|
π¬ unit-no-extras on 3.10
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
π¬ unit-no-extras on 3.10
No files were found with the provided path: junit-unit-no-extras-3.10.xml. No artifacts will be uploaded.
|
|
π¬ unit-no-extras on 3.10
No files were found with the provided path: .coverage.unit-no-extras-3.10. No artifacts will be uploaded.
|
|
π¬ unit-no-extras on 3.13
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
π¬ unit-no-extras on 3.13
No files were found with the provided path: junit-unit-no-extras-3.13.xml. No artifacts will be uploaded.
|
|
π¬ unit-no-extras on 3.13
No files were found with the provided path: .coverage.unit-no-extras-3.13. No artifacts will be uploaded.
|
|
π¬ unit on 3.10
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
π¬ unit on 3.10
No files were found with the provided path: junit-unit-3.10.xml. No artifacts will be uploaded.
|
|
π¬ unit on 3.10
No files were found with the provided path: .coverage.unit-3.10. No artifacts will be uploaded.
|
|
π¬ unit on 3.14
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
π¬ unit on 3.14
No files were found with the provided path: junit-unit-3.14.xml. No artifacts will be uploaded.
|
|
π¬ unit on 3.14
No files were found with the provided path: .coverage.unit-3.14. No artifacts will be uploaded.
|
|
π¬ unit-no-extras on 3.14
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
π¬ unit-no-extras on 3.14
No files were found with the provided path: junit-unit-no-extras-3.14.xml. No artifacts will be uploaded.
|
|
π¬ unit-no-extras on 3.14
No files were found with the provided path: .coverage.unit-no-extras-3.14. No artifacts will be uploaded.
|
|
π¬ integration-sqlite on 3.13
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f, jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-sqlite on 3.13
No files were found with the provided path: junit-integration-sqlite-3.13.xml. No artifacts will be uploaded.
|
|
π¬ integration-sqlite on 3.13
No files were found with the provided path: .coverage.integration-sqlite-3.13. No artifacts will be uploaded.
|
|
π¬ integration-sqlite on 3.11
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f, jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-sqlite on 3.11
No files were found with the provided path: junit-integration-sqlite-3.11.xml. No artifacts will be uploaded.
|
|
π¬ integration-sqlite on 3.11
No files were found with the provided path: .coverage.integration-sqlite-3.11. No artifacts will be uploaded.
|
|
π¬ integration-sqlite on 3.10
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f, jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-sqlite on 3.10
No files were found with the provided path: junit-integration-sqlite-3.10.xml. No artifacts will be uploaded.
|
|
π¬ integration-sqlite on 3.10
No files were found with the provided path: .coverage.integration-sqlite-3.10. No artifacts will be uploaded.
|
|
π¬ unit-no-extras on 3.11
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
π¬ unit-no-extras on 3.11
No files were found with the provided path: junit-unit-no-extras-3.11.xml. No artifacts will be uploaded.
|
|
π¬ unit-no-extras on 3.11
No files were found with the provided path: .coverage.unit-no-extras-3.11. No artifacts will be uploaded.
|
|
π¬ integration-mysql on 3.11
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f, jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-mysql on 3.11
No files were found with the provided path: junit-integration-mysql-3.11.xml. No artifacts will be uploaded.
|
|
π¬ integration-mysql on 3.11
No files were found with the provided path: .coverage.integration-mysql-3.11. No artifacts will be uploaded.
|
|
π¬ integration-mysql on 3.12
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f, jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-mysql on 3.12
No files were found with the provided path: junit-integration-mysql-3.12.xml. No artifacts will be uploaded.
|
|
π¬ integration-mysql on 3.12
No files were found with the provided path: .coverage.integration-mysql-3.12. No artifacts will be uploaded.
|
|
π¬ integration-mysql on 3.10
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f, jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-mysql on 3.10
No files were found with the provided path: junit-integration-mysql-3.10.xml. No artifacts will be uploaded.
|
|
π¬ integration-mysql on 3.10
No files were found with the provided path: .coverage.integration-mysql-3.10. No artifacts will be uploaded.
|
|
π¬ integration-sqlite on 3.14
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f, jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-sqlite on 3.14
No files were found with the provided path: junit-integration-sqlite-3.14.xml. No artifacts will be uploaded.
|
|
π¬ integration-sqlite on 3.14
No files were found with the provided path: .coverage.integration-sqlite-3.14. No artifacts will be uploaded.
|
|
π¬ integration-sqlite on 3.12
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f, jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-sqlite on 3.12
No files were found with the provided path: junit-integration-sqlite-3.12.xml. No artifacts will be uploaded.
|
|
π¬ integration-sqlite on 3.12
No files were found with the provided path: .coverage.integration-sqlite-3.12. No artifacts will be uploaded.
|
|
π¬ integration-mysql on 3.13
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f, jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-mysql on 3.13
No files were found with the provided path: junit-integration-mysql-3.13.xml. No artifacts will be uploaded.
|
|
π¬ integration-mysql on 3.13
No files were found with the provided path: .coverage.integration-mysql-3.13. No artifacts will be uploaded.
|
|
π¬ integration-mysql on 3.14
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f, jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-mysql on 3.14
No files were found with the provided path: junit-integration-mysql-3.14.xml. No artifacts will be uploaded.
|
|
π¬ integration-mysql on 3.14
No files were found with the provided path: .coverage.integration-mysql-3.14. No artifacts will be uploaded.
|
|
π¬ integration-postgres on 3.14
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f, jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-postgres on 3.14
No files were found with the provided path: junit-integration-postgres-3.14.xml. No artifacts will be uploaded.
|
|
π¬ integration-postgres on 3.14
No files were found with the provided path: .coverage.integration-postgres-3.14. No artifacts will be uploaded.
|
|
π¬ integration-postgres on 3.13
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f, jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-postgres on 3.13
No files were found with the provided path: junit-integration-postgres-3.13.xml. No artifacts will be uploaded.
|
|
π¬ integration-postgres on 3.13
No files were found with the provided path: .coverage.integration-postgres-3.13. No artifacts will be uploaded.
|
|
π¬ integration-postgres on 3.10
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f, jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-postgres on 3.10
No files were found with the provided path: junit-integration-postgres-3.10.xml. No artifacts will be uploaded.
|
|
π¬ integration-postgres on 3.10
No files were found with the provided path: .coverage.integration-postgres-3.10. No artifacts will be uploaded.
|
|
π¬ integration-postgres on 3.11
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f, jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-postgres on 3.11
No files were found with the provided path: junit-integration-postgres-3.11.xml. No artifacts will be uploaded.
|
|
π¬ integration-postgres on 3.11
No files were found with the provided path: .coverage.integration-postgres-3.11. No artifacts will be uploaded.
|
|
π¬ integration-postgres on 3.12
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f, jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-postgres on 3.12
No files were found with the provided path: junit-integration-postgres-3.12.xml. No artifacts will be uploaded.
|
|
π¬ integration-postgres on 3.12
No files were found with the provided path: .coverage.integration-postgres-3.12. No artifacts will be uploaded.
|