Releases: ajaynegi33/FormMaillyGo
Releases · ajaynegi33/FormMaillyGo
Release list
FormMaillyGo v2.1.0 Release Notes
🚀 Major Improvements
Enhanced AWS Lambda Deployment
- NEW: Complete AWS SAM template (
template.yml) for one-click serverless deployment
Complete Documentation Overhaul
- NEW: Comprehensive step-by-step setup guide with interactive elements
- NEW: Enhanced HTML documentation with modern styling and improved user experience
- NEW: Interactive code blocks with copy-to-clipboard functionality
- IMPROVED: Clear instructions for Gmail 2FA setup, AWS account configuration, and deployment
Brand Identity & Assets
- NEW: Professional mascot illustrations and brand assets:
- FormMaillyGo-Mascot-with-Go.svg
- FormMaillyGo-Mascot-with-email.svg
- FormMaillyGoIcon-fade.svg
- FormMaillyGoIcon.svg
Backend Stability Improvements
- SIMPLIFIED: Health handler no longer depends on
PRODUCT_NAMEenvironment variable. - ENHANCED: Better AWS Lambda compatibility with optimized handler structure.
- IMPROVED: More robust error handling and configuration validation.
🐛 Bug Fixes
- FIXED: AWS Lambda server crash issue that prevented proper function execution.
- RESOLVED: Environment variable loading conflicts between main.go and aws_lambda.go.
- IMPROVED: Handler response consistency and reliability.
🎯 Upgrade Notes
Breaking Changes: None - v2.1.0 is fully backward compatible with v2.0.0
Recommended Actions:
- Update your deployment to use the new AWS SAM template for easier management
- Review the enhanced documentation for improved setup procedures
- Consider migrating to the new streamlined configuration approach
🙏 Community Support
- NEW: GitHub Sponsors integration for project sustainability
- Enhanced contribution guidelines and community resources
v1.2.0
Form-Mailly-Go V2.0.0
Added
- Custom validation engine without external dependencies
- Comprehensive email validation with 15+ distinct checks
- Security headers middleware (CSP, XSS protection, HSTS)
- Configuration validation
- Structured error response format
Changed
- BREAKING: JSON response format standardized
- BREAKING: Stricter email validation rules
- BREAKING: All environment variables now required
- Validation errors now return 400 with specific messages
Fixed
- Potential XSS vulnerabilities in email template
- UTF-8 length validation issues
- SMTP connection reuse problems
- Case-sensitive domain validation