feat: enforce Node.js 24 for all runners and workflows

[GrammaTonic]

• Adds FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true to all runner Docker Compose files and environment examples
• Sets FORCE_JAVASCRIPT_ACTIONS_TO_NODE24 at the workflow level in ci-cd.yml
• Ensures all JavaScript actions use Node.js 24 across standard, Chrome, and Chrome-Go runners
• Updates documentation and configuration for Node.js 24 enforcement

Closes #performance, #devops, #nodejs, #ci-cd

/cc @copilot

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request aims to enforce the use of Node.js 24 for all JavaScript actions within the CI/CD pipelines and local runner environments. By standardizing the Node.js version, the change ensures greater consistency, improves compatibility, and allows for leveraging the latest features and performance enhancements offered by Node.js 24 across all runner types.

Highlights

• Node.js 24 Enforcement: Standardized the Node.js version to 24 for all JavaScript actions across various runners (standard, Chrome, Chrome-Go) by introducing the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24 environment variable.
• Configuration Updates: Updated Docker Compose files and environment examples to include the new Node.js 24 enforcement variable, ensuring consistent application of the specified Node.js version.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• config/chrome-go-runner.env.example
  • Added FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true to enforce Node.js 24 for JavaScript actions.
• config/chrome-runner.env.example
  • Added FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true to enforce Node.js 24 for JavaScript actions.
• config/runner.env.example
  • Added FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true to enforce Node.js 24 for JavaScript actions.
• docker/docker-compose.chrome-go.yml
  • Added FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true to the environment variables for the runner service.
• docker/docker-compose.chrome.yml
  • Added FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true to the environment variables for the runner service.
• docker/docker-compose.production.yml
  • Added FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true to the environment variables for the runner service.

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/ci-cd.yml

Activity

• No human activity has been recorded on this pull request yet.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request consistently enforces the use of Node.js 24 across all runner configurations by adding the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true setting. The changes are applied to the example environment files and the Docker Compose configurations for all runner types. My review focuses on improving the consistency of how this new environment variable is handled in the Docker Compose files to allow for optional overrides, aligning with its inclusion in the example files.

[gemini-code-assist]

To maintain consistency with how other variables are handled in this file, it's recommended to allow this value to be overridden from the environment. This aligns with the addition of FORCE_JAVASCRIPT_ACTIONS_TO_NODE24 to the .env.example files and provides flexibility for users who might need to disable this feature.

      - FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=${FORCE_JAVASCRIPT_ACTIONS_TO_NODE24:-true}

[gemini-code-assist]

For consistency with other environment variables in this compose file, it would be better to allow this setting to be configured via an environment variable. This change would make the configuration more flexible and consistent with the presence of FORCE_JAVASCRIPT_ACTIONS_TO_NODE24 in the example environment files.

      - FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=${FORCE_JAVASCRIPT_ACTIONS_TO_NODE24:-true}

[gemini-code-assist]

To ensure consistency across configurations and provide flexibility, this hardcoded value should be replaced with a reference to an environment variable with a default. This aligns with the practice used for other variables in this file and the fact that FORCE_JAVASCRIPT_ACTIONS_TO_NODE24 is now part of the example environment files.

      - FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=${FORCE_JAVASCRIPT_ACTIONS_TO_NODE24:-true}