-
Notifications
You must be signed in to change notification settings - Fork 9.1k
schema.json files were removed #4149
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Note: this also broke schemastore (reporting in the Slack at https://open-api.slack.com/archives/C0EDH2QKD/p1729499316054029) -- i.e. IDE type hinting globally for OpenAPI files.
Can we bring them back 🙏 ![]() ![]() ![]() |
The
These URLs return JSON. |
@leandrodamascena Thanks for reporting this! @ThomasRooney Thanks for pointing us to SchemaStore! An overview of these schemas is available on https://spec.openapis.org/ |
@leandrodamascena and others who might be reading, to explain why this happened: We're working to make it more clear that the files on The YAML documents and README are being further updated in other open PRs right now. |
Hi @handrews and @ralfhandl, thanks for clarifying this! I was able to get it working using the new URLs extracted from the base document, thanks. Closing this issue. |
PR for Schema Store has been merged: |
Hello everyone! I saw in this PR that the files https://raw.githubusercontent.com/OAI/OpenAPI-Specification/main/schemas/v3.1/schema.json and https://raw.githubusercontent.com/OAI/OpenAPI-Specification/main/schemas/v3.0/schema.json were removed because they should not be the source of truth. It turns out that I use these files a lot in my CI to compare and validate my OpenAPI schemas in many tests. I download and store them, but I update the file every 1 hour and now it's failing and breaking my CI.
I generate my OpenAPI schemas in JSON and not in YAML, which is a practice used by many and accepted by the specification.
Is there any chance to revert this change?
Thanks.
The text was updated successfully, but these errors were encountered: