Search Issue Tracker
Active
Under Consideration for 6000.3.X
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
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI Toolkit meshes are fully rendered and rasterized when opacity is 0
- Light rendering artefacts appear in the Editor when assigning unsupported 3D Custom Render Texture in Camera’s Output Texture, unclearable errors and warnings spammed
- Memory leak when running a test with "GfxThreadingMode" set to "SplitJobs"
- Loading Unloaded unsaved Scene throws “ArgumentException” error in the Console
- Crash on std::__1::__tree_const_iterator when opening the Build Profiles window in a specific project
Add comment