fix!: require Node.js 22.22 and repair CI - #58
Conversation
BREAKING CHANGE: The Python wrapper now requires Node.js 22.22.0 or newer.
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 1ad16d23dd
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3bda89c3cd
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Summary
22.22.0) before delegating through either global npm or npx; document and recommend Node 24 LTS, with tests for missing, broken, older, minimum, and newer runtimes.uv.lock, lint both workflows, and let a dedicated release token start eligiblepull_requestCI automatically. With the default token GitHub requires a maintainer to approve workflow execution; historical manual re-publications preserve their existing lock-repair behavior.The previous
mainand release-please dependency PR runs failed in different Windows smoke jobs; their detailed logs have expired. A manual workflow dispatch on the existing release PR confirmed that GitHub runs against its head but excludes those checks from branch protection, as documented in GitHub's required checks troubleshooting guide. This PR therefore uses the standard pull request workflow instead.Validation
[email protected]smoke suite on macOS: 20 passed through a global installation on Node 24; 20 passed through npx on exactly Node 22.22.0[email protected]updater against the full lockfile and verified only the root package version changesBreaking change: the Python wrapper no longer supports Node 20 or Node 22 releases older than 22.22.0, including when an older promptfoo CLI is pinned.