Skip to content

fix: ensure we parse recipes with config files #10043

fix: ensure we parse recipes with config files

fix: ensure we parse recipes with config files #10043

Triggered via pull request March 21, 2026 20:24
@beckermrbeckermr
synchronize #5845
parse-cfg
Status Failure
Total duration 14m 15s
Artifacts 6

tests.yml

on: pull_request
Check if we can skip the merge queue
20s
Check if we can skip the merge queue
Matrix: tests / tests-mongodb
Matrix: tests / tests
tests  /  test-coverage-and-durations
0s
tests / test-coverage-and-durations
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 3 warnings
tests / tests (2)
Process completed with exit code 1.
tests / status
Process completed with exit code 1.
tests / tests-mongodb (1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: mamba-org/setup-micromamba@add3a49764cedee8ee24e82dfde87f5bc2914462. 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/
tests / tests (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@10e90e3645eae34f1e60eeb005ba3a3d33f178e8, docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f, mamba-org/setup-micromamba@add3a49764cedee8ee24e82dfde87f5bc2914462. 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/
tests / tests (1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@10e90e3645eae34f1e60eeb005ba3a3d33f178e8, docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f, mamba-org/setup-micromamba@add3a49764cedee8ee24e82dfde87f5bc2914462. 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/

Artifacts

Produced during runtime
Name Size Digest
coverage-1
16.9 KB
sha256:456daac3a8b2c3f65db3c9205614139ef88e0e6dc331642b4a8417ce1b3d256f
coverage-mongodb
13.9 KB
sha256:68f6aba696448499a8573ca19bd5b3de79277985404092aa5b79352f4a9a0ecf
regro~cf-scripts~0PHSNT.dockerbuild
49.9 KB
sha256:431234f70f1f1eae5bab8e44577870ef2c7f0d6ffbb6ea760c0dc023d32a8d19
regro~cf-scripts~A1N31J.dockerbuild
49.4 KB
sha256:650318560e4e074e3c23e166d1ea2d4b0f39b833f2c61db6e632ea001497ca28
test-durations-1
18.2 KB
sha256:789bf6172c12fec4925c244bd658127aeb6d1ad377642791a3055a0ff853318b
test-durations-mongodb
391 Bytes
sha256:71071e28953c9df93b084df95203d12ded3a75fed1dddcac5bdbd1c2249ca22d