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

chore(deps): upgrade dependencies #267

Merged
merged 1 commit into from
Apr 14, 2020
Merged

Conversation

devaradhanm
Copy link
Contributor

@devaradhanm devaradhanm commented Apr 14, 2020

Description of changes

upgrading dependencies to update minimist resolutions to use 1.2.5 (upgrading npm from 6.13.6 to 6.14.4 fixes this issue, but i just upgraded all packages instead.)

1.2.0 version was used under node_modules/npm/node_modules/rc/node_modules/minimist/package.json

& 0.0.8 under /home/vsts/work/1/s/node_modules/npm/node_modules/minimist/package.json

Pull request checklist

  • PR title respects Conventional Commits (starts with fix:, feat:, etc, and is suitable for user-facing release notes)
  • PR contains no breaking changes, OR description of both PR and final merge commit starts with BREAKING CHANGE:
  • (if applicable) Addresses issue: #0000
  • Added relevant unit tests for your changes
  • Ran yarn precheckin
  • Verified code coverage for the changes made

upgrading dependencies to update minimist resolutions to use 1.2.5
@devaradhanm devaradhanm requested a review from a team as a code owner April 14, 2020 16:37
@devaradhanm devaradhanm changed the title fix: upgrade dependencies chore(deps): upgrade dependencies Apr 14, 2020
@devaradhanm devaradhanm added the dependencies Pull requests that update a dependency file label Apr 14, 2020
@@ -2,144 +2,152 @@
# yarn lockfile v1


"@babel/code-frame@^7.0.0", "@babel/code-frame@^7.5.5", "@babel/code-frame@^7.8.3":
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did you manually update yarn.lock to cover this? I thought that with yarn, the preferred pattern was to update package.json with a resolutions property to enable yarn to handle this itself; was that not an option here?

Copy link
Contributor Author

@devaradhanm devaradhanm Apr 14, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I did not manually update yarn. I just deleted yarn.lock & did yarn install again to update all packages. That fixed the issue. Alternatively i could have also added resolution in package.json on npm to fix this issue. But, chose this option since we anyway try to be up to date with dependabot.

Copy link
Contributor

@dbjorge dbjorge left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Question inline

@devaradhanm devaradhanm merged commit be9a03e into master Apr 14, 2020
@devaradhanm devaradhanm deleted the demuruge/update-packages branch April 14, 2020 20:22
@ada-cat
Copy link
Collaborator

ada-cat commented Apr 14, 2020

🎉 This PR is included in version 2.3.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file released
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants