- Added new deployment functionality to handle both models and documentation in a single request.
- Introduced new schemas for unified deployment requests and responses using Zod.
- Updated deployment handlers to process and validate models and docs together.
- Enhanced logging to provide detailed information about deleted models and docs during deployment.
- Refactored existing code to integrate the new deployment structure, ensuring backward compatibility with previous functionalities.
- Introduced new API routes for managing documents, including listing, creating, updating, and deleting documents.
- Implemented database queries for document operations.
- Added validation schemas for request and response types using Zod.
- Updated the database schema to include a 'docs' table with necessary constraints.
- Integrated the new docs functionality into the server and shared packages.
- Added `TURBOPUFFER_REGION` to the environment configuration.
- Modified the `createClient` function to utilize the new `TURBOPUFFER_REGION` variable.
- Updated the `generateNamespace` function to return the data source ID directly instead of prefixing it.
- Adjusted various tests and sync job logic to reflect changes in namespace generation and ensure consistency across the application.
- Added .actrc to .gitignore to prevent local configuration from being tracked.
- Updated cli-release.yml to specify paths for apps and packages, enhancing workflow triggers.
- Improved permissions in cli-release.yml for better access control.
- Enhanced update-brew-tap.yml with detailed summary creation for deployment results.
- Introduced README.md for GitHub Actions, providing usage instructions and supported platforms.
- Added deploy and dry-run actions for better deployment management.
- Updated error handling in CLI commands for clearer messaging and improved user experience.
- Bumped CLI version to 0.3.0 in package.json to reflect recent changes.
- Introduced `init` command to initialize a new Buster project.
- Updated `deploy` command options to clarify the path description.
- Removed unused options from the deploy command.
- Refactored deployment logic to improve error handling and response processing.
- Enhanced configuration loading to ensure required fields are validated.
- Added spinner component for better user feedback during loading states.
Updated DEFAULT_CACHE_OPTIONS in analyst and think-and-prep agents to include gateway options. Added gateway settings in multiple steps including analysis-type-router, create-todos, extract-values, generate-chat-title, flag-chat, format-follow-up, format-initial, and identify-assumptions steps to restrict provider usage to 'anthropic'. This enhances control over the AI model interactions.
- Enhanced the CLI with new linter rules and updated file structures for better organization.
- Modified package.json to reflect changes in dependencies and ensure compatibility.
- Improved the vitest configuration for better testing practices.
- Refactored various components for consistency and readability, including imports and error handling.
- Updated the server API and database queries to streamline authentication processes.
- Removed deprecated code and cleaned up unused files to maintain a tidy codebase.
- Added new CLI commands for authentication management and improved default action handling.
- Updated package.json to include new dependencies and scripts for building and running the CLI.
- Integrated authentication features into the SDK, allowing for API key validation.
- Modified the SDK configuration to use a new default API URL.
- Expanded the server API to include authentication routes.
- Updated database queries to support new API key functionalities.
- Improved code structure and readability across CLI and SDK components.
- Added bucketName to S3 integration responses and handlers to support bucket-specific operations.
- Updated tests to reflect the inclusion of bucketName in integration creation and retrieval processes.
- Improved error handling for fetching bucket names from the vault during S3 integration retrieval.
These changes improve the S3 integration management by allowing for more granular control and visibility of storage buckets.
- Simplified S3 integration handler functions by consolidating imports and improving code readability.
- Updated error handling in the S3 integration process to enhance clarity and maintainability.
- Refactored storage provider functions to utilize a more modular approach, separating concerns for better organization.
- Introduced utility functions for common operations, improving code reuse and reducing duplication.
These changes enhance the overall structure and maintainability of the S3 integration management features.
- Added routes for creating, retrieving, and deleting S3 integrations in the API.
- Introduced handlers for S3 integration operations, including validation of user permissions and storage credentials.
- Updated database schema to support S3 integrations, including a new table and associated queries.
- Integrated storage provider logic to handle S3, R2, and GCS configurations.
- Enhanced error handling and response structures for integration operations.
This commit lays the groundwork for managing storage integrations within the application, allowing users to connect and manage their S3 storage solutions.
- Modified the SSL configuration in both the PostgreSQL adapter and its tests to use { rejectUnauthorized: false } instead of a boolean true value.
- Ensured consistency in handling SSL settings across the adapter and its tests.
- Updated all database adapter tests and implementations to replace the 'database' field with 'default_database' for consistency.
- Ensured backward compatibility in the Redshift adapter by allowing both 'database' and 'default_database' fields.
- Enhanced SQLServer and MySQL adapters to reflect the new credential structure, improving clarity and maintainability.
- Added checks to ensure toolCallId exists and is a valid string before processing tool results.
- Preserves the original part if toolCallId is missing or invalid, improving robustness in message conversion.
- Updated logic to prioritize cache as the source of truth during streaming, with asynchronous database updates for persistence.
- Improved error handling for background database updates, ensuring cache validity even if DB update fails.
- Cleaned up mergeResponseMessages and mergeReasoningMessages functions by removing redundant code.
- Introduced lru-cache version 11.1.0 in package.json and pnpm-lock.yaml.
- Refactored updateMessageEntries to utilize TypeScript-based merge logic with write-through caching.
- Improved error handling for fetching existing message entries and updated database logic to merge new entries with existing ones.
dal
Nate Kelley
jacob-buster