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

Change configstore dependency version to 2.0.0 #73

Merged
merged 1 commit into from
Mar 17, 2016
Merged

Change configstore dependency version to 2.0.0 #73

merged 1 commit into from
Mar 17, 2016

Conversation

nikeee
Copy link
Contributor

@nikeee nikeee commented Mar 16, 2016

This PR addresses issue #72.
According to the release notes of configstore, there has been added support for dot notations. Since update-notifier does not use dots in its config values, this should be fine by just changing the referenced version.

@@ -1,9 +1,10 @@
{
"name": "update-notifier",
"version": "0.6.2",
"version": "0.6.3",
Copy link
Member

Choose a reason for hiding this comment

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

Don't bump versions. Package maintainers will take care of it.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done

@SBoudrias
Copy link
Member

Squash your commits and we'll be good to merge.

hemanth added a commit that referenced this pull request Mar 17, 2016
Change configstore dependency version to 2.0.0
@hemanth hemanth merged commit 6302783 into yeoman:master Mar 17, 2016
@hemanth
Copy link
Member

hemanth commented Mar 17, 2016

On behalf of Simon ;)

@@ -4,6 +4,7 @@
"description": "Update notifications for your CLI app",
"license": "BSD-2-Clause",
"repository": "yeoman/update-notifier",
"bugs": "https://github.com/yeoman/update-notifier/issues",
Copy link
Member

Choose a reason for hiding this comment

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

This should also not have been part of the PR... It's out of scope and not needed as npm infers it from the repo field.

sindresorhus added a commit that referenced this pull request Mar 17, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants