Brief description of the changes and why they are needed.
Fixes # (issue number)
- 🐛 Bug fix (non-breaking change which fixes an issue)
- 🚀 New feature (non-breaking change which adds functionality)
- 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
- 📚 Documentation update
- 🔧 Code refactoring (no functional changes)
- ⚡ Performance improvement
- 🛡️ Security enhancement
- 🧪 Test improvements
- Unit tests pass
- Integration tests pass
- Manual testing completed
- No existing tests were broken
- I have added an entry to CHANGELOG.md under "Unreleased" section
- Added - New features
- Changed - Changes in existing functionality
- Deprecated - Soon-to-be removed features
- Removed - Removed features
- Fixed - Bug fixes
- Security - Security improvements
Brief description of the change for end users
- My code follows the project's code style guidelines
- I have performed a self-review of my code
- I have commented my code, particularly in hard-to-understand areas
- I have made corresponding changes to the documentation
- My changes generate no new warnings
- I have added tests that prove my fix is effective or that my feature works
- New and existing unit tests pass locally with my changes
- Code has been formatted using project standards
- No hardcoded secrets or sensitive data included
- Error handling is appropriate
- Logging is appropriate (no sensitive data logged)
Add screenshots or GIFs to help explain your changes.
- Closes #(issue number)
- Related to #(issue number)
Any additional information, deployment notes, or context that reviewers should know.
Note: This PR will not be merged without a changelog entry unless labeled skip-changelog.