New Schema Files not able to resolve top level `$ref`

[scotttyso]

Describe the bug

Expected Behavior

JSON Schema should resolve

Current Behavior

I am attempting to create a new schema and the top level $ref is saying it cannot be resolved. In troubleshooting, I found that only an old schema on GitHub was working. To isolate, I downloaded the older schema and uploaded it to another repository and the schema will not resolve the top level reference with the same file. It being a copy of the same file that is working from a commit around a year ago.

I have the following in VS Code settings.json

    "yaml.schemas": {
        "https://raw.githubusercontent.com/scotttyso/Cisco-AI-Pods/147be45524687406c29997e75dc6bceef64257c8/schema/easy-imm.json": "*.ezai.yaml",
        "https://raw.githubusercontent.com/terraform-cisco-modules/easy-imm/15d4fe511ec8e339b070edc54934e34cae2e6e06/yaml_schema/easy-imm.json": "*.ezi.yaml"
    },

Here is an example YAML content to use the schema

example:
  pools:
    mac:
      - name: mac-pool
        mac_blocks:
          - from: 00:25:B5:0A:00:00
            size: 255

If I name the file example.ezi.yaml the Schema works as expected.
If I name the file example.ezai.yaml the schema fails to load with the error:

$ref '/components/schemas/easy_imm' in 'https://github.com/terraform-cisco-modules/easy-imm' cannot be resolved.

The only difference between the two json schema files is one is from today and one is from Jun 30, 2025.

I also see the error if I use a more current version of the schema in the same repository that is working. I thought I was going Crazy

Steps to Reproduce

1. Create YAML file with two different extensions as shown above

Environment

• Windows - Using Remote SSH to Linux Host or WSL local Container
• Mac
• Linux - Extension Version 1.21.0
• other (please specify)

[scotttyso]

It was a strange behavior, but after more testing, it doesn't seem like the openAPI framework of schemas anymore and prefers using the definitions framework. After moving to the definitions framework and rebuilding the schema, I am not seeing this issue anymore.