What’s New
Chain deployment support
The action now supports deploying Baseten Chains in addition to Truss models. The action auto-detects which type to deploy based on the input path:
Directory → model (existing behavior, unchanged)
.py file → chain
- uses: basetenlabs/action-truss-push@v0.1
with:
truss-directory: "./my_chain.py"
baseten-api-key: ${{ secrets.BASETEN_API_KEY }}
predict-payload: '{"query": "Hello"}'
Chain deployments get the same lifecycle as models: deploy, wait for all chainlets to be ready, optionally run a predict request, and clean up.
New input:
model-name now also sets the chain name for chain deployments
New output:
chain-id — the Baseten chain ID (empty for model deploys)