Search Issue Tracker
Fixed
Fixed in 6000.3.0b5, 6000.4.0a2
Votes
0
Found in
6000.3.0a6
Issue ID
UUM-116023
Regression
No
Validation message in package creation contains 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 “Create”
- Select the newly created package for it to appear in the Inspector window
- Close the "Package Manager" window
- Click the “Edit” button in the “Inspector” window
- Find the "Dependencies" section and click "" under it
- Remove by default displayed values from both fields
- Add "123" to both fields
- Save changes and observe the result in the Package Manager window
Actual results: A user gets an error "Package has invalid dependencies: 123: Version '123' is invalid. Expected a 'SemVer'compatible value."
Expected results:
"Package has invalid dependencies: 123: Version '123' is invalid. Expected a value that follows semantic versioning rules."
Reproducible with versions: 6000.3.0a6
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
SemVer is a common term in software development.