Plugin names with @, colons, whitespace, path separators or invisible characters are now rejected.
What's wrong with this entry?
A plugin manifest is now rejected with a validation error if its name is empty or contains @, :, whitespace, a path separator, or an invisible or control character. Naming a plugin after its own directory produces a specific hint.
- A manifest version containing unprintable characters is treated as if absent, with a warning rather than a hard failure.
must be non-empty and must not contain "@", ":", whitespace, path separators, or invisible/control characters
Strings lifted out of the shipped bundle, so the claim above can be checked against them.