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

lint: chang eslint-plugin version to ~5.12.1 #3737

Closed
wants to merge 3 commits into from

Conversation

xtx1130
Copy link
Contributor

@xtx1130 xtx1130 commented Mar 2, 2022

lint: change version for eslint-plugin until typescript-eslint/typescript-eslint#4620 be merged and publish new version
test: change 3000 to random port, prevent local test failed due to port address already in use

Checklist

@xtx1130
Copy link
Contributor Author

xtx1130 commented Mar 2, 2022

I think the github ci doesn't use "@typescript-eslint/eslint-plugin": "~5.12.1" for checking😒. I don't think there is any need to change the eslint-plugin version anymore. What's your opinions? @fastify/core

@climba03003
Copy link
Member

climba03003 commented Mar 2, 2022

I think it is more related to the typescript version instead of @typescript-eslint/eslint-plugin
As semver x.y is the major version of TypeScript, I think we should just lock it to ~4.5.x

I see the problematic PR.

@mcollina
Copy link
Member

mcollina commented Mar 2, 2022

I think the github ci doesn't use "@typescript-eslint/eslint-plugin": "~5.12.1" for checking😒. I don't think there is any need to change the eslint-plugin version anymore. What's your opinions? @fastify/core

I don't understand what problematic PR you are referring to.

@climba03003
Copy link
Member

I think the github ci doesn't use "@typescript-eslint/eslint-plugin": "~5.12.1" for checking😒. I don't think there is any need to change the eslint-plugin version anymore. What's your opinions? @fastify/core

I don't understand what problematic PR you are referring to.

The lint error introduced in PR 4541 which comes with version 5.13.0 for @typescript-eslint/eslint-plugin.

@xtx1130
Copy link
Contributor Author

xtx1130 commented Mar 2, 2022

All PRs for fastify's lint check is failing, and I have found it is a bug comes from @typescript-eslint/eslint-plugin at version 5.13.0, I want to use 5.12.1 for default. But github ci linter also failed. So I think gitlab ci doesn't use 5.12.1 for lint and change the version for @typescript-eslint/eslint-plugin is useless.

@Eomm Eomm added test Issue or pr related to our testing infrastructure. typescript TypeScript related labels Mar 2, 2022
@mcollina
Copy link
Member

mcollina commented Mar 2, 2022

@xtx1130 can you split the change-of-port to the package.json edit?

@xtx1130
Copy link
Contributor Author

xtx1130 commented Mar 3, 2022

@xtx1130 can you split the change-of-port to the package.json edit?

ok, I will start another pr mainly for port

@github-actions github-actions bot removed test Issue or pr related to our testing infrastructure. typescript TypeScript related labels Mar 3, 2022
@xtx1130 xtx1130 changed the title lint,test: chang eslint-plugin version to ~5.12.1 & make test case's port random lint: chang eslint-plugin version to ~5.12.1 Mar 3, 2022
@xtx1130 xtx1130 mentioned this pull request Mar 3, 2022
4 tasks
package.json Outdated Show resolved Hide resolved
@mcollina
Copy link
Member

mcollina commented Mar 3, 2022

I have a better fix on the way ;)

Co-authored-by: Manuel Spigolon <behemoth89@gmail.com>
@xtx1130
Copy link
Contributor Author

xtx1130 commented Mar 3, 2022

be closed because of #3741 has merged

@xtx1130 xtx1130 closed this Mar 3, 2022
@github-actions
Copy link

github-actions bot commented Mar 4, 2023

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 4, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants