Releases: daveshanley/vacuum
v0.14.2
v0.14.1
v0.14.0
v0.13.6
Changelog
- b2d44dc - Renamed RuleSetExecution.SpecFileNam to SpecFilePath because it's actually set to the path, not just the filename - Include references from the root as well as the rolodex when checking unused components
- a389635 Added GetAllReferences() and GetAllMappedReferences() methods to Rolodex
- 298f7f3 Undo renaming of public field
v0.13.5
v0.13.2
Updates dependencies across the board and includes the following contributions:
Changelog
- 18d8d7c Addressed issue #549
- 3555616 Fix --config flag description to reference correct default
- 518aede Fix Spectral severity SeverityInfo
- b07da40 cmd: do not print success with silent enabled
- 9061344 feat: watching changed on configuration file
- 0ab6060 fix: xdg home default + use supplied param in
- 5f31f49 fixed docker build and issue #548
- 5872428 upgraded deps
v0.13.1
v0.13.0
Adds support for the doctor to all core functions. Adds little value to vacuum, but turbo charges our downstream product.
Also cleaned up the SPDX checking by adding new rules. Bumped go to v1.23.0 and bumped a number of deps.
Changelog
- 8810de6 Added doctor support to all core functions.
- 07fed9f Added updated SPDX license rule.
- 1b21f9d Revert "added a nill check on examples"
- 215d7fa added a nill check on examples
- 41bcd26 bumped deps
- 4291712 bumped deps and upgraded to latest go 1.23
- c45295d cleaned up and added spdx rule.
- 53c3c5c cleaned up license rule
- c5a66ec fixed tests.
- 087e35b re-bumped deps
- deeb636 update go version.
v0.12.1
v0.12.0
Before v0.12
All core functions returned the same path
provided in the rule. This is because there was no way to determine the actual path due to limitations in some core dependencies.
This is explained here: #269 and was recently revived here: #527
After v0.12
All core functions now return the correct JSON path for all results. This is now possible because of two supporting library upgrades
that we control has facilitated this possibility, without depending on any upstream libs we don't control.
For example, the following ruleset:
rules:
description-is-coffee:
description: "check that every description is 'coffee'"
given: $..description
severity: warn
then:
function: pattern
functionOptions:
match: "^coffee$"
every-response-has-schema:
description: "check that every media type for 200 response has a made up field called peanuts"
given: $.paths.*.*.responses.200.content.*
severity: error
then:
field: peanuts
function: truthy
When run with the model/test_files/burgershop.openapi.yaml
sample spec, results in output like this:
vacuum lint model/test_files/burgershop.openapi.yaml -r ruleset.yaml -d -m
However, now in v0.12+
the same command (and using the new --no-clip
command) shows the actual path.
vacuum lint model/test_files/burgershop.openapi.yaml -r ruleset.yaml -d -m --no-clip