-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Running yarn install
before running the update checkoer
#11011
Running yarn install
before running the update checkoer
#11011
Conversation
@@ -101,12 +101,21 @@ def npm_files | |||
fetched_npm_files | |||
end | |||
|
|||
def run_yarn_install | |||
Dir.chdir("repo") do | |||
# --refresh-lockfile Refresh the package metadata stored in the lockfile |
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.
Any reason why we are not using the Helper.Subprocess method?
Also, can we add tests?
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.
Based on the analysis, yarn immutable install
is only creating .yarn/cache
directory on the repo directory. So I have updated fix and test accordingly.
With this, I ran the cli and ensured, Customer reported issue is fixed
f6cb157
to
bf310e6
Compare
TODO: Junit needs to be added. |
What are you trying to accomplish?
Rel : https://github.com/github/dependabot-updates/issues/7169
Root cause of above issue is
yarn add/upgrade <package-name>@version
is failingCreating a cache folder under .yarn file fixes this issue.
Anything you want to highlight for special attention from reviewers?
I have ran the cli against the repo where I recreated the error and solved it by this update.
How will you know you've accomplished your goal?
I have ran the cli against the repo where I recreated the error and solved it by this update.
Checklist