fix: bump stale openapi.json info.version 0.1.6 → 0.2.0 (#60) - #90
Open
Vishnu J (vishnujayvel) wants to merge 1 commit into
Open
fix: bump stale openapi.json info.version 0.1.6 → 0.2.0 (#60)#90Vishnu J (vishnujayvel) wants to merge 1 commit into
Vishnu J (vishnujayvel) wants to merge 1 commit into
Conversation
The Scalar API docs (api.html) render whatever `info.version` is set to in openapi.json, which has been frozen at 0.1.6 since langchain-ai#46 even though the spec has since been substantially reworked (run creation consolidated under /runs, streaming, resume, etc.). Commit 59338b3 ("Small fixes for 0.2.0") shows 0.2.0 was already the intended label for that consolidation, so this bumps the field to match. Verified: valid JSON, `make format-openapi` reports the file unchanged (already prettier-formatted), and the version field isn't referenced by generated server code (`make gen-server` diff is unaffected by this change). Fixes langchain-ai#60
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Fixes #60 —
openapi.json'sinfo.versionhas been frozen at0.1.6while theAPI moved on. The
/runsendpoint consolidation that #60 references shipped with0.2.0 and is already present in the current spec, but the version string was never
bumped. The Scalar API docs page (
api.html) rendersinfo.version, so thepublished docs currently show the wrong version.
What changed
A single line in
openapi.json:Nothing else.
Why 0.2.0
This matches the causal story in #60 and the commit (
59338b3, "Small fixes for0.2.0") that landed the
/runsconsolidation. Happy to target0.2.1instead —the latest tag — if you'd prefer the newest tagged version; just say the word. I
avoided inventing a fresh
0.3.0so this stays a pure metadata correction anddoesn't imply a new release cut.
Verification
json.loadparses cleanly), andprettier --write openapi.jsonproduces zero diff (stays formatter-clean).
Thanks to the #60 reporter for catching this.