Bump octokit/request-action from 2.4.0 to 3.0.0#1268
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
WalkthroughBumps the Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.github/workflows/publish-components-for-e2e-tests.yml:
- 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.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 0cf91770-8ff4-415d-aca2-b52aa6fb4b43
📒 Files selected for processing (1)
.github/workflows/publish-components-for-e2e-tests.yml
| - 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 |
There was a problem hiding this comment.
🧩 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-nodeand setnode-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 viaFORCE_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.ymlRepository: 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=trueOtherwise 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.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alexeykazakov, dependabot[bot], MatousJobanek The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest |
|
New changes are detected. LGTM label has been removed. |
|
@dependabot rebase hitting rebase because some checks did not trigger
|
|
Looks like this PR has been edited by someone other than Dependabot. That means Dependabot can't rebase it - sorry! If you're happy for Dependabot to recreate it from scratch, overwriting any edits, you can request |
|
@dependabot recreate |
Bumps [octokit/request-action](https://github.com/octokit/request-action) from 2.4.0 to 3.0.0. - [Release notes](https://github.com/octokit/request-action/releases) - [Commits](octokit/request-action@v2.4.0...v3.0.0) --- updated-dependencies: - dependency-name: octokit/request-action dependency-version: 3.0.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
1b553df to
46e3034
Compare
|




Bumps octokit/request-action from 2.4.0 to 3.0.0.
Release notes
Sourced from octokit/request-action's releases.
Commits
b91aabafix(deps): update dependency@octokit/actionto v8, update runner to v24, swi...02f5e7cci(action): update peter-evans/create-or-update-comment action to v5 (#331)f103041ci(action): update github/codeql-action action to v4 (#332)937f551ci(action): update actions/checkout action to v6 (#340)c861151ci(action): update actions/setup-node action to v6 (#333)05a2312build(deps): bump@octokit/requestfrom 9.1.1 to 9.2.2 (#322)22cf731build(deps): bump@octokit/plugin-paginate-restfrom 11.3.0 to 11.4.2 (#319)786351dci(action): update actions/publish-immutable-action action to v0.0.4 (#314)Summary by CodeRabbit