Broken JSON output for force:package:version:create

[aly76]

Summary

sfdx force:package:version:create --json is leaking log statements to the console, in JSON mode.

Steps To Reproduce:

1. Create package version with --json flag

Expected result

Only the JSON output should be printed to the console.

Actual result

❯ sfdx force:package:version:create -p mypackage -w 120 --definitionfile config/project-scratch-def.json --json -x --skipvalidation -v devhub
Dependency on package A was resolved to version number 1.0.4.2, branch null, 04t.
Dependency on package B was resolved to version number 1.0.2.2, branch null, 04t.
Dependency on package B was resolved to version number 1.0.4.2, branch null, 04t.
{
"status": 0,
"result": {
"Id": "08c4",
"Status": "Success",
"Package2Id": "0Ho4",
"Package2VersionId": "05i",
"SubscriberPackageVersionId": "04t",
"Tag": null,
"Branch": null,
"Error": [],
"CreatedDate": "2021-05-05 16:24",
"HasMetadataRemoved": false
}
}

Additional information

Feel free to attach a screenshot.

SFDX CLI Version(to find the version of the CLI engine run sfdx --version):
7.99.0

SFDX plugin Version(to find the version of the CLI plugin run sfdx plugins --core)
51.10.0

OS and version:
macOS 10.15.7

[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.

[uip-robot-zz]

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

[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.

[gsbasso]

Once again a CLI update has broken our CI process. What is the ETA for a fix (or at least an option to suppress the additional verbiage)? We need to assess whether we need to spend time devising a workaround on our own. Thanks.

[azlam-abdulsalam]

@gsbasso We use a docker image to counter this and test through all commands before an update

[fl43]

Things like this should not happen. It looks like there are no proper unit tests in place.

[shetzel]

The fix is in the release candidate from last week Thursday. It will be promoted tomorrow. Apologies for the regression!

[github-actions]

We have determined that the issue you reported exists in code owned by another team that uses only the official support channels. To ensure that your issue is addressed, open an official Salesforce customer support ticket with a link to this issue. We encourage anyone experiencing this issue to do the same to increase the priority. We will keep this issue open for the community to collaborate on.

[mshanemc]

fixed in latest release