[Feature request/Discussion] Behaviour of CURRENTVERSION placeholder in template file.

I have a solution with two projects A and B.
Both projects produce nuget packages and B has a nuget dependency of project A.

I want to set dependency with range ["A current version", "A next major version")

I can use ~> CURRENTVERSION placeholder in template file for B but there are two problems with it.

1. CURRENTVERSION only works when version explicitly set in pack command arguments (with --specific-version for A or with just --version <...>).
   Maybe paket can use same version as for package itself (from assemblyVersion attribute or template file for project A)?
2. I can't achieve next-major-version) right border although it seems a good choice from semver perspective.
   E.g. If A version is 3.2.1 with ~> CURRENTVERSION i get [3.2.1, 3.3.0) range.
   Maybe paket needs another placeholder for exactly that case?

I can explicitly set version range in template file for B but in that case i must not forget to update it every time i change A version. It's annoying :)

Start with the CURRENTVERSION behavior described for Paket template files and the pack command, comparing explicit --specific-version or --version inputs with versions from project A's assemblyVersion attribute or template. Clarify the desired next-major semver range behavior and define how the dependency range should be generated before identifying the relevant implementation and tests.