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):
- CLI: 6.7.8
- Cross-platform modules: 6.5.2
- Android Runtime: -
- iOS Runtime: -
- Plugin(s): -
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
Environment
Provide version numbers for the following components (information can be retrieved by running
tns infoin your project folder or by inspecting thepackage.jsonof 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