Repository navigation
Auto cherry pick - #32
Conversation
Move the project to Node 24 and pnpm 10 across local tool versions, GitHub workflows, and the packaged action runtime. Update Turbo and the lockfile for the newer package manager metadata. This is a breaking change as the github action now uses Node 24 instead of Node 20.
Replace the split Jest, ESLint, Prettier, esbuild, and Super Linter setup with Vite+ commands and configuration. Move packaging to vp pack with ESM output for the GitHub Action bundle, remove stale root tests, and update CI to run Vite+ checks, tests, and builds.
resolves braintrustdata/eval-action#88 Support Go eval workflows. Example action configuration: ```yaml - name: Run Evals uses: braintrustdata/eval-action@v1 with: api_key: ${{ secrets.BRAINTRUST_API_KEY }} runtime: go root: my_eval_dir paths: . ```
|
📦 Target Release Version: |
🔍 Cherry-Pick Verification Report📦 Upstream Changes: 📋 File-by-File Analysis:
|
🔍 Cherry-Pick Verification Report📦 Upstream Changes: 📋 File-by-File Analysis:
|
🔍 Cherry-Pick Verification Report📦 Upstream Changes: 📋 File-by-File Analysis:
|
|
PR Review complete - see details below |
PR ReviewAction TypeNode-based action - entry at eval/dist/index.js via node24. Passed Checks
Failed Checks
Warnings
Security Findings
SummaryWell-structured cherry-pick adding report_scores, report_metrics, github_token, step_key inputs plus README/checkout updates. Single blocker: duplicate .tool-versions entries. |
|
PR Review Action Type: Node-based (node24 runtime, eval/dist/index.js) PASSED CHECKS:
FAILED CHECKS:
WARNINGS:
SECURITY FINDINGS:
SUMMARY: |
PR ReviewAction TypeNode-based action (runs on Passed Checks
Failed Checks
Warnings
Security Findings
SummaryThe PR cherry-picks upstream improvements (new |
|
Follow-up note: The .tool-versions duplicate entry issue appears to have already been addressed in commit cae5a23 ('fix: remove duplicate entry') pushed after the initial cherry-pick. The examples/go/go.yml issue (duplicate workflow blocks + braintrustdata/eval-action@v1 reference) still requires attention — see the inline comment on that file. |
|
Review Update: Two corrections to the initial review comment above. CORRECTION - .tool-versions: The duplicate-entry issue reported in the initial review is a local merge-commit artifact in this test environment and is NOT part of this PR actual diff. Please disregard that Failed Check. NEW CRITICAL FINDING - examples/go/go.yml: This file has its entire YAML content duplicated (file doubled from 42 to 84 lines). The first 42 lines contain the old upstream workflow using braintrustdata/eval-action@v1 and actions/checkout@v4. The second 42 lines contain the correct step-security workflow using step-security/eval-action@v2 and actions/checkout@v7. This is a cherry-pick merge artifact. The old upstream content (lines 1-42) must be removed before merging - the file has duplicate top-level YAML keys and the braintrustdata action reference must not appear in the step-security fork examples. An inline comment has been added on the diff to mark the affected lines. |
braintrustdata/eval-action@v2.0.0...v2.1.0