Lol, speaking of bugs, this change actually broke my live trading to today, and of course I spent the whole deal trying to figure out what was wrong without considering that it was THIS change that caused the issue. Leaving details in case it helps others.
In short, if you haven't yet upgraded to 2.6, and you're using both history and realtime databases together, such as when live trading, specifying start and end dates to strategy.trade or get_prices will NOT pass the correct timezone to the realtime service and thus you'll likely get incorrect prices which are being cut off due to a wrong timezone. See related post here.
In summary, if you haven't upgraded to 2.6, do not specify an end_date within the Moonshot.trade method as I posted above . Alternative, you can specify the timezone offset with your end_times that are being passed to Moonshot.trade or get_prices.
Hope this helps someone else!
P.S. @brian in 2.5 there is a related bug that mostly goes unnoticed here. Basically, when only specifying a start date, the lookback period is offsetting the start_date and thus hiding the timezone offset issue when using a realtime database. This could be a problem if your lookback is set too tightly as you'd be missing some prices due to the timezone offset. In 2.6, as long as a Monshoot.TIMEZONE is set, this won't be a problem but just something to note.