Search Unity

  1. Good news ✨ We have more Unite Now videos available for you to watch on-demand! Come check them out and ask our experts any questions!
    Dismiss Notice
  2. Ever participated in one our Game Jams? Want pointers on your project? Our Evangelists will be available on Friday to give feedback. Come share your games with us!
    Dismiss Notice

Semantic versioning like 1.0.x is not working

Discussion in 'Package Manager' started by arielsan, Mar 24, 2019.

  1. arielsan

    arielsan

    Joined:
    Dec 3, 2013
    Posts:
    29
    Hi, I was testing semantic versioning (semver calculator) to depend on latest patch of a specific version but can't make it work. I supposed it was supported by reading the forums and even by the error code:

    Code (txt):
    1. An error occurred while resolving packages:
    2.   Project has invalid dependencies:
    3.     com.unity.collab-proxy: Version '1.2.x' is invalid. Expected one of: a 'SemVer' compatible value; a value starting with 'file:'; a Git URL starting with 'git:' or 'git+', or ending with '.git'.
    4.  
    Am I doing it wrong? is it not supported yet?

    Thanks!
     
    Last edited: Mar 25, 2019
  2. JakHussain

    JakHussain

    Joined:
    Oct 20, 2016
    Posts:
    279
    I'm pretty sure all 3 digits need to be numbers. You can also add "-preview" at the end of the version number for the preview tag to appear in the package manager UI.
     
  3. okcompute_unity

    okcompute_unity

    Unity Technologies

    Joined:
    Jan 16, 2017
    Posts:
    723
    Hi @arielsan ,

    Semantic Versioning (SemVer) is at the core of the Unity Package Manager. But, what you are trying to set is called version range. It refers to SemVer versions. Two related but different concepts. Version range is not supported for the moment by Unity Package Manager. This is in our long term plan though. Note that we plan to implement a Nuget (or Scientific) notation. This is different than npm implementation.

    Hope it helps,

    Pascal
     
    mandisaw and JakHussain like this.
  4. arielsan

    arielsan

    Joined:
    Dec 3, 2013
    Posts:
    29
    Yes, it helps, and clarifies the concepts :), sorry I was messing them up.

    We'll have to wait until version range is supported then :(

    Thanks!
     
  5. JKort

    JKort

    Joined:
    Sep 14, 2017
    Posts:
    1
    Any update on this? Also wondering why to opt for the nuget implementation when everything else seems to be based on npm packages. Personally think the npm ranges are easier to read as well :)
     
  6. mandisaw

    mandisaw

    Joined:
    Jan 4, 2018
    Posts:
    37
    Just a guess, but probably because .NET/Visual Studio already understands NuGet.
     
  7. Florian-Nouviale

    Florian-Nouviale

    Joined:
    Mar 14, 2013
    Posts:
    29
    Hi, any news on this ? It's difficult for us to maintain CI generated dependencies automatically without version range
     
unityunity