Skip to content
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

bump linter to node 16 #64

Merged
merged 1 commit into from
Apr 9, 2024
Merged

bump linter to node 16 #64

merged 1 commit into from
Apr 9, 2024

Conversation

tomap
Copy link
Contributor

@tomap tomap commented Apr 8, 2024

check list

  • Add test cases for the changes.
  • Passed the CI test.

Description

Additional information

@coveralls
Copy link

Coverage Status

coverage: 100.0%. remained the same
when pulling d298a27 on tomap-patch-1
into d9e4cf7 on master.

Copy link
Member

@uiolee uiolee left a comment

Choose a reason for hiding this comment

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

In my opinion there is no need to specify the node version for the linter as it doesn't require exact node version, and we can avoid updating this number. There is a default version of node in the ci environment. BTW running actions/setup-node takes a few seconds longer.

I plan to delete actions/setup-node in the job linter in the future

@tomap tomap merged commit 2fe2ef0 into master Apr 9, 2024
24 checks passed
@tomap tomap deleted the tomap-patch-1 branch April 9, 2024 08:56
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.

3 participants