Search Issue Tracker
Fixed
Fixed in 6000.3.0b1
Votes
0
Found in
6000.3.0a4
Issue ID
UUM-113476
Regression
No
Custom package uses an old Test Framework version by default
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. Select the created package and go to "Dependencies"
5. Observe the "Is Using" field
Expected results: The new package doesn't use any other package
Actual results: The new package uses the "Test Framework" package of the wrong 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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment