Don't link to latest URL of JSON Schema
#330
Labels
Comments
|
Welcome to OpenRPC! Thank you for taking the time to create an issue. Please review the guidelines |
|
@Relequestual thanks for the issue. Im not sure to which url you are referring. Can you provide a link? |
|
Ah, terrific. thanks for that! |
BelfordZ
added a commit
that referenced
this issue
Apr 16, 2021
BelfordZ
pushed a commit
that referenced
this issue
Feb 1, 2023
# [1.3.0](1.2.6...1.3.0) (2023-02-01) ### Bug Fixes * bump node version and update circle config ([52403aa](52403aa)) * dont point to latest json schema ([114202c](114202c)), closes [#330](#330) * follow conventional capitalization pattern ([bb3b838](bb3b838)) * markdown inside html doenst work ([664eec1](664eec1)) * missing bracket ([8f6e649](8f6e649)) * re-order release perparation steps ([4893ac8](4893ac8)), closes [#292](#292) * remove example object referencing content descriptor use ([b9f00de](b9f00de)), closes [/github.com//issues/315#issuecomment-718258896](https://github.com//github.com/open-rpc/spec/issues/315/issues/issuecomment-718258896) * s/supercedes/supersedes/ ([91533e3](91533e3)) * shamelessly add funding link via open collective ([c3f8de2](c3f8de2)) * typo in Example Object ([c551b21](c551b21)) * update discord link ([d75ceeb](d75ceeb)) * update labler to v4 ([cd3ac52](cd3ac52)) ### Features * add support for strict notification methods ([a9a3091](a9a3091)), closes [#230](#230)
|
🎉 This issue has been resolved in version 1.3.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
and others
In the specification document, you link to a JSON Schema URL which includes
latest. This is not ideal, and we plan to deprecatelatestvery soon.Also, that link will be breaking very soon (as soon as I fix some issues and push changes for draft 2020-12).
Thanks for using JSON Schema =]
The text was updated successfully, but these errors were encountered: