Skip to content

eval: include structured results, run config, and summary in JSON output #4967

eval: include structured results, run config, and summary in JSON output

eval: include structured results, run config, and summary in JSON output #4967

Triggered via pull request April 2, 2026 13:51
Status Failure
Total duration 4m 7s
Artifacts

ci.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 1 warning
lint
issues found
lint: pkg/evaluation/save_test.go#L279
float-compare: use assert.InEpsilon (or InDelta) (testifylint)
lint: pkg/evaluation/save_test.go#L260
float-compare: use assert.InEpsilon (or InDelta) (testifylint)
lint: pkg/evaluation/save_test.go#L259
float-compare: use assert.InEpsilon (or InDelta) (testifylint)
lint: pkg/session/session.go#L237
File is not properly formatted (gci)
lint: pkg/evaluation/types.go#L29
File is not properly formatted (gci)
lint: pkg/evaluation/eval_test.go#L661
File is not properly formatted (gci)
build-and-test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: jdx/mise-action@c37c93293d6b742fc901e1406b8f764f6fb19dac. 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/