Deployment and versioning
Endpoints and tools deploy hot — no restart, no downtime. The previous version stays live until the new one compiles successfully.
Promoting code across environments:
# Export from dev
curiosity-cli export-workspace-definitions \
-s https://dev.workspace.example.com -t $DEV_TOKEN \
-o ./workspace-definitions/
# Import into staging
curiosity-cli import-workspace-definitions \
-s https://staging.workspace.example.com -t $STAGING_TOKEN \
-i ./workspace-definitions/
Store the exported definitions in git. This gives you a full history, code review on endpoint changes, and a one-command rollback.
Versioning endpoints:
Breaking changes → new endpoint with a version suffix:
similar-tickets ← current, in use
similar-tickets-v2 ← new version, deploy alongside
Run both in parallel during migration. Retire the old one when all callers have switched.
Rollback: revert in the editor (history is kept per save) or re-import the previous exported definitions.