@corgea/cli 1.11.0 → 1.12.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (7) hide show
  1. package/README.md +2 -3
  2. package/package.json +1 -1
  3. package/vendor/aarch64-apple-darwin/corgea/corgea +0 -0
  4. package/vendor/aarch64-unknown-linux-musl/corgea/corgea +0 -0
  5. package/vendor/x86_64-apple-darwin/corgea/corgea +0 -0
  6. package/vendor/x86_64-pc-windows-msvc/corgea/corgea.exe +0 -0
  7. package/vendor/x86_64-unknown-linux-musl/corgea/corgea +0 -0
package/README.md CHANGED
@@ -73,9 +73,8 @@ Only a scan that answers the same question is reused, which is stricter than
73
73
  branch rather than a pull request, from an explicitly clean worktree, with no
74
74
  scanner problems reported — and this run has to be a default whole-commit scan
75
75
  itself. Anything else runs a real scan: nothing inside the window, only a failed
76
- or still-running scan, a worktree that does not match the commit (including
77
- files the index hides from `git status`), or a lookup the platform could not
78
- answer.
76
+ or still-running scan, a worktree `git status` reports changes in, or a lookup
77
+ the platform could not answer.
79
78
 
80
79
  Two things are hard errors instead. An unresolvable commit (not a git
81
80
  repository, or no commits yet) exits 1 rather than silently scanning. And a run
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@corgea/cli",
3
- "version": "1.11.0",
3
+ "version": "1.12.0",
4
4
  "description": "The Corgea CLI. Scan for vulnerabilities, create fixes.",
5
5
  "license": "LGPL-2.1-only",
6
6
  "homepage": "https://corgea.com",