Skip to content

chore: re-add node 20 CI MCP-518#1227

Draft
nirinchev wants to merge 1 commit into
mainfrom
ni/node-20-ci
Draft

chore: re-add node 20 CI MCP-518#1227
nirinchev wants to merge 1 commit into
mainfrom
ni/node-20-ci

Conversation

@nirinchev

Copy link
Copy Markdown
Collaborator

Proposed changes

Addresses a leftover comment from #1221

Copilot AI review requested due to automatic review settings June 5, 2026 21:07
@nirinchev
nirinchev requested a review from a team as a code owner June 5, 2026 21:07
@nirinchev
nirinchev requested review from cveticm and removed request for a team June 5, 2026 21:07

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

This PR adjusts the GitHub Actions “Code Health” workflows to expand the Node.js version test matrix (notably re-adding Node 20) while keeping macOS/Windows coverage on a single Node version.

Changes:

  • Expand Linux CI to run the MongoDB test job on Node 20, 22, 24, and 26.
  • Keep macOS and Windows CI runs, but limit them to Node 22 via matrix include.
  • Apply the same matrix changes to both the main-repo and fork (dependabot/external PR) workflows.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
.github/workflows/code-health.yml Expands the Node test matrix on Ubuntu and retains macOS/Windows runs on Node 22.
.github/workflows/code-health-fork.yml Mirrors the updated matrix strategy for fork/dependabot PRs.

@nirinchev

Copy link
Copy Markdown
Collaborator Author

This actually doesn't work because pnpm doesn't support node 20. Will try and come up with an alternative solution.

@nirinchev
nirinchev marked this pull request as draft June 8, 2026 10:41
@github-actions

github-actions Bot commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

This PR has gone 30 days without any activity and meets the project's definition of "stale". This will be auto-closed if there is no new activity over the next 30 days. If the issue is still relevant and active, you can simply comment with a "bump" to keep it open, or add the label "not_stale". Thanks for keeping our repository healthy!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants