Release [Develop → Master]

[kenyipp]

Summary

Type of Change

• 🐛 Bug fix (resolves an issue without affecting existing functionality)
• ✨ New feature (adds functionality without breaking existing behavior)
• 💥 Breaking change (alters existing behavior or introduces incompatibilities)
• 📝 Documentation update (changes to documentation or README)

List of Changes

Testing Details

Merge Workflow Checklist

For New Features / Fixes

• Ensure the PR targets the develop branch.
• Use a descriptive PR title with relevant issue/ticket references (if applicable).
• Include relevant design documents, requirements, or tickets in the PR.
• Provide screenshots, logs, cURL requests, or backend call samples where relevant.
• Follow the Squash Commits strategy, ensuring the commit message matches the PR title and follows internal contribution guidelines.

Release Workflow

• Set the PR target to main (source branch: staging).
• Use Merge Commits with the message: Release [Develop → Master].

[kenyipp]

🎉 This PR is included in version 1.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀