v0.10.0 - Fix Duplicate get_recent_account_balances Methods

🐛 Bug Fixes

Fixed AccountService.get_recent_account_balances GraphQL Error (#37)

Issue: The AccountService.get_recent_account_balances() method was using a non-existent accountBalanceHistory GraphQL field, causing the error:

{'message': 'Something went wrong while processing: None on request_id: None.', 'locations': [{'line': 2, 'column': 3}]}

Solution:

• Updated to use the correct recentBalances field from the MonarchMoney GraphQL schema
• Added client-side filtering for account_id parameter
• Documented that end_date parameter is not supported by the API

Method Clarification

There are two get_recent_account_balances methods available:

1. MonarchMoney.get_recent_account_balances(start_date)

   • Original method from the base package
   • Gets balance history for all accounts
   • Only supports start_date parameter

2. AccountService.get_recent_account_balances(account_id, start_date, end_date)

   • Enhanced service method (now fixed)
   • Supports filtering by specific account_id
   • end_date parameter ignored with warning (API limitation)
   • Uses same underlying GraphQL query as the original method

🔧 Improvements

• Added daily backwards compatibility checks (previously weekly)
• Fixed compatibility check workflow to match existing test files
• Added manual workflow dispatch trigger for easier testing

👏 Thanks

Special thanks to @bmcdonough for reporting the duplicate methods confusion and GraphQL error in issue #37!

---

Full Changelog: v0.9.9...v0.10.0