ci: force minimax to run on node24 via env override

[nelson2005]

What

Set job-scoped FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true on the MiniMax Code Review job so the action runs on node24 ahead of GitHub's 2026-06-02 forced switch.

Why

Upstream tarmojussila/minimax-code-review still declares using: "node20" at v0.4.0 (latest). The previous bump from v0.3.0 → v0.4.0 only picked up new features; the runtime warning persists. The FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true env var is GitHub's documented opt-in to run a node20-declared action on node24 now.

Risk + revert

If the action's code uses APIs deprecated/removed in node24, the minimax job will fail. Low probability (most node20 actions run fine on node24), but unverified.

Revert by removing the env: block on minimax_code_review.yml. Drop the override entirely once upstream ships a node24 release.

Notes

• Job-scoped (not workflow-scoped), so blast radius is the single minimax review job.
• Same change to follow in nelson2005/numbox if the trial works here, or vice versa.

[gemini-code-assist]

Note

Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported.

[github-actions]

MiniMax Code Review

The user is asking me to review a pull request that modifies a GitHub Actions workflow file. Let me analyze the change:

The modification adds two lines to the workflow:

env:
  FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: "true"

This sets an environment variable FORCE_JAVASCRIPT_ACTIONS_TO_NODE24 to "true" at the job level.

Let me think about what this could mean:

1. This appears to be forcing JavaScript actions to use Node.js version 24 (which is likely a very recent or upcoming version of Node.js)
2. The naming convention suggests it's related to some kind of compatibility or testing for newer Node.js versions

Now let me provide code review feedback:

What I can observe:

• The change is straightforward - it just adds environment variables
• The variable name is descriptive and suggests its purpose is to force JS actions to use Node 24

Questions I should raise:

1. What is the purpose of this environment variable? It seems like it might be related to the minimax-code-review action's behavior.
2. Is this change necessary? Why does this specific review action need to run on Node 24?
3. Is this a temporary fix or a permanent change? If it's tied to a specific Node.js version that hasn't been released yet, there might be concerns about future compatibility.
4. Are there any security implications of using an unreleased or cutting-edge Node.js version?

Potential concerns:

1. Node.js 24 doesn't exist yet (as of my knowledge cut-off). This seems like a forward-looking change, but it could be unnecessary if Node 24 isn't stable.
2. Using cutting-edge versions can introduce unexpected behavior or security vulnerabilities.
3. The action tarmojussila/minimax-code-review@v0.4.0 - I don't know anything about this specific action.

I should verify the action's legitimacy by checking its source, maintenance status, and potential security implications. Investigating the repository's activity, maintainer reputation, and code review history will help assess its reliability and safety for the project.

Code Review: minimax_code_review.yml Modification

Summary

This PR adds an environment variable to force JavaScript actions to use Node.js 24.

---

Observations

1. Legibility

• ✅ The change is simple and easy to understand
• ⚠️ The variable name is somewhat unclear about its exact purpose

2. Potential Concerns

Concern	Severity	Notes
Node version validity	Medium	Node.js 24 isn't officially released yet (current LTS is v20, v22 in development). This could break if the action doesn't support it.
Action maintenance	Low	The custom action tarmojussila/minimax-code-review@v0.4.0 should be verified for active maintenance.
Intent unclear	Low	No context provided in the commit message or PR description about why this is needed.

---

Questions for the Author

1. Why Node 24? Is this required for a specific feature in the minimax-code-review action, or is this a workaround?

2. Is this temporary? If Node 24 isn't stable yet, should this be added conditionally or reverted later?

3. Any documentation? Could you provide context about what problem this solves?

---

Recommendation

The change looks syntactically correct. However, I'd recommend adding a PR description explaining why this environment variable is needed before merging.

Request for author: Please add more context about the intent of this change.

---

Would you like me to elaborate on any of these points?

[Copilot]

Pull request overview

Sets a job-scoped environment override so the tarmojussila/minimax-code-review@v0.4.0 JavaScript action runs under Node.js 24 ahead of GitHub’s upcoming forced runtime switch, limiting impact to the single MiniMax review job.

Changes:

• Add FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: "true" to the MiniMax Code Review job environment.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.