Repository navigation
chore: sync openapi.yaml with schemas v1.4.1 (deprecated metadata key) - #156
Conversation
dafe89f to
43600ab
Compare
43600ab to
c1e8e58
Compare
|
@infer please update the PR description and title to reflect on the change. |
|
Model: Todos(agent has not posted a plan yet) Pull Request✅ Infer Result: SuccessDone - PR #156's title and description now reflect the actual change. What I updated:
One caveat: the schemas-sync workflow writes these fields itself, so if it re-runs on a future schemas update, it may retitle the PR back to its default format. Skipped: no code, doc, or commit changes (nothing to run checks on; working tree is clean), and I did not open follow-up issues since the PR body already names the only conceivable follow-up (docstring refresh), which is the user's call. Model: Tokens: 248,251 in · 11,106 out · 259,357 total (9 requests) Tool calls: 13 total · 100% success rate TracesStatsTriggered by edenreich · Infer Action · OSS |
Deterministic sync from inference-gateway/schemas at v1.4.1, regenerated with
task oas-sync SCHEMAS_REF=refs/tags/v1.4.1. Re-runs update this PR in place; it closes automatically if the repo is back in sync.This PR is spec-only: no generated or hand-written code changes.
Net change against our v1.2.2 baseline
select_metadataparameter on the list models endpoint gains adeprecatedvalue (upstream schemas PR #290 in v1.4.0, references gateway #793), and its description now explains thatdeprecatedlists models the community tables mark as deprecated, which are hidden by default, and adds no field.Impact on the SDK
inference_gateway/models.pyhas no diff in this PR becausedeprecatedadds no response field.InferenceGatewayClient.list_modelstakesincludeas a plain list of strings, so callers can already pass"deprecated"today. A future PR could refresh the docstring's supported-values list, that is all.