Skip to content

Prod - August 2026 Release 3 - #139

Merged
jmgasper merged 15 commits into
masterfrom
develop
Aug 18, 2026
Merged

Prod - August 2026 Release 3#139
jmgasper merged 15 commits into
masterfrom
develop

Conversation

@jmgasper

Copy link
Copy Markdown
Collaborator

jmgasper and others added 15 commits August 12, 2026 19:53
What was broken

Date filters could omit the selected end date or, after making it inclusive, show late July 31 SFDC payments as August 1. Monthly BA fees could also place those payments in the next month.

Root cause

Finance payment timestamps are stored as UTC values without timezone metadata. Date bounds were interpreted as instants or through the database session timezone, while SFDC output applied the America/New_York conversion in the wrong direction.

What was changed

Interpret report filters as calendar dates with half-open next-day bounds. Convert SFDC New York calendar bounds to UTC for payment storage, return payment dates with the correct New York offset, and group BA fees by the corrected New York date.

Any added/updated tests

Updated SQL regression coverage for payment accruals, SFDC payments, both BA fee variants, monthly buckets, and report-directory metadata. PostgreSQL 16 checks cover the July 31 boundary and daylight-saving transitions.
…tics

PM-4620 - fix report for member details
PM-5834 - add support for live leaderboard scoring based on ai decissions
PM-5839: Correct payment report calendar dates
…onal-data

MM leaderboard - provisional data fix
…provisional

MM leaderboard - provisional data fix
@jmgasper
jmgasper merged commit 5e91349 into master Aug 18, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants