-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Upgrades jasmine, karma-webpack, webdriver-manager, covergae, pygithub & webpack to their latest version #6770
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.
Hi @NishealJ, thanks for the PR. Can you please list the testing methodology for this (and other upgrade PRs)?
package-lock.json
Outdated
"eslint-scope": "^4.0.0", | ||
"eslint-visitor-keys": "^1.0.0" | ||
}, | ||
"dependencies": { | ||
"eslint-scope": { |
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.
Hi @NishealJ, I have a couple of questions here:
- There seem to be deletions in this file. Is this the case or have some dependencies been moved? If the latter, please revert them to their original positions.
- There are multiple versions of eslint-scope listed in this file as dependencies (4.0.3 and 3.7.1). Why? Are there any other such dependencies? Can you please check this?
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.
Hi @apb7,
yes, I'll provide the testing docs for this.
package-lock.json was auto-generated after the upgrade, I believe there are deletions in package-lock.json because, after the upgrade, libraries might have changed their requirements.
Also,
eslint-scope is mentioned twice because package-lock contains all the libraries and their requirements, if 2 or more libraries require eslint-scope it will be mentioned more than 2 time.
I'll completely test this and provide a testing doc thanks!
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.
yes, I'll provide the testing docs for this.
Hmm. I was looking for the manual tests you must have carried out locally when upgrading this.
package-lock.json was auto-generated after the upgrade, I believe there are deletions in package-lock.json because, after the upgrade, libraries might have changed their requirements.
Okay, thanks for the explanation.
eslint-scope is mentioned twice because package-lock contains all the libraries and their requirements, if 2 or more libraries require eslint-scope it will be mentioned more than 2 time.
I agree -- if there are two or more libraries that require eslint-scope, it will be mentioned more than two times. I was more concerned regarding two different versions of eslint-scope...
I'll completely test this and provide a testing doc thanks!
Okay, if this PR is untested, can you please do the following:
- Label this as a WIP and add to the PR explanation whatever is left to do.
- Assign the PR to yourself until it remains a WIP. As soon as you are done with the PR, please re-assign it to me so that I can review it.
Thanks!
Oh, and also, is this PR dependent on or related to PR #6769? I can see some overlapping changes in package-lock.json. Thanks! |
Hi @NishealJ, I'm going to mark this PR as stale because it hasn't had any updates for 10 days. If no further activity occurs within 7 days, it will be automatically closed so that others can take up the issue. |
Hi @lilithxxx, i'm working on the testing doc. |
@NishealJ, since you're upgrading multiple libraries here, please change the PR title accordingly. Thanks! |
Hi @NishealJ, two things -- please make the doc commentable by anyone, and please also make sure the doc contains links to the changelogs for the relevant libraries and calls out + analyzes any breaking changes. Thanks! |
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.
LGTM, thanks @NishealJ. Please check out a fresh copy of package-lock.json (if it isn't already).
Hi @seanlip and @vojtechjelinek, ptal as code owners. Thanks! |
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.
The package-lock.json shouldn't be empty, otherwise LGTM!
Hi @vojtechjelinek Done Thanks! |
Hi @vojtechjelinek & @seanlip PTAL Thanks! |
Hi @vojtechjelinek, ptal. Thanks! |
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.
LGTM!
Explanation
This PR upgrades jasmine, karma-webpack, webdriver-manager & webpack to their latest version.
Visit here to see the upgrade status of all the oppia third-party libraries.
visit here for testing doc
Checklist
python scripts/pre_commit_linter.py
andbash scripts/run_frontend_tests.sh
.