Release: merge next-release into main #64
No reviewers
Labels
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: cal/major-domo-database#64
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "next-release"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
11 commits from
next-releaserebased ontomainand ready to ship.limit/offsetto DB inPlayerService.get_players(#37)PlayerServicewrite operations (#32)WEEK_NUMSdict fromdb_engine.py(#34)sort_byparameter withLiteraltype inviews.py(#36)print(req.scope)withlogger.debugin/api/docs(#21)standings.pyandpitchingstats.py(#30)except:withexcept Exception:(#29)lob_2outsandrbipercentinSeasonPitchingStats(#28)Conflict resolution
Rebased (not squash-merged) to surface conflicts cleanly. Resolved:
battingstats,results,schedules,transactions,pitchingstats,custom_commands): kept main's@router.post("/")trailing slash fix; applied next-release's functional changes on toptransactions.py: preservedfn.UPPER(Team.abbrev)case-insensitive filter from mainrequirements.txt: kept main's fully-pinned deps includingstarlette==0.52.1standings.py: took next-release's import block (pydantic import removed, genuinely unused)Test plan
team_abbrevfilter on transactions still works case-insensitivelylimit/offset) works correctlyexcept:blocks remain:grep -r "except:" app/