Skip to content

Run CI on node 18, 20, and 22#1480

Merged
Andarist merged 4 commits intonextfrom
setup-ci-node
Nov 12, 2024
Merged

Run CI on node 18, 20, and 22#1480
Andarist merged 4 commits intonextfrom
setup-ci-node

Conversation

@bluwy
Copy link
Copy Markdown
Member

@bluwy bluwy commented Oct 5, 2024

This is the same thing as #1465 but for the next branch. Maybe we should do this only for the next branch for now.

@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Oct 5, 2024

⚠️ No Changeset found

Latest commit: a800181

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@codecov
Copy link
Copy Markdown

codecov Bot commented Oct 5, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Please upload report for BASE (next@ac917ca). Learn more about missing BASE report.

Additional details and impacted files
@@           Coverage Diff           @@
##             next    #1480   +/-   ##
=======================================
  Coverage        ?   80.82%           
=======================================
  Files           ?       53           
  Lines           ?     2216           
  Branches        ?      656           
=======================================
  Hits            ?     1791           
  Misses          ?      421           
  Partials        ?        4           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@Andarist
Copy link
Copy Markdown
Member

Andarist commented Oct 5, 2024

Maybe we should do this only for the next branch for now.

I'm fine with that 👍

node-version:
description: "Node.js version"
required: false
default: 20
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

out of curiosity, why 20 and not 22? ;p

Copy link
Copy Markdown
Member Author

@bluwy bluwy Oct 5, 2024

Choose a reason for hiding this comment

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

The initial action sets 20 so I reused that. And in practice/experience, 22 is still prone to accidental breaking changes from node itself, so sticking with 20 feels safer.

Comment thread .github/workflows/ci.yml Outdated
jobs:
test:
name: Test
name: "Test: node-${{ matrix.node_version }}"
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

q: what would be the auto-generated titles without this change?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

I don't quite remember, but searching around and landing at https://stackoverflow.com/questions/69105449/github-actions-job-name-based-on-matrix-index-instead-of-matrix-value. I assume it could look like Test (18)

Comment thread .github/workflows/ci.yml Outdated
Co-authored-by: Mateusz Burzyński <mateuszburzynski@gmail.com>
Comment thread .github/workflows/ci.yml Outdated
@Andarist Andarist merged commit 08fef8a into next Nov 12, 2024
@Andarist Andarist deleted the setup-ci-node branch November 12, 2024 08:47
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