Search Issue Tracker
By Design
Votes
1
Found in
2019.4
2020.2
2020.2.1f1
2021.1
2021.2
Issue ID
1307408
Regression
No
Dependency package version is not updated in the manifest.json file when upgrading the main package
For example, there's a package A (1.0.0) that depends on packages B (1.0.0), C (1.0.0). If package A is updated to version 2.0.0 that depends on B and C versions 2.0.0, packages B and C would still be listed as having version 1.0.0 in the "manifest.json" file.
How to reproduce:
1. Create a new project (using the default 3D template)
2. Import an older version of a Package that has dependencies (i.e., Entities)
3. Update one of the dependencies or add it to the manifest.json file (so it would be listed, i.e., Jobs)
4. Inspect the versions listed in the "manifest.json" file and the Package Manager
5. Update the main Package
6. Inspect the updated dependency version in the Package Manager
7. Compare it to the "manifest.json" file version
Expected result: Dependency's version listed in the Package Manager and the manifest.json is the same
Actual result: manifest.json has the older version of the package even though it's updated in the Package Manager
Reproducible with: 2019.4.20f1, 2020.2.5f1, 2021.1.0b7, 2021.2.0a6
Couldn't test with: 2018.4.32f1 (Dependent packages don't change the version in the Package Manager nor in the manifest.json and package dependencies are not listed)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UXML elements visually stretch when dragging an element along other elements in the UI Builder Hierarchy
- Material does not update when setting an enum keyword using EnableKeyword
- AddComponentMenu.componentOrder has no effect on the "Add Component" menu in the Inspector window
- Distant objects become visibly illuminated when looking through the volumetric fog with SSGI enabled
- WebGL build crashes when opening a ZipArchive entry and "Code Optimization" is not set to the default "Shorter Build Time"
Resolution Note:
This is the behaviour by design. The dependency resolution algorithm takes care of selecting the right package version without overwriting the project manifest. User keeps control over project manifest.