Automated Database Migrations & Project Health Updates
This release introduces a significant architectural enhancement with a new automated database migration system to handle schema evolution. It also includes substantial improvements to project documentation and general dependency maintenance.

🗄️ Automated Database Migration System
A generic, versioned database migration system for MongoDB has been implemented. The rationale for this system is to provide a robust, automated, and traceable way to apply schema changes on application startup, ensuring data consistency across all deployments without manual intervention.
- Introduced a new migration system that automatically detects and applies pending schema changes to the MongoDB database on application startup. [#62]
- Migrations are versioned using their Pull Request merge date and include the PR ID and summary, providing direct traceability for every schema change. [#62]
- The system is designed to be idempotent, meaning migrations can be safely run multiple times without causing errors or data inconsistencies. [#62]
- The first migration has been implemented to refactor the
adConfig
structure withinRemoteConfig
documents to a more flexible, role-based model. [#62]
📝 Documentation & Project Health
This release includes several updates focused on improving the developer experience, code clarity, and long-term project maintainability.
- The main
README.md
file has been significantly restructured for better readability, featuring collapsible sections to showcase API features in a more organized way. [#59] - Updated project dependencies, including upgrading
very_good_analysis
to9.0.0
and pinning several git dependencies to specific commit hashes for build consistency. [#61] - Added explicit type annotations to several providers and configuration files to improve code clarity and maintainability. [#61]