Environment
Provide version numbers for the following components (information can be retrieved by running tns info in your project folder or by inspecting the package.json of the project):
Describe the bug
Not sure if it is a bug or the desired behavior, but I think when upgrading @nativescript/core via tns plugin add @nativescript/core@latest, do dependency should point to a @next release that might be unstable.
Right now this happens:

To Reproduce
See description
Expected behavior
Upgrading a component to @latest should upgrade its dependencies to @latest as well, not to @next.
Sample project
-
Additional context
-
Hey @felixkrautschuk - thanks for the heads up, we are looking into why this was done this way - and we'll be fixing the versions in an upcoming release!
seems to be fixed with the recent release:

@madmas @rigor789 I can confirm that this does not occur anymore updating to the latest @nativescript/core version.
Thanks