Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/workflows/publish-components-for-e2e-tests.yml
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ jobs:
# If the workflow was triggered based on comment, then we need to get the information about the PR
- name: Send Github API Request to get PR data
id: request
uses: octokit/request-action@v2.4.0
uses: octokit/request-action@v3.0.0
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🌐 Web query:

Does GitHub Actions ubuntu-24.04 runner support Node 24?

💡 Result:

Yes—with two important distinctions:

  • Running your workflow code on Node.js 24: Use actions/setup-node and set node-version: 24 (supported). [1]
  • JavaScript-based GitHub Actions runtime (the Node version used to run actions like actions/checkout): The GitHub Actions runner supports Node24 (runner v2.328.0+). You can opt in today via FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true, and GitHub plans to make Node24 the default starting June 2, 2026. [2]
  • What’s preinstalled on ubuntu-24.04: The image currently lists Node.js 20.20.1 as the installed system Node. [3]

Sources: [1] [2] [3]


🏁 Script executed:

cat .github/workflows/publish-components-for-e2e-tests.yml

Repository: codeready-toolchain/toolchain-e2e

Length of output: 3764


Set FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable.

The octokit/request-action@v3.0.0 requires Node 24, but ubuntu-24.04 has Node 20 preinstalled. GitHub Actions will make Node 24 the default for JavaScript actions on June 2, 2026, but until then you must explicitly opt in by adding the environment variable to the job or step. Add:

env:
  FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true

Otherwise the action will fail when triggered via issue comment event.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In @.github/workflows/publish-components-for-e2e-tests.yml at line 38, Add the
environment variable forcing Node 24 for JavaScript actions so the
octokit/request-action@v3.0.0 step runs correctly: update the GitHub Actions job
or the specific step that uses octokit/request-action@v3.0.0 to include env:
FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true; target the step referencing
octokit/request-action@v3.0.0 (or the surrounding job) and add that env key so
the action runs under Node 24 instead of the runner's default Node 20.

if: ${{ github.event_name == 'issue_comment' }}
with:
route: ${{ github.event.issue.pull_request.url }}
Expand Down
Loading