-
Notifications
You must be signed in to change notification settings - Fork 349
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
backport checks changes to v2 branch #2048
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this works. Though, is there a benefit to running the checks on a different node version on v2? I was imagining that when the matrix value is not current
, then the job can just trivially end in success. If there's a reason to run on both versions, then let's do it.
NODE_TYPES_VERSION: ${{ matrix.node-types-version }} | ||
run: | | ||
# Export `NODE_TYPES_VERSION` so it's available to jq | ||
export NODE_TYPES_VERSION="${NODE_TYPES_VERSION}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't know this was necessary.
Pretty sure this works the same:
export NODE_TYPES_VERSION="${NODE_TYPES_VERSION}" | |
export NODE_TYPES_VERSION |
steps: | ||
- name: Checkout | ||
uses: actions/checkout@v4 | ||
|
||
- name: Lint | ||
run: npm run-script lint | ||
|
||
- name: Update version of @types/node | ||
if: matrix.node-types-version != 'current' | ||
env: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
env: | |
shell: bash | |
env: |
In order to keep alignment of check names across all the maintained branches, we backport the matrix job to the
releases/v2
branch.The check runs on node 16 and skips for the current version (node 20).
Merge / deployment checklist