Search Unity

  1. Megacity Metro Demo now available. Download now.
    Dismiss Notice
  2. Unity support for visionOS is now available. Learn more in our blog post.
    Dismiss Notice

Version in PackageManager seems not to match version in manifest?

Discussion in 'Physics for ECS' started by MNNoxMortem, Oct 26, 2020.

  1. MNNoxMortem

    MNNoxMortem

    Joined:
    Sep 11, 2016
    Posts:
    723
    Is this intended?
    upload_2020-10-26_19-27-26.png
    vs
    upload_2020-10-26_19-27-44.png
     
  2. petarmHavok

    petarmHavok

    Joined:
    Nov 20, 2018
    Posts:
    461
    Which manifest is this?
     
  3. MNNoxMortem

    MNNoxMortem

    Joined:
    Sep 11, 2016
    Posts:
    723
    The manifest.json of my main project. I am not sure what you are asking for. It is the manifest of the project I have added the package manager screenshot from.
     
  4. rz_0lento

    rz_0lento

    Joined:
    Oct 8, 2013
    Posts:
    2,361
    Just to make sure, are you certain you are looking at the same projects manifest?

    Additionally, did you refresh the view on notepad++ so you are not looking at some older cache of that file? I ask because it's not only physics package on your manifest that has a different version.
     
    MNNoxMortem likes this.
  5. MNNoxMortem

    MNNoxMortem

    Joined:
    Sep 11, 2016
    Posts:
    723
    The question is absolutely valid, but what should I say, re-opened it in atom to compare:
    upload_2020-11-1_22-49-30.png
    I thought the manifest is the true source of versions to be loaded? The package-lock shows that the versioning is maybe out of date as unity.physics is loaded via havok dependeny:
    upload_2020-11-1_22-50-37.png
    however, even the root level package looks correct to me:
    upload_2020-11-1_22-51-13.png

    I only created this thread as I would expect that the manifest.json version is in sync, but maybe it does not need to be.
     
    Last edited: Nov 1, 2020
  6. petarmHavok

    petarmHavok

    Joined:
    Nov 20, 2018
    Posts:
    461
    Yeah, sorry, I completely misunderstood what you were saying. It is possible that packages pull in higher dependencies of other packages than stated in the manifest, and that happens exactly like this. I know it's not ideal, thanks for pointing it out!
     
    MNNoxMortem likes this.