v3.0.1

3.0.1 (2026-04-21)

Bug Fixes

• ETU-70915: Turn off rule "info-contact" (#109) (b9e2e29)
• Set API-spec version automatically (using CalVer convention) (3f21893)

v3.0.0

3.0.0 (2026-04-01)

⚠ BREAKING CHANGES

• ETU-66996: Add entur extensions as errors to spectral rulesets (#101)

Features

• ETU-66996: Add entur extensions as errors to spectral rulesets (#101) (dfd9a72)

v2.2.4

2.2.4 (2026-03-31)

Bug Fixes

• entur-request-body-description updated to allow description on schema referenced in content.*.schema. (a3211ff)
• Allow header "Entur-POS" since it is standard (#102) (7480b19)
• ETU-69952: Add default as allowed response code (#103) (39294d5)

v2.2.3

2.2.3 (2026-03-16)

Bug Fixes

• ETU-69733: Add 302 as valid response code for GET (#99) (56f3999)

v2.2.2

2.2.2 (2026-03-10)

Bug Fixes

• Add 201 as allowed response to PUT (#97) (3ac6331)

v2.2.1

2.2.1 (2026-02-27)

Bug Fixes

• Disable no-$ref-siblings rule from required ruleset (#95) (5f8e8b7)

v2.2.0

2.2.0 (2026-02-23)

Features

• Add ci workflow to check that linting works (#93) (4c719cb)
• Add lint rules to more x-entur-metadata fields (#92) (a12c96c)

v2.1.0

2.1.0 (2026-01-29)

Features

• ETU-66252 Add guidelines for merging apis (f6065e4)
• ETU-66252 Add guidelines for merging specs (0d545a1)
• ETU-66252 Add lint rule that parentId is formatted correctly (46845a2)

Bug Fixes

• Clarify that x-entur-metadata.id should identify spec, not service (#90) (7e1cfe3)

v2.0.2

2.0.2 (2026-01-14)

Bug Fixes

• Allowing HTTP response code 423 for delete, post, put, patch. (#87) (5bc3566)
• Added custom function requireExampleOrRef which looks for examples in components referenced in schema.items (when schema.type == 'array'). (#84) (1d47976)
• Schema properties which have type: array and items { $ref } no longer needs an example. (5358854)
• Severity of rule 'entur-rfc-9457-content-type' changed to warning. (#86) (60395da)

v2.0.1

2.0.1 (2025-12-02)

Bug Fixes

• API-571: Added info about "info.title" linting in guidelines. Moved linting rules to correct sections, so that it matches guidelines. (#77) (beec7fe)
• API-578: Header "ET-Client-Name" not necessary. (#79) (45c5c4d)