New meaning for -o argument of force:source:deploy breaks existing usages of original meaning

[SCWells72]

I've been hearing about failures during IC2 deployment using force:source:deploy of late, and one user tracked it down to a new meaning for the existing -o argument:

FLAGS
  -o, --ignoreerrors                                                                                                 Ignore any errors and don't roll back deployment.
  -o, --target-org=<value>                                                                                           (required) Username or alias of the target org.

The first is the original meaning and the second is new, but now when IC2 invokes that command as it always has, it fails with:

{
  "code": 1.0,
  "message": "Parsing --target-org \n\tNo authorization information found for -g.\nSee more help with --help",
  "name": "NamedOrgNotFoundError",
  "status": 1.0,
  "stack": "NamedOrgNotFoundError: Parsing --target-org \n\tNo authorization information found for -g....",
  "exitCode": 1.0,
  "warnings": [
    "We plan to deprecate this command in the future. Try using the \"project deploy start\" command instead."
  ]
}

I can change IC2 to use the long form --ignoreerrors, but this is another example of a breaking change to what should be a 100% reliable, stable API with, at most, a planned and scheduled deprecation lifecycle.

[github-actions]

Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.

[git2gus]

This issue has been linked to a new work item: W-13056553

[WillieRuemmele]

Hey @SCWells72 - sorry for breaking this - we've fixed it in latest-rc which will be promoted to latest tomorrow morning, hopefully this wasn't too much of a pain for you