You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The code at this line points to the latest version of ToolHive API, which might differ from the latest release.
An alternative might be to ship a swagger.yaml file in ToolHive releases so that we can reference it unambiguously via a static URL like described in GitHub docs.
Note that the name of the artifact should be static and not containing the version number, otherwise it would be impossible to calculate.
The text was updated successfully, but these errors were encountered:
I added a script to pull the CLI and API docs down from the latest release tarball, just need to wire it up as an action. My current idea is to trigger when a new release is cut in the app repo, and have it open a PR here to merge the updated docs, that auto-PR also becomes a good touchpoint/reminder to update other docs areas based on the release.
The code at this line points to the latest version of ToolHive API, which might differ from the latest release.
An alternative might be to ship a
swagger.yaml
file in ToolHive releases so that we can reference it unambiguously via a static URL like described in GitHub docs.Note that the name of the artifact should be static and not containing the version number, otherwise it would be impossible to calculate.
The text was updated successfully, but these errors were encountered: