Maciej Urbańczyk

Clarify the shape of the SecurityRequirement Object

3

Together with @smoya we wonder if we have a good understanding of the use of the `SecurityRequirements Object` item in the `Server Object` and `Operation Object`. The specification gives the...

**Checklist** - [X] Tests added / updated - [X] Docs added / updated **Does this PR introduce a breaking change?** - [ ] Yes - [X] No PR adds support...

feat(rulesets): add rule to check if the AsyncAPI document is using the latest version.

1

**Checklist** - [X] Tests added / updated - [X] Docs added / updated **Does this PR introduce a breaking change?** - [ ] Yes - [X] No **Additional context** -...

feat(rulesets): add rule to check if messageId is defined

3

**Checklist** - [X] Tests added / updated - [X] Docs added / updated **Does this PR introduce a breaking change?** - [ ] Yes - [X] No **Additional context** -...

**Checklist** - [X] Tests added / updated - [ ] Docs added / updated - not needed **Does this PR introduce a breaking change?** - [ ] Yes - [X]...

feat(rulesets): validate unresolved AsyncAPI document

3

Fixes #2261. **Checklist** - [X] Tests added / updated - [X] Docs added / updated **Does this PR introduce a breaking change?** - [ ] Yes - [X] No **Screenshots**...

**Chore summary** As a user I want to know if I defined `$ref` fields in proper places in my AsyncAPI document **Is your feature request related to a problem?** The...

feat: integrate new parser API

1

**Description** Integrate new ParserJS API: - add new template config field `apiVersion`. - update relevant source code to handle new and old API - add some utils TODO: use released...

We should integrate new ParserAPI in Generator but with fallback compatibility with old one, solution described in the https://github.com/asyncapi/parser-js/issues/585: - add support for new (optional!) field in template's config, `apiVersion`...

**Description** As in title. I think it's clear :) We added support for `tags` in Server Objects in 2.5.0 version of spec.