> August was certainly a bit less busy across the Solidus project, and so the status update will be a bit shorter, too. > > Looking at the progress on the Solidus 4.6 milestone, we’re about ready for a minor release. 👀 Stay tuned for the announcement. > > Bug squashing > > Quite a bit of bug squashing occurred this month: > • In July, we moved all order, shipment, and payment state change tracking into background jobs to make order updates faster. However, we accidentally change the behaviour of tracking records created via the

OrderUpdater

. Luckily, we didn’t cut a release with this issue and the bug has now been fixed on

main

. (#6318) > • There was a long-standing bug where a shipment’s state would not be updated to “canceled” if every inventory unit in the shipment had been canceled. Squashed! (#6314) > • This one’s a bit complicated to summarize. A fix was merged for an issue where splitting a shipment containing backordered inventory for a single variant could result in “disappeared” backordered items during the move. (#6319) > > Work continues on the in-memory order updater > > The Super Good team and I are getting closer to a mergeable in-memory order updater implementation. This month, we pulled out individual pieces of functionality from the in-memory order updater into separate pull requests that would benefit Solidus whether or not your application would use the in-memory order updater. (#6315, #6316)