-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Closed
Labels
p4-importantViolate documented behavior or significantly improves performance (priority)Violate documented behavior or significantly improves performance (priority)
Description
Describe the bug
After upgrading from v2.0.5 to 2.1.0 I now get the All projects should have unique names error, for every package.
The problem goes away if I downgrade back to 2.0.5
This seems like a regression maybe?
Reproduction
Unknown, I am unable to repro outside of our environment. Downgrading versions resolves.
System Info
System:
OS: Linux 5.15 Ubuntu 20.04.6 LTS (Focal Fossa)
CPU: (16) x64 11th Gen Intel(R) Core(TM) i7-11850H @ 2.50GHz
Memory: 8.41 GB / 11.68 GB
Container: Yes
Shell: 5.0.17 - /bin/bash
Binaries:
Node: 20.12.2 - ~/.nvm/versions/node/v20.12.2/bin/node
npm: 10.7.0 - ~/.nvm/versions/node/v20.12.2/bin/npm
pnpm: 9.0.6 - ~/.nvm/versions/node/v20.12.2/bin/pnpm
npmPackages:
vitest: 2.0.5 => 2.0.5
### Used Package Manager
pnpm
### Validations
- [X] Follow our [Code of Conduct](https://github.com/vitest-dev/vitest/blob/main/CODE_OF_CONDUCT.md)
- [X] Read the [Contributing Guidelines](https://github.com/vitest-dev/vitest/blob/main/CONTRIBUTING.md).
- [X] Read the [docs](https://vitest.dev/guide/).
- [X] Check that there isn't [already an issue](https://github.com/vitest-dev/vitest/issues) that reports the same bug to avoid creating a duplicate.
- [X] Check that this is a concrete bug. For Q&A open a [GitHub Discussion](https://github.com/vitest-dev/vitest/discussions) or join our [Discord Chat Server](https://chat.vitest.dev).
- [X] The provided reproduction is a [minimal reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) of the bug.
Metadata
Metadata
Assignees
Labels
p4-importantViolate documented behavior or significantly improves performance (priority)Violate documented behavior or significantly improves performance (priority)