basetenlabs/Truss Push

Deploy and validate a Truss model or chain on Baseten

Trust Signals

Scorecard Score: not yet scored
Maintenance Recency: Activelast commit Jun 22, 2026
License: MIT

Pinned Snippet

workflow.ymlSHA-pinned

uses: basetenlabs/action-truss-push@7c8c19be6e4d1880db111e55f4bdeea845b92b92 # v0.1.2

tags can be moved; commit SHAs can't. why a SHA?

Inputs

name	description	required	default
truss-directory	Path to a model directory containing config.yaml, or a .py file for chain deployments	yes	—
baseten-api-key	Baseten API key (from secrets)	yes	—
model-name	Override the model/chain name (maps to truss push --model-name for models, or chain_name for chains)	no	""
environment	Publish to a specific environment	no	""
include-git-info	Attach git versioning info (sha, branch, tag) to the deployment	no	true
labels	JSON string of labels as key-value pairs (e.g. '{"team": "ml", "project": "llm"}')	no	""
deployment-name	Name of the deployment. Defaults to 'PR-<number>_<sha>' on pull requests or '<sha>' otherwise	no	""
cleanup	Whether to deactivate the deployment after validation	no	true
predict-payload	JSON predict payload. For models, defaults to model_metadata.example_model_input from config.yaml. For chains, must be provided explicitly.	no	""
deploy-timeout-minutes	Max minutes to wait for deployment to become active	no	45
predict-timeout	Timeout in seconds for predict request	no	300
regional-environment	Use regional endpoint format for predict requests	no	false
team	Baseten team name to deploy to (required when the API key has access to multiple teams)	no	""

Outputs

name	description
deployment-id	Baseten deployment ID
model-id	Baseten model ID (models only)
chain-id	Baseten chain ID (chains only)
model-name	Model or chain name
deploy-time-seconds	Wall-clock seconds from push to active
predict-response	Response from predict call (truncated to 4KB)
status	One of: success, deploy_failed, deploy_timeout, predict_failed, cleanup_failed