Error on Valid Schema

[ghost]

I have simple Open API specification which is based on version 3.1.0

On running analyze, I get two errors at the title line:

1. OpenAPI specification is invalid: /properties/info/$ref doesn't validate with '/definitions/Info'
2. OpenAPI specification is invalid: /properties/openapi/pattern does not match pattern '^3\.0\.\d(-.+)?$'

In both cases, "How to fix violation" shows "The schema isn't valid OpenAPI 3. Check the errors for more details".

Not sure whats wrong with the YAML manifest:

openapi: 3.1.0
info:
  title: Backend of microblogging application
  description: |-
    Mockroblog is a backend application based on course CPSC-449 Web Back-end Engineering, for the batch of Fall 2021.
    
    Links:
    - [Application homepage](https://blogger.st)
    - [Project repository](https://github.com/saurami/mockroblog)
  contact:
    name: Saurabh Mishra
    url: https://saurabh.cc
  license:
    name: MIT
    url: https://opensource.org/licenses/MIT
  version: 1.0

servers:
  - url: https://blogger.st/api/v1
    description: Production APIs

tags:
  - name: hello
    description: Hello world

paths:
  /hello:
    get:
      tags:
        - hello
      summary: Get "Hello, world!" response
      description: Get "Hello, world!" as a utf-8 encoded text response
      operationId: helloHandler
      responses:
        '200':
          description: successful operation
          content:
            text/plain:
              schema:
                type: string
              example: 'Hello!'

[daveshanley]

Interestingly, the schema error messages are not very helpful; the underlying schema library is spewing some really unhelpful messages. It's the same issues reported in #210.

I am back online in a few days. I will investigate more then.

[daveshanley]

There is improved schema issue reporting in v0.0.48. It's much more helpful.

When I run this spec through it, it tells me that the $.info.version is a number (1.0). It's supposed to be a string "1.0"

So, this isn't a bug, it's actually invalid. but thank you for your report. The schema error messages are now better because of your nudge.