Search Issue Tracker
Fixed
Fixed in 6000.3.0b7, 6000.4.0a3
Votes
0
Found in
6000.3.0a4
6000.4.0a1
Issue ID
UUM-113483
Regression
No
"Release" field of "Minimum Unity version" on a custom package can be left empty
How to reproduce:
1. Create a new Unity project
2. Open the Package Manager (Window -> Package Management -> Package Manager)
3. Click the "+" button -> Create packageĀ
4. Go to Manage -> Edit Manifest
5. In the Inspector, go to the "Minimum Unity version" section -> "Release" field
6. Delete everything and click Apply
Expected results: The applied changes leave that field empty and remove it from the manifest as well
Actual results: Release can be left empty and Package Manager defaults to the "0a1" version
Reproducible with: 6000.3.0a4
Can't test with: 6000.0.55f1, 6000.1.15f1, 6000.2.0f1 (no such functionality)
Reproducible on: Windows 11 Pro
Not reproducible on: No other environment tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Uninitialized variable warning appears in the Inspector of a custom shader when the variable is initialized
- "Failed creating toolbar element from ID..." error is thrown when resetting the Scene view Overlay layout while an Asset Transformer Toolbox overlay is active
- Entity ID for Font Assets is serialized twice which throws an error when using Debug Inspector
- Play Mode can be entered when disabling Adaptive Performance and pressing either the Play Mode button or the keyboard shortcut to enter Play Mode before recompilation leading to errors and warnings thrown
- Parent ListView element also becomes selected when inner ListView element is selected
Add comment