I just noticed sometimes when I run
meteor update, I get this message:
- New versions of these packages are available! Run ‘meteor update’ to try to update those packages to their latest versions. If your packages cannot be updated further, try typing
meteor add <package>@<newVersion>to see more information.
But some packages will automatically update when
meteor update is run. Why are packages being held back from updating?
And as a package author, how do you set a stopping point where a user has to manually use
meteor add <package>@<version> to update?