@quobix/vacuum 0.30.6 → 0.32.0

package/README.md

@@ -15,7 +15,7 @@
 
 An **ultra-super-fast**, lightweight OpenAPI, AsyncAPI and JSON Schema linter and quality checking tool inspired by [Spectral](https://github.com/stoplightio/spectral).
 
-It's **fully compatible** with existing [Spectral](https://github.com/stoplightio/spectral) rulesets.
+It supports Spectral-style YAML and JSON rulesets. See [Spectral migration](#spectral-migration) for compatibility limits and built-in alternatives.
 
 ## Install using the official [homebrew](https://brew.sh) tap
 
@@ -226,6 +226,28 @@ target exactly what we want to change. vacuum now supports a new `apply-overlay`
 
 - [Learn more about the apply-overlay command](https://quobix.com/vacuum/commands/apply-overlay)
 
+`apply-overlay` can also build a fail-closed publication document after applying
+the standard Overlay actions:
+
+```bash
+vacuum apply-overlay internal.yaml public.overlay.yaml public.yaml \
+  --include-tag public \
+  --tag-match any \
+  --prune-unused
+```
+
+Inclusive tags are exact and case-sensitive; `any` keeps operations with at
+least one included tag and `all` requires every included tag. Untagged
+operations are removed. Filtering runs after Overlay actions and before
+reachability-based component pruning. These opt-in transforms require a
+bundled, self-contained OpenAPI document. Top-level Tag Objects are retained.
+YAML aliases and merge keys are expanded when filtering. Retained mapping
+order, comments, and scalar styles are preserved. Pruning rejects schema
+`$id` scopes that cannot be resolved safely. Link Objects targeting filtered
+operations are retained and reported as warnings. Document output remains
+pure on stdout; warnings are written to stderr. The warning summary uses the `apply-overlay produced` prefix to
+cover both Overlay actions and publication transforms.
+
 ---
 
 
@@ -352,7 +374,7 @@ You can use either **YAML** or **JSON**, vacuum supports both formats.
 
 ## Using vacuum with pre-commit
 
-Vacuum can be used with [pre-commit](https://pre-commit.com).
+vacuum can be used with [pre-commit](https://pre-commit.com).
 
 To do that, add to your `.pre-commit-config.yaml`:
 
@@ -445,7 +467,7 @@ The report file name is _optional_. The default report output name is `vacuum-sp
 
 ## Generate a `vacuum report`
 
-Vacuum reports are complete snapshots in time of a linting report for a specification. These reports can be 'replayed' 
+vacuum reports are complete snapshots in time of a linting report for a specification. These reports can be 'replayed'
 back through vacuum. Use the `dashboard` or the `html-report` commands to 'replay' the report and explore the results
 as they were when the report was generated.
 
@@ -501,6 +523,37 @@ if you're interested in seeing how things are progressing, it's available.
 ```
 
 ---
+## Spectral migration
+
+vacuum loads YAML and JSON rulesets. Resolve each relative `extends` path from the
+file that contains it, including on Windows. Keep sibling rulesets relative:
+
+```yaml
+extends:
+  - ./ruleset.bank.yml
+  - ./ruleset.nlgov.yml
+  - [vacuum:owasp, all]
+```
+
+Use `[vacuum:owasp, all]` for vacuum's built-in OWASP checks instead of importing
+`@stoplight/spectral-owasp-ruleset/dist/ruleset.mjs`. The native rules use vacuum's
+rule names and behavior; they do not execute the Spectral package. JavaScript
+ruleset modules (`.js`, `.mjs`, `.cjs`) are not supported.
+
+Arazzo workflow linting and `spectral:arazzo` are not supported. Remove that entry
+from rulesets used to lint OpenAPI documents. Use an Arazzo-capable linter for
+Arazzo workflow documents.
+
+`--functions` takes a directory containing custom function files:
+
+```shell
+vacuum lint api.yaml --ruleset rules/main.yaml --functions ./functions
+```
+
+It does not enable JavaScript ruleset modules. Omitting the directory reports an
+input error and exits with code 2. In the editor, vacuum checks recognized ruleset
+buffers against its ruleset schema instead of reporting an unsupported API type.
+
 ## Supply your own Spectral compatible ruleset
 
 If you're already using Spectral and you have your own [custom ruleset](https://meta.stoplight.io/docs/spectral/e5b9616d6d50c-custom-rulesets#custom-rulesets),
@@ -592,9 +645,14 @@ lint:
 
 ### Environment variables
 
-You can configure global vacuum flags using environment variables in the form of: `VACUUM_<flag>`
+You can configure global and command-local flags with `VACUUM_<FLAG>`
+environment variables. Use uppercase flag names and replace `-` with `_`.
+Explicit command-line flags take precedence over environment variables;
+environment variables take precedence over configuration files.
 
-If a flag, has a `-` in it, replace with `_`
+Collection flags accept comma-separated values. For example,
+`VACUUM_INCLUDE_TAG='public,partner'` sets the included tags for
+`apply-overlay`.
 
 
 ## Auto-fixing rule violations

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@quobix/vacuum",
-  "version": "0.30.6",
+  "version": "0.32.0",
   "description": "The world's fastest, most scalable and complete OpenAPI parser",
   "type": "module",
   "author": "Dave Shanley",