Repeating "Forcing update" notification #303

Closed
AvnerCohen opened this Issue Sep 6, 2012 · 4 comments

Comments

Projects
None yet
4 participants

I have updated Yeoman to latest code, npm install -g and npm link and all seems to be working fine.
However, whenever running the command line "yeoman whatever", I'm getting the following output:

› yeoman server
Starting update check...
Update available: 0.1.13 (current: 0.3.15)
Forcing update because it's been too long since last
Updating grunt

npm http GET https://nodeload.github.com/cowboy/grunt/tarball/0ba6d4b529
npm http 200 https://nodeload.github.com/cowboy/grunt/tarball/0ba6d4b529
npm WARN excluding symbolic link test/fixtures/octocat-link.png -> octocat.png

Updated successfully!

Despite the success notification, as I ran Yeoman again, I see the same version state and same output.

Owner

addyosmani commented Sep 6, 2012

@sindresorhus I can't reproduce. Can you? If so, maybe we should disable the update check until its possible to check for actual yeoman updates.

Member

paulirish commented Sep 6, 2012

I'm less enthused about shipping without the updater in order.

Owner

addyosmani commented Sep 6, 2012

@paulirish I agree. I think the issue is that we're still checking against the latest version of grunt rather than yeoman latest because we're not public yet. This is one of the pre-launch tasks that need to be done. Actually, I'll create an issue as a reminder.

Owner

sindresorhus commented Sep 6, 2012

As explained in the Updater PR, this is intended so that we could test it before it was actually on NPM.

@szinya szinya pushed a commit to menthainternet/yeoman that referenced this issue Sep 17, 2014

@sindresorhus sindresorhus Updater: Some final fixes. Fixes #303 #304
Added a `--skip-updater` flag in case we need it.
84fa684

@sindresorhus sindresorhus added a commit that referenced this issue Apr 24, 2015

@sindresorhus sindresorhus Updater: Some final fixes. Fixes #303 #304
Added a `--skip-updater` flag in case we need it.
0b972e4
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment