We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug CodeQL v1 is getting deprecated This of course affects all of the pull requests here, since those tests will fail.
Since CodeQL is switching to Node.js 16, and this project for some reason still wants to be compatible with older unsupported Node.js projects still, I have no idea, if it is just enough to switch that "v1" into a "v2" inside https://github.com/validatorjs/validator.js/blob/master/.github/workflows/codeql-analysis.yml
Just wanted to bring this to the attention of everybody here.
The text was updated successfully, but these errors were encountered:
CodeQL runs checks that are independent of the Node version/features so yes you can just open a PR to update v1 to v2 to solve this
v1
v2
Sorry, something went wrong.
chore(CodeQL): update deprecated v1 to v2
f1835cd
https://github.blog/changelog/2022-04-27-code-scanning-deprecation-of-codeql-action-v1/ fixes validatorjs#2149
chore(CodeQL): update deprecated v1 to v2 (#2150)
93667bd
https://github.blog/changelog/2022-04-27-code-scanning-deprecation-of-codeql-action-v1/ fixes #2149
Successfully merging a pull request may close this issue.
Describe the bug
CodeQL v1 is getting deprecated
This of course affects all of the pull requests here, since those tests will fail.
Since CodeQL is switching to Node.js 16, and this project for some reason still wants to be compatible with older unsupported Node.js projects still, I have no idea, if it is just enough to switch that "v1" into a "v2" inside https://github.com/validatorjs/validator.js/blob/master/.github/workflows/codeql-analysis.yml
Just wanted to bring this to the attention of everybody here.
The text was updated successfully, but these errors were encountered: