dust-breaking-changes
API Breaking Changes - Critical Rule
CRITICAL: You must NEVER introduce breaking changes to the private API without explicit user approval.
What is a Breaking Change?
A breaking change is any modification that would require existing API consumers to update their code, including:
- Endpoints: Removing or renaming API endpoints
- Schemas: Changing request/response schemas
- Removing fields from responses
- Changing field types (string → number, object → array, etc.)
- Making optional fields required
- Renaming fields
- Authentication: Modifying authentication or authorization requirements
- HTTP Methods: Changing HTTP methods (GET → POST) or status codes
- Error Formats: Altering error response formats or codes
- Query Parameters: Removing or making required previously optional parameters
- Headers: Requiring new headers or changing header validation
More from dust-tt/dust
react-hook-form-writer
Write and refactor React forms using react-hook-form with Zod validation. Use when creating new form components, converting existing forms to react-hook-form, or implementing form validation patterns.
74dust-mcp-server
Step-by-step guide for creating new internal MCP server integrations in Dust that connect to remote platforms (Jira, HubSpot, Salesforce, etc.). Use when adding a new MCP server, implementing a platform integration, or connecting Dust to a new external service.
60dust-temporal
Step-by-step guide for creating Temporal workflows in Dust. Use when adding background jobs, async processing, durable workflows, or task queues.
59dust-llm
Step-by-step guide for adding support for a new LLM in Dust. Use when adding a new model, or updating a previous one.
55dust-test
Step-by-step guide for writing focused, practical tests for Dust codebases following the 80/20 principle.
54writing-react-effects
Writes React components without unnecessary useEffect. Use when creating/reviewing React components, refactoring effects, or when code uses useEffect to transform data or handle events.
53