Search Issue Tracker
Won't Fix
Votes
0
Found in
6000.3.0b1
Issue ID
UUM-116383
Regression
No
Tooltip message in the "Inspector" window has unclear 'SemVer' abbreviation
Steps to reproduce:
- Create a project
- Window -> Package Management -> Package Manager
- Click “+” and select “Create package”
- Enter the package name and click the “Create”
- Select the newly created package for it to appear in the Inspector window
- Go to the "Inspector" window and hover the mouse above the "Version"
- Observe the tooltip
Actual results: Tooltip "Must follow SemVer (ex:.....)"
Expected results:
Must follow semantic versioning, such as 3.2.1 or 1.0.0-preview.1.
Reproducible with versions: 6000.3.0b1
Not reproducible with versions: -
Can’t test with versions: 6000.0.55f1, 6000.1.15f1, 6000.2.2f1, 6000.3.0a2 as package creation functionality landed just in 6000.3.0a3
Tested on (OS): M1 Max - Sequoia 15.6.1
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
We have confirmed the issue. However, the fix for it will not be prioritized in the near future, so we're closing this ticket. We might reopen this ticket if priorities change.