-
-
Notifications
You must be signed in to change notification settings - Fork 31
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
refactor: Lint project and remove deprecated code #43
Conversation
Thanks for opening this pull request! |
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #43 +/- ##
==========================================
+ Coverage 90.83% 93.44% +2.60%
==========================================
Files 1 1
Lines 131 122 -9
==========================================
- Hits 119 114 -5
+ Misses 12 8 -4 ☔ View full report in Codecov by Sentry. |
@mtrezza @dblythy Can either revert semantic-release as suggested in #45 or merge this PR which currently uses the previous version of semantic-release to pass the CI In the repo settings you should add protections for the following passing tests:
Remove the following as they are replaced by the aforementioned tests:
|
Could you please resolve any conflicts; and keep the semantic release version of the main branch, it should work with #46. |
My reason for opening for #45 is because it results in the following when trying to install on a local machine: npm WARN old lockfile
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @parse/[email protected]
npm WARN Found: [email protected]
npm WARN node_modules/semantic-release
npm WARN peer semantic-release@">=16.0.0 <18.0.0" from @semantic-release/[email protected]
npm WARN 6 more (@semantic-release/changelog, @semantic-release/npm, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer semantic-release@">=16.0.0 <18.0.0" from @semantic-release/[email protected]
npm WARN node_modules/@semantic-release/commit-analyzer
npm WARN @semantic-release/commit-analyzer@"^8.0.0" from [email protected]
npm WARN node_modules/semantic-release
npm WARN 1 more (the root project)
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @parse/[email protected]
npm WARN Found: [email protected]
npm WARN node_modules/semantic-release
npm WARN peer semantic-release@">=16.0.0 <18.0.0" from @semantic-release/[email protected]
npm WARN 6 more (@semantic-release/changelog, @semantic-release/npm, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer semantic-release@">=15.8.0 <18.0.0" from @semantic-release/[email protected]
npm WARN node_modules/@semantic-release/changelog
npm WARN dev @semantic-release/changelog@"5.0.1" from the root project
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @parse/[email protected]
npm WARN Found: [email protected]
npm WARN node_modules/semantic-release
npm WARN peer semantic-release@">=16.0.0 <18.0.0" from @semantic-release/[email protected]
npm WARN 6 more (@semantic-release/changelog, @semantic-release/npm, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer semantic-release@">=16.0.0 <18.0.0" from @semantic-release/[email protected]
npm WARN node_modules/@semantic-release/npm
npm WARN @semantic-release/npm@"^7.0.0" from [email protected]
npm WARN 1 more (the root project)
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @parse/[email protected]
npm WARN Found: [email protected]
npm WARN node_modules/semantic-release
npm WARN peer semantic-release@">=16.0.0 <18.0.0" from @semantic-release/[email protected]
npm WARN 6 more (@semantic-release/changelog, @semantic-release/npm, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer semantic-release@">=16.0.0 <18.0.0" from @semantic-release/[email protected]
npm WARN node_modules/@semantic-release/git
npm WARN dev @semantic-release/git@"9.0.0" from the root project
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @parse/[email protected]
npm WARN Found: [email protected]
npm WARN node_modules/semantic-release
npm WARN peer semantic-release@">=16.0.0 <18.0.0" from @semantic-release/[email protected]
npm WARN 6 more (@semantic-release/changelog, @semantic-release/npm, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer semantic-release@">=16.0.0 <18.0.0" from @semantic-release/[email protected]
npm WARN node_modules/@semantic-release/github
npm WARN @semantic-release/github@"^7.0.0" from [email protected]
npm WARN 1 more (the root project)
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @parse/[email protected]
npm WARN Found: [email protected]
npm WARN node_modules/semantic-release
npm WARN peer semantic-release@">=16.0.0 <18.0.0" from @semantic-release/[email protected]
npm WARN 6 more (@semantic-release/changelog, @semantic-release/npm, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer semantic-release@">=15.8.0 <18.0.0" from @semantic-release/[email protected]
npm WARN node_modules/@semantic-release/release-notes-generator
npm WARN @semantic-release/release-notes-generator@"^9.0.0" from [email protected]
npm WARN 1 more (the root project)
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: @parse/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/semantic-release
npm ERR! dev semantic-release@"21.0.1" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer semantic-release@">=16.0.0 <18.0.0" from @semantic-release/[email protected]
npm ERR! node_modules/@semantic-release/commit-analyzer
npm ERR! dev @semantic-release/commit-analyzer@"8.0.1" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution. If you know of a better way without force installing, let me know, but the errors seem to point to wanting newer versions than what's in the package.json and package-lock |
What Node and npm version are you running? I tried with Node 16 and 18 and it worked fine. It really just needs to run in our CI, and that's it. This release framework is our internal tool. Check here: |
I'm running |
The main branch works it seems, so why are you trying to install the dependency explicitly? If you use the main branch and then run npm i it should work I guess. |
It appears to me that dependabot allowed an incorrect update in #41 and somehow forced an update to the package-lock. The warnings and errors in #43 (comment) look explicit and state a number of problems like #41 updated from In addition, the parse-server receives way more updates than this repo and it's versions aren't this high: https://github.com/parse-community/parse-server/blob/9674d4a2c0a9d0cda112056a6a2b1629931f37a3/package.json#L75-L107 |
This PR requires babel/lint to be installed, installing using |
Ready for review... In the repo settings you should add protections for the following passing tests:
Remove the following as they are replaced by the aforementioned tests:
|
🎉 This change has been released in version 3.0.0 |
Pull Request
Issue
The project isn't linted
Closes: #44
Approach
Add babel dev dependenciesUpdate CI to test for successful lintsubstr
withsubstring
rotateEncryptionKey()
to use async/await instead of promiseTasks