Feedback Add an option to auto update packages.

Hi @Circadence_DanW,

We have something in our plan to fulfill your use case. The UX might not be the same you propose though.

This feature is available withouta proper UI in 2019.3 beta release. You'll need to manually update the project manifest to change the Package Manager resolution strategy.

First, you need enable the lock file. The lock file is, for the moment, an opt-in feature. To enable the lock file, add the enableLockFile property with the value to your project manifest.

Code (csharp):

1.  
2. {
3.   "dependencies": {},
4.   "enableLockFile": true
5. }
6.  

Once this is done, a new packages-lock.json will get created alongside manifest.json as soon as you give focus back to Unity.

Ideally, this file should:

• Be source controlled: this is in order to ensure reproducibility over time and across machines;
• Not be modified manually: because this file is generated by the Package Manager, it could be rewritten according to its internal rules and your changes, discarded. In the worst case, a bad manual edit could lead the file to be completely rewritten, for instance if there is a JSON syntax error. (In that case, VCS is your friend: see the above point.)

The new lock file supersedes the lock property of the project manifest, which was used to track Git dependencies. If you intend to keep the lock file feature enabled, you can manually remove the lock property from the project manifest.

Next, you need to change the resolution strategy.

The resolutionStrategy configuration allows UPM to upgrade transitive dependencies based on well-known Semantic Versioning rules. The following values are supported:

• highestPatch - In this mode, the SemVer expression "~" is applied to the requested version (e.g: ~1.0.0).
• highestMinor - In this mode, the SemVer expression "^" is applied to the requested version (e.g: ^1.0.0).
• highest - In this mode, the SemVer expression ">=" is applied to the requested version (e.g: >=1.0.0).

Note that these SemVer expressions will never allow a dependency to jump from a stable to a pre-release (AKA preview) version of a package.

In you case, you would set:

Code (csharp):

1.  
2. {
3.   "dependencies": {},
4.   "enableLockFile": true,
5.   "resolutionStrategy": "highest"
6. }
7.  

Once a package has been resolved, it will remained locked at that version as long as it satisfies the SemVer expression of the strategy.

The lock file needs to be deleted in order to force a refresh of transitive dependency versions. Any modification to the project manifest or to a writable package (ie: local or embedded) can potentially result in a locked version to be recalculated. As I said, at some point we will have something in the UI to remove the lock.

Let us know if this would fulfill your requirement (albeit the missing UI).

Regards,

Pascal

 

It looks like the project you are opening in your CI run is older than the Unity version opening the project. This triggers the project update flow which updates packages to their minimum requirement and adds some default packages. A solution would be to update the project, prior to opening in the CI, to the same Unity version used in the CI.

Hope this helps,

Pascal

 

HI @fschmeidl, I'm sorry, it turns out we haven't received a lot of requests to expose this feature in the UI in the end. If this feature is important to you, you can make your voice heard by clicking the *Submit a new idea!* tile in the Package Management product roadmap page.

Regards,

Pascal