Release Changelog
🚀 New Features
Prompt System Migration
-
Implemented new comprehensive prompt management system
- Complete revamp of how prompts are stored and managed in the application
- New database schema with improved relationships between models and prompts
- Support for default prompts per model
- Enhanced prompt organization and categorization
-
Added migration tools for administrators
- New admin interface for migrating data from old preset prompts system
- Two-step process: migration followed by optional cleanup
- Progress indicators and detailed success/error states
- Safety confirmations to prevent accidental data loss
- Support for bulk migration of all existing preset prompts
🛠️ Bug Fixes
Route Handler Type Fixes for Next.js 15
- Fixed API route parameters type mismatch: Updated all route handler files to use the correct Next.js 15 parameter format
- Updated route handler functions to use
context: { params: any }pattern consistently - Added proper Promise resolution for route parameters with
await Promise.resolve(context.params) - Ensured consistent parameter extraction pattern across all API routes
- Fixed DELETE and PATCH handler type definitions in nested routes
- Updated route handler functions to use
Component State Management Improvements
- Fixed MigrationPanel type errors: Improved type safety in the admin migration interface
- Introduced a proper Status enum system replacing string literals
- Updated all state handling to use the new enum values
- Added type assertions to resolve TypeScript narrowing issues in conditional expressions
- Ensured consistent state comparison throughout the component
🔧 Technical Improvements
- Enhanced TypeScript compliance: Made codebase fully compatible with stricter type checking in Next.js 15
- Consistent parameter handling: Unified approach to route handler parameter processing
- Improved state management: Replaced string literals with typed enums for better maintainability
- Build process stability: Eliminated type errors preventing successful builds
- Prompt System Architecture:
- Implemented separate tables for prompts and model-prompt associations
- Added support for marking prompts as default for specific models
- Created new API endpoints for managing the prompt system
- Server actions for prompt operations (creation, association, deletion)
📝 Notes
-
Migration Process:
- Administrators can migrate data through the new Migration Panel in the admin interface
- Old preset prompts will remain available until explicitly deleted through the cleanup step
- The migration is non-destructive; it creates new entries while preserving existing data
- After successful testing, old data can be safely removed using the cleanup function
-
All changes were implemented with minimal modifications to existing functionality
-
Existing API endpoints maintain the same behavior but with improved type safety