Forge 2.0 - Complete Rewrite

We've completely rebuilt Forge from the ground up with a focus on performance, type safety, and developer experience. This major release includes breaking changes but provides significant improvements across the board.

• •Complete rewrite with 3x performance improvements in routing and middleware
• •New dependency injection container with compile-time type safety
• •Enhanced observability with structured logging, metrics, and distributed tracing
• •Improved extension system with better lifecycle management
• •Better documentation and examples for common use cases

Bug Fixes

• •Fixed race condition in middleware chain execution
• •Resolved memory leak in connection pooling
• •Fixed OpenAPI schema generation for nested types

Security Enhancements & Rate Limiting

Major security improvements including advanced rate limiting, enhanced authentication, and better error handling throughout the framework.

• •Advanced rate limiting with Redis backend support and distributed rate limiting
• •Enhanced security middleware with CSRF protection and secure headers
• •Improved error handling with structured error responses
• •Better input validation with automatic sanitization
• •Updated dependencies to address security vulnerabilities

Bug Fixes

• •Fixed authentication edge cases in multi-tenant scenarios
• •Resolved rate limiter reset issues
• •Fixed error stack trace exposure in production mode

WebSocket Support & Middleware Improvements

Added first-class WebSocket support and a completely redesigned middleware system for better composability and performance.

• •Native WebSocket support with connection pooling and automatic reconnection
• •New middleware system with improved error handling and async support
• •Enhanced OpenAPI generation with better type inference
• •Performance optimizations in routing and request handling
• •Added middleware for automatic request/response compression

Bug Fixes

• •Fixed middleware ordering issues in certain edge cases
• •Resolved OpenAPI generation bugs for complex schemas
• •Fixed memory leak in long-lived WebSocket connections