v5.5.0-beta5

v5.5.0-beta5

v5.5.0-beta4

v5.5.0-beta4

v5.5.0-beta3

v5.5.0-beta3

v5.5.0-beta2

v5.5.0-beta2

v5.5.0-beta1

v5.5.0-beta1

v5.4.0

Added

• New AsyncAPI 2 ruleset and format #965
• Custom functions can be async #694
• Expose fetch and cache to custom functions #1078, #1079

Changed

• Drop example-value-or-externalValue rule and introduce oas3-examples-value-or-externalValue #883, #1098
• Drop useless oas rule tags #1095
• AJV: swallow missing references #1147
• Improve ruleset validation #1144
• Allow running spectral from any directory in Docker #1022

Fixed

• Improve oas2-schema and oas3-schema rules #403
• path-params rule now properly detects undefined parameters across operations #1076
• Load custom functions from NPM correctly #1093
• Teach path-params to report an actual endpoint path #1130

v5.4.0-beta1

AsyncAPI Ruleset Support 🥳

v5.3.0

Added

• Built-in functions can now be accessed from custom functions #925
• CLI: --show-unmatched-globs flag #747

Changed

• typed-enum function is no longer a built-in function. It's been migrated into a custom function of the OpenAPI ruleset #924
• openapi-tags rule has been fixed to make it fit its description #1038

Fixed

• Ruleset exceptions used to slip certain errors through cracks #1018
• Correct misleading info-license message #1031
• Requiring packages located under node_modules is possible #1029
• Set proper document source if legacy parsed result is given #1040

v5.2.0

Added

• Rule exceptions are supported #747
• Allow require calls in Node.JS #1011

Changed

• YAMLIncomaptibleValue diagnostics are now considered warnings #1009

Fixed

• Alphabetical rule works correctly for $refs #979

v5.1.0

Features

• Implement a new typed-enum rule to detect enum value that do not respect specified type #913

Added

• API: introduced document #876 - note, this is not a breaking change
• Introduce optional enhancers to casing function #884

Fixed

• Improved Example Object validation #882
• oas3-operation-security-defined rule supports optional authentication #895
• Generate more correct paths when reporting an error #900
• example-value-or-externalValue no longer reports false positives #899
• schema-path accepts a JSON Path expression as a field selector #917
• schema-path handles invalid values gracefully #917
• oas3-valid-(content-)schema-example rules handle nullable correctly #914