title: Updating all Meteor packages to latest versions
body: <p>I'm developing a Meteor app that isn't yet in production, so I can afford to move quickly when adopting new package versions (useraccounts had a significant version bump a few hours after I'd integrated it, for instance.) This was what I thought <code>meteor update</code> was meant to accomplish. Yet when I run:</p>
  
  <p><code>meteor update</code></p>
  
  <p>from my project, I'm told that packages were updated but .meteor/versions remains unchanged.</p>
  
  <p>I can upgrade the package by running <code>meteor add someone:package@whatever</code>, but this just shuffles the version dependency from .meteor/versions to .meteor/packages even though it seems to do the upgrade. I'm happy to lock versions down when I go to production, but it seems like in development I should be able to use the update command, especially as <code>meteor list</code> indicates that as a next step.</p>
  
  <p>I've managed to upgrade all my packages by removing .meteor/versions and .meteor/local and running <code>meteor update</code>, but this seems messy.</p>
  
  <p>I also found <a href="https://github.com/meteor/meteor/issues/3393">this issue</a> but it was closed. Should it be reopened or should I open a new issue? I understand how semver works, but I think the issue is that Meteor isn't writing its constraint solver results to .meteor/versions so doesn't realize that package updates have been applied. Is that accurate or am I just misunderstanding something?</p>