You'll notice
No documentation found
Plugin command.run no longer rejects overly long arguments, only logs their length
What
The check that runs before a plugin's command.run operation executes used to reject the call with an error if its arguments exceeded a maximum length. That rejection has been removed: the check now only records the argument length for telemetry (internal usage tracking) and always allows the call to proceed.
Why
Plugin commands with very long arguments that would previously have been blocked can now run instead, since the length limit is no longer enforced, only measured.
Names in the bundlecommand.run