- 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 .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.
- Added shortcuts routes to the API.
- Enhanced chat handler to process shortcuts in user prompts.
- Introduced shortcuts table schema in the database.
- Updated relevant queries and shared types to include shortcuts.
- Configured environment variables for database connection.
- 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.
- 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.
- Upgraded '@aws-sdk/client-s3' to version 3.873.0 across multiple packages.
- Introduced caching mechanisms for metric data retrieval in the getMetricDataHandler function.
- Updated API endpoints to support report_file_id for cache lookups and data retrieval.
- Enhanced error handling and logging for cache operations.
- Refactored related components to accommodate new caching logic and parameters.
- Updated DELETE, GET, and POST handlers to return structured response types (ShareDeleteResponse, ShareGetResponse, SharePostResponse) for better consistency and clarity.
- Refactored permission checks and report existence validation to streamline logic.
- Improved optimistic UI updates in the frontend for sharing reports, ensuring a smoother user experience.
- Added response schemas for sharing operations to the shared reports module.
- Updated GET reports endpoint to use `getReportsWithPermissions` for improved access control.
- Added support for filtering reports based on `shared_with_me` and `only_my_reports` flags.
- Introduced `getReportsWithPermissions` function to handle complex permission logic in the database layer.
- Enhanced report metadata retrieval to ensure proper access validation before fetching report details.
- Added '@buster/data-source' dependency to the server and pnpm lock files.
- Enhanced the getMetricDataHandler function to support versioning and data source integration.
- Updated the metric data query schema to include an optional version number parameter.
- Modified the API endpoint to accommodate the new versioning feature for metric data retrieval.
- Introduced a new endpoint to retrieve metric data with pagination at /metric_files/:id/data.
- Added MetricDataParamsSchema and MetricDataQuerySchema for request validation.
- Updated GetMetricDataRequestSchema to include an optional limit parameter for pagination.
- Changed chatAssetTypeToDatabaseAssetType to a Partial<Record> for better type safety.
- Updated convertChatAssetTypeToDatabaseAssetType to throw an error for unmapped asset types.
- Modified downloadMetricFileHandler tests to use fake timers and improve timeout handling.
- Updated report sharing endpoint to use SharePermissionsUpdateRequest for better clarity.
- Renamed schemas in server-shared for backward compatibility while maintaining clarity.
- Adjusted GetTitleRequestSchema to restrict asset types to those supporting title retrieval.
- Added permission checks to metric file download handler
- Added permission checks to export-metric-data trigger task
- Created comprehensive tests for access control integration
- Updated AssetType enums to include report_file
- Resolved export conflicts in server-shared package
- Fixed AI package imports for new getPermissionedDatasets API
- Combined asset type enums from both branches
- Merged all database query exports
- Integrated access-controls package into server-shared
- Resolved conflicts in AI package instructions
- Introduced new API endpoint for downloading metric files as CSV.
- Implemented export logic to handle large datasets (up to 1 million rows) and generate presigned URLs for secure downloads.
- Added cleanup task to remove exported files from R2 storage after 60 seconds.
- Updated environment configuration to include Cloudflare R2 credentials.
- Enhanced error handling for various export scenarios.
- Refactored related database queries and schemas for better integration.
- Updated documentation for new features and usage instructions.
- Introduced `createReports` and `modifyReports` tools, enabling users to create and modify reports with improved state management.
- Added new schemas for report input and output, enhancing type safety and clarity.
- Implemented helper functions for transforming report state and generating reasoning entries.
- Improved test coverage for the new reporting functionalities to ensure robust integration.
These changes streamline the reporting process and enhance overall code maintainability.
- Removed unused properties from the dashboard state and output schemas for clarity.
- Introduced a new state file schema to better represent dashboard files.
- Updated helper functions to streamline file transformation and reasoning message creation.
- Improved type safety by utilizing the newly defined `StatusSchema`.
These changes optimize the dashboard creation process and enhance code maintainability.
- Removed unused import for `createMetricsRawLlmMessageEntry` in visualization tools.
- Introduced Zod schemas for `Dashboard` and `DashboardConfig` to enhance type validation and structure.
- Cleaned up the interface definitions for better clarity and maintainability.
These changes improve the robustness of the dashboard configuration and streamline the codebase.
- Replace ReportElementsSchema with z.any() cast to ReportElements type
- Avoid complex Zod schema inference that exceeds TypeScript serialization limits
- Maintain type safety through explicit type annotations while fixing CI compilation
Co-Authored-By: nate@buster.so <nate@buster.so>
- Use BaseReportSchema.extend() pattern to break down complex type inference
- Separate content field extension to avoid 'type exceeds maximum length' errors
- Maintain same API contract while fixing CI compilation issues
Co-Authored-By: nate@buster.so <nate@buster.so>
- Add Report schema extending ReportElements with metadata fields
- Create GET /api/v2/reports endpoint with pagination
- Create PUT /api/v2/reports/:id endpoint for updates
- Use stubbed data responses following established patterns
- Follow modular route structure and Zod-first validation
Co-Authored-By: nate@buster.so <nate@buster.so>
Nate Kelley
Wells Bunker
dal
Nate Kelley
Devin AI