Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
1
Found in
2019.3.0a7
2019.3.0b7
2020.1.0a1
Issue ID
1191723
Regression
Yes
Package version is not updated when version is changed in package.json file
How to reproduce:
1. Open attached project ("Reproz.zip")
2. Open Package Manager window (Window->Package Manager)
3. Find BUG REPORT package
4. Open package.json in Project window (Packages/BUG REPORT)
5. Change version value
Expected result: Package version is updated
Actual result: Package version is not updated
Reproducible with: 2019.3.0a7, 2019.3.0b7, 2020.1.0a9
Not reproducible with: 2017.4.33f1 (Package Manager was not present), 2018.4.11f1, 2019.2.10f1, 2019.3.0a6
Note: Same behavior is happening when changing version value in Inspector window
Comments (3)
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
- Play Mode framerate drops significantly when moving the mouse cursor with high polling rate
- Create workspace does not update the Unity Version Control and Branch Explorer windows leading to multiple clicks on “Create workspace” which throws an “already exists” error when Creating a workspace with the Branch Explorer window open
- Default and Result encoding properties have blank dropdowns by default when opening the Unity Version Control Settings
- Crash on "StoredGraphicsBuffer::GetGfxBufferID" when activating VFX via extention of Activation Track in Timeline window
- [Linux] Stack trace file path and line number information is missing when IL2CPP Stacktrace Information is set to "Method Name, File Name, and Line Number"
fherbst
Apr 02, 2020 11:58
This is not fixed in 2019.3.7f1.
fherbst
Feb 11, 2020 23:10
This is not fixed in 2019.3.0f6 and is a workflow issue for inhouse package development.
fherbst
Jan 10, 2020 23:35
This is not fixed in 2019.3.0f4.