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

v5.0.0

Features

• Alphabetical rule function now supports numeric keys #730
• Non-JSON-ish YAML mapping keys are reported #726
• CLI: new formatter - text #822
• CLI: new formatter - teamcity #823
• CLI: new formatter - HTML #389
• CLI: custom resolver can be provided leveraging --resolver flag #717
• CLI: input can be provided via STDIN #757
• Implement ignoreUnsupportedFormats to make it easier to detect unrecognized formats #678
• Rule's Given can be an array now #799
• Casing built-in function is added #564
• New oas rule - operation-tag-defined #704

Changed

• BREAKING: The oas2 and oas3 rulesets have been merged into a single oas ruleset #773
• BREAKING: Deprecated Spectral#addRules and Spectral#addFunctions have been removed #561
• BREAKING: Some oas rules, such as example-value-or-externalValue and openapi-tags, are now included in the recommended rulset #725 #706
• BREAKING: The model-description and operation-summary-formatted rules have been removed #725
• BREAKING: The when rule property has been removed #585
• BREAKING: Rules are set to recommended by default #719
• Improved error source detection #685
• Error paths point at unresolved document #839
• Validation messages contain more consistent error paths #867
• CLI: Default --fail-severity is now error, so getting a warn, info or a hint will not return a exit status code #706
• Rulesets no longer require a rules property #652

Fixed

• Circular remote references with JSON pointers are resolved correctly json-ref-resolver#141
• Local root JSON pointers are resolved correctly json-ref-resolver#146
• Invalid JSON pointers are reported as errors now json-ref-resolver#140 and json-ref-resolver#147
• Unixify glob patterns under Windows #679
• Improved duplicate keys detection #751
• Spectral should be usable in browsers with no crypto module available #846
• Falsy values are printed in validation messages #824
• Validation results are no longer duplicate #680, #737 and #856

v5.0.0-beta4

v5.0.0-beta4

v5.0.0-beta3

v5.0.0-beta3

v5.0.0-beta2

v5.0.0-beta2

v5.0.0-beta1

v5.0.0-beta1

v4.2.0

Features

• CLI: glob patterns and multiple paths are allowed #534
• CLI: control fail severity and result display #368
• CLI: new formatter - JUnit #478
• CLI: add possibility to proxy requests #446
• Built-in ruleset formats targeting JSON Schema files #571
• {{value}} and {{path}} can be used in messages #520 #572

Deprecated

• when Rule property is deprecated #585

Changed

• Validation results produced by alphabetical function are more meaningful #613
• Enhanced JSON Schema enum validation #579
• Improved messages generated by oasPathParam function #537
• CLI: the amount of enabled rules is now displayed if you run Spectral with --verbose flag #435
• Stricter source matching for errors #615

Fixed

• schema function can validate falsy values 10e5d1c
• schema function can validate Draft 6 and Draft 7 JSON Schemas ea2ddff
• Parameters in links objects are not linted for not having a description property. #272
• More accurate ranges for errors occurring in referenced files 6986b82
• CLI: stylish formatter reports info and hint severity levels correctly #565

v4.2.0-beta5

v4.2.0-beta5

v4.2.0-beta4

v4.2.0-beta4

v4.2.0-beta3

v4.2.0-beta3