JSON output for `lerna publish`

Expected Behavior

When I run lerna publish, I would like to get a machine-readable output alongside the regular logging.

Current Behavior

There is no JSON output.

Possible Solution

lerna publish --summary-file lerna-publish.json

This would write the following to lerna-publish.json:

{
  "published": [
    { "name": "@scope/module-a", "version": "1.2.3", "tag": "latest" },
    { "name": "@scope/module-b", "version": "1.1.1", "tag": "latest" }
  ]
}

Context

The use case for this file is to kick off deployments in CI pipelines that depend on the packages that were just published.

Here is the horrible bash script that I want to kill! 🔥

lerna publish | tee lerna-output.log

# Extract published packages from the output log
published_packages=$(grep -A 1000 'Successfully published' lerna-output.log \
  | grep -e '^ - @[a-z]\+/' \
  | sed 's/^ - //' \
  | sed 's/@\([0-9].*\)$/ \1/'
)

while read -r module_name version; do
  echo "Do something with ${module_name}@${version}."
done <<< "${published_packages}"

[azz]

Closing this as I’m happy enough with reading git tags. Feel free to re-open if you think there’s wider value.

[creatyvtype]

+1 to this. Also for CI and updating comments in PRs, trying to get a result of publishing beta versions right now requires ugly code to reduce the output of lerna publish into something meaningful.