Together Python SDK and CLI 3.1.0 add expiring secrets and GB200 clusters

Together Python SDK 3.1.0 and Together CLI 3.1.0 are now available.

tg beta jig deploy no longer stores your API key as a TOGETHER_API_KEY secret on new deployments. Existing deployments keep the secret they already have.

Sprocket 0.1.8 and later authenticate with the deployment's service token instead. Before you deploy with CLI 3.1.0, raise the sprocket pin in your image to 0.1.8 or later. If your own code reads TOGETHER_API_KEY, set it as a secret.

What's new:

• Deploy after tg login: tg beta jig deploy now works with a tg login session, so you don't need an API key to deploy a container.
• Expiring secrets: client.beta.jig.secrets.create and update take ttl_seconds, which sets how long a secret lives before it's deleted, from one to 14 days. Secrets return their deletion time as expires_at. To set an expiry from the CLI, pass --ttl to tg beta jig secrets set.
• --debug replaces TOGETHER_DEBUG: tg beta jig no longer reads the TOGETHER_DEBUG environment variable. For debug output, pass --debug.
• Idle timeout in the SDK: ModelResourcesClient.create takes inactive_timeout, the number of seconds a resource stays READY without activity before it stops. To keep a resource from stopping for inactivity while you aren't running operations, call extend_expiry.
• ready_timeout replaces timeout: ModelResourcesClient.create now takes ready_timeout, which caps how long it waits for the resource to become READY. timeout still works but shows a FutureWarning.
• GB200 GPU clusters: client.clusters.create and tg clusters create accept GB200_SXM as a GPU type.
• Applied credit in the SDK: Line items from client.organization.usage.costs.list() now include a typed applied_credit object.