cargo-action-fmt can "swallow" error return codes

[jamesmunns]

Hi there! In tosc-rs/mnemos#226 (comment) we realized that piping to cargo-action-fmt seemed to swallow the error code output of cargo check, without failing the build in some other way.

Normally this should be fixed with set -o pipefail, but we are also using just.

This is extra weird because in this case cargo produces NO output:

james@Jamess-MacBook-Pro ➜  mnemos git:(eliza/forced-x86-target) cargo check --lib --bins --examples --tests --benches --all-features --package mnemos-x86_64-bootloader --message-format=json
error: no library targets found in package `mnemos-x86_64-bootloader`

This may not be reasonable for you to fix, but thought I would share just in case!

[JP-Ellis]

This can be easily fixed by setting the pipefail option:

run: |
  set -o pipefail
  cargo check --message-format=json | cargo-action-fmt

Admittedly, a better fix would be to have cargo-action-fmt return a non-zero exit code if it prints out any errors.

@olix0r, would you be open for a PR to implement this? I'd be happy to contribute.

[olix0r]

Thanks! This seems like an easy fix. I obviously haven't been very hands-on with this repo, but if there's a fix coming through I'll can try to dust off the dependabot cobwebs and get a new release together.