Merge branch 'master' into clean-up-fossa-scan-action

Changelog.md

@@ -1,4 +1,6 @@
 # FOSSA CLI Changelog
+## 3.9.40
+- Licensing: Fix a bug where license scanner output sometimes included log lines, which breaks JSON parsing
 
 ## 3.9.39
 - Licensing: Add the PSF-3.12.7 license. Make a correction to the MulanPSL license. Add a new public-domain rule ([#1480](https://github.com/fossas/fossa-cli/pull/1480))

docs/references/subcommands/sbom.md

@@ -30,7 +30,7 @@ In addition to the [usual FOSSA project flags](#common-fossa-project-flags) supp
 
 The `sbom test` command checks whether the most-recent scan of your FOSSA project raised license-policy or vulnerability issues. This command is usually run immediately after `fossa sbom analyze`.
 
-- If there are issues, it prints them to stdout and fails with an exit code of 1
+- If there are issues, it prints them to stderr and fails with an exit code of 1
 - If there are no issues, it prints nothing and succeeds with an exit code of 0
 
 `fossa sbom test` supports the [Common FOSSA Project Flags](./analyze.md#common-fossa-project-flags).

docs/references/subcommands/test.md

@@ -3,7 +3,7 @@
 
 The test command checks whether the most-recent scan of your FOSSA project raised license-policy or vulnerability issues. This command is usually run immediately after `fossa analyze`
 
-- If there are issues, it prints them to stdout and fails with an exit code of 1
+- If there are issues, it prints them to stderr and fails with an exit code of 1
 - If there are no issues, it prints nothing and succeeds with an exit code of 0
 
 `fossa test` supports the [Common FOSSA Project Flags](./analyze.md#common-fossa-project-flags) supported by all commands
@@ -54,4 +54,4 @@ For instance,
 
 
 * If the revision `v2.0.0` has issue: `A`, and the revision `34021e` has issues `A`, `B`, 
-  * `fossa-cli` reports issue `B` and exits with status code of 1.
+  * `fossa-cli` reports issue `B` and exits with status code of 1.