You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Minor: Ideally we'd use --message-format like Cargo itself does. Otherwise I think it's the right direction - you either need output for humans or machines - usually not both.
The logs output by `cargo libcnb package` have changed over recent
PRs - this updates the example output to match.
There's still some improvements required to the output (eg #600), however,
for now it at least reflects reality.
After #575, the
cargo libcnb package
command now outputs the paths of all compiled buildpacks to stdout (with the rest of the output on stderr).This is intended so that automation can fish out the buildpack names, and is used by eg:
https://github.com/heroku/languages-github-actions
However, it gives a cluttered output for human users of
cargo libcnb package
, eg:(ie: the very final line of the log output)
Perhaps we need a separate
--machine-readable
or some other output format control?The text was updated successfully, but these errors were encountered: