Extend Avro and OpenAPI schema versions

[Pakisan]

Why do we need this improvement?

It's important for our users, who are working with latest versions of Avro and OpenAPI specifications

• OpenAPI:
  • 3.0.1
  • 3.0.2
  • 3.0.3
  • 3.1.0
• Avro:
  • 1.9.1
  • 1.9.2
  • 1.10.0
  • 1.10.1
  • 1.10.2
  • 1.11.0
  • 1.11.1

How will this change help?

It's time to allow to our users use last versions of supported schemas to stay relevant

Screenshots

No response

How could it be implemented/designed?

• OpenAPI:
  • 3.0.1
  • 3.0.2
  • 3.0.3
    • No extra changes - Schema is the same
  • 3.1.0
    • Implement new schema format (JSON Schema draft 2020-12)
• Avro
  • 1.9.1
  • 1.9.2
  • 1.10.0
  • 1.10.1
  • 1.10.2
  • 1.11.0
  • 1.11.1
    • No extra changes. At first look Schema is the same

🚧 Breaking changes

No

👀 Have you checked for similar open issues?

• [X] I checked and didn't find a similar issue

🏢 Have you read the Contributing Guidelines?

• [X] I have read the Contributing Guidelines

Are you willing to work on this issue?

Yes I am willing to submit a PR!

Closes: https://github.com/asyncapi/spec/issues/1051

[github-actions[bot]]

Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity :sleeping:

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience :heart: