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

Question Upgrading packages between users

Discussion in 'Unity Version Control' started by sstrong, Jul 10, 2022.

  1. sstrong

    sstrong

    Joined:
    Oct 16, 2013
    Posts:
    2,229
    What is the best practice for upgrading packages in shared Plastic SCM project?

    Recently, we had the manifest file shared (as was previously suggested) and upgraded the Version Control package on one PC from 1.14.12 to 1.14.18 and committed changes (which included the changes to the manifest file).

    On another PC, when the project was updated it "seemed" to work fine until the Unity editor (2019.4.32) was restarted. Then Plastic raised some errors. After a couple of editor restarts, no more errors.

    How does Plastic SCM Unity plug-in handle package upgraded between PCs?
     
  2. ollieblanks

    ollieblanks

    Unity Technologies

    Joined:
    Aug 21, 2017
    Posts:
    459
    The version of the package is handled via updates to the manifest file, the same workflow as any other package. Interesting this would cause the behaviour you mention, I have been unable to reproduce this.

    If you can, please update your Editor version, so you can use version 1.15.x (or 1.17.x) of the package.

    Hope this helps.
     
  3. sstrong

    sstrong

    Joined:
    Oct 16, 2013
    Posts:
    2,229
    We're on 2019.4 LTS at the moment for some projects but maybe later in the year we'll consider it.