release: 0.31.0

[stainless-app]

Automated Release PR

0.31.0 (2025-11-14)

Full Changelog: v0.30.0...v0.31.0

⚠ BREAKING CHANGES

• api: Access to the api for listing checkpoints has changed its name to list_checkpoints
• api: Access to fine tuning APIs namespace has changed from fine_tune to fine_tuning

Features

• api: Add audio.voices.list sdk (890595e)
• api: Add batches.cancel API (b1133f8)
• api: Add endpoints.list_avzones (606fea8)
• api: Add fine_tune.delete API (79d0c84)
• api: api update (4be10bc)
• api: api update (e594a76)
• api: api update (8ec7bf0)
• api: api update (04797be)
• api: api update (c219bfd)
• api: manual updates (9f78929)
• api: Update Eval APIs (c91b8c0)

Styles

• api: Change fine tuning method retrieve_checkpoints to list_checkpoints (b2c168a)
• api: Change fine tuning namespace to fine_tuning (77b1211)

---

This pull request is managed by Stainless's GitHub App.

The semver version number is based on included commit messages. Alternatively, you can manually set the version number in the title of this pull request.

For a better experience, it is recommended to use either rebase-merge or squash-merge when merging this pull request.

🔗 Stainless website
📚 Read the docs
🙋 Reach out for help or questions

---

Note

Bumps to 0.31.0 with fine_tuning namespace and listCheckpoints rename, adds audio voices listing, batch cancel, endpoint availability zones and filters, and substantially updates Evals APIs/types.

• Version: 0.31.0
• Breaking:
  • Rename client.fineTune → client.fineTuning; method retrieveCheckpoints → listCheckpoints.
  • Endpoints CRUD now return DedicatedEndpoint type.
• New APIs:
  • client.audio.voices.list() → fetch available TTS voices.
  • client.batches.cancel(id) → cancel batch jobs.
  • client.endpoints.listAvzones() → list availability zones; list supports mine and usage_type filters.
• Evals Overhaul:
  • Add evals.create, evals.update, evals.status; evals.list moved to /evaluation; new/updated types (EvaluationJob, EvalStatusResponse, etc.).
• Other:
  • Chat/Completions streaming deltas include optional reasoning field.
  • Docs (api.md), tests, and exports updated accordingly.

^{Written by Cursor Bugbot for commit 67951c6. This will update automatically on new commits. Configure here.}

[cursor]

This PR is being reviewed by Cursor Bugbot

Details

Your team is on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle for each member of your team.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

[cursor]

Bug: User Input Overrides Required API Parameters

The delete method spreads options after setting the query property, allowing user-provided options.query to override the required force parameter. This means the force value from params could be lost if the caller passes query in options, breaking the API call.

 

[cursor]

Bug: API Inconsistency Prevents Reasoning in Chat Creation

The reasoning field is missing from CompletionCreateParams.ChatCompletionAssistantMessageParam but present in the top-level ChatCompletionAssistantMessageParam and in response types. This inconsistency prevents users from including reasoning in assistant messages when creating chat completions, even though the API supports it in responses.

src/resources/chat/completions.ts#L535-L548

together-typescript/src/resources/chat/completions.ts

Lines 535 to 548 in 0eb8879

	export interface ChatCompletionAssistantMessageParam {
	role: 'assistant';
	content?: string | null;
	/**
	* @deprecated
	*/
	function_call?: ChatCompletionAssistantMessageParam.FunctionCall;
	name?: string;
	tool_calls?: Array<CompletionsAPI.ToolChoice>;

 

---