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
- Warnings in the Bug Reporter window are cut off and not truncated when the Bug Reporter window is resized to its minimum size
- Color is incorrectly applied to objects when initialized with non-normalized parameters
- SerializationUtility.GetManagedReferencesWithMissingTypes() don't return null when “Prefab has missing SerializeReference Types“ warning banner is present
- Memory leak when VFX Graph is open and Camera has "Target Texture" enabled
- The Canvas component's warning box is missing an apostrophe when Additional Shader Channels is set to "Normal" and "Tangent" with Render Mode set to "Screen Space - Overlay"
Add comment