Skip to content

Bump actions/checkout to v5 to fix Node.js 20 deprecation - #33

Merged
omindu merged 1 commit into
wso2:mainfrom
ranuka-laksika:fix-node20-checkout-deprecation
Jul 22, 2026
Merged

Bump actions/checkout to v5 to fix Node.js 20 deprecation#33
omindu merged 1 commit into
wso2:mainfrom
ranuka-laksika:fix-node20-checkout-deprecation

Conversation

@ranuka-laksika

@ranuka-laksika ranuka-laksika commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

Summary

GitHub on Actions runners. actions/checkout@v4 bundles Node.js 20 and was being force-run on Node.js 24, producing a deprecation warning in the analyze-dependencies job.

This bumps actions/checkout@v4@v5, which targets Node.js 24 natively, removing the warning.

Ref:- deprecated the Node.js 20 runtime

Changes

  • .github/workflows/dependency_analysis.ymlanalyze-dependencies job checkout step
  • .github/workflows/registry-pr-validator.yaml — both checkout steps (yaml-lint and schema-validation jobs)

GitHub deprecated the Node.js 20 runtime on Actions runners, and
actions/checkout@v4 was being force-run on Node.js 24. Bump to
actions/checkout@v5, which targets Node.js 24 natively.
@coderabbitai

coderabbitai Bot commented Jul 22, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@ranuka-laksika, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 43 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: ff528e2a-db53-4f39-b685-1378d088832f

📥 Commits

Reviewing files that changed from the base of the PR and between f3bdc6d and 7fbb0d6.

📒 Files selected for processing (2)
  • .github/workflows/dependency_analysis.yml
  • .github/workflows/registry-pr-validator.yaml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@ranuka-laksika ranuka-laksika changed the title ci: bump actions/checkout to v5 to fix Node.js 20 deprecation Bump actions/checkout to v5 to fix Node.js 20 deprecation Jul 22, 2026
@omindu
omindu merged commit 3b1bcb1 into wso2:main Jul 22, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants