Solidus Status Update – October 2025

In the last status update, I missed being able to write about the Solidus 4.6 release by just a day. So in case you didn’t know: yes, Solidus 4.6 exists and has for over a month! Since the release, a bunch of other stuff has been happening. Read more below.

A new core team member

We are more than happy to announce that long time Spree/Solidus contributor and former core team member Martin Meyerhoff has joined the core team again. You may recognize him from his work creating the new solidus_promotions system, but he’s made numerous major contributions to the community over more than ten years.

Three new releases

The Solidus 4.6.1 release fixed an issue where the shipment adjustments are not persisting on order recalculate. There was also a minor release, 0.15.0, to solidus_support with improvements to Solidus’s autoloading behavior. Lastly, we have the 2.0.0 release of solidus_volume_pricing with improvements to autoloading and support for Solidus 4.6. 🎉

Configurable stock quantifiers

In the next minor Solidus release, developers will be able to create custom stock quantifier classes in case they’d like to enhance the default behaviour without monkeypatching. (#6335)

Updates to solidus_promotions

There are a number of in-progress and merged pull requests to improve the functionality of solidus_promotions for the next minor Solidus release. In my opinion, the most notable changes are for "previewing" strikethrough prices to be calculated for variants (#6287) and, a related change, allowing the passing of options to any defined calculators in an application (#6346), opening the door for more customizable calculators. Martin also merged a lot of refactors and improvements to documentations. (Check out the huge list of pull requests: #6330 #6332 #6343 #6344 #6345 #6346 #6349 #6350 #6351 #6352 #6353 #6354).

CI/CD improvements for various Solidus extensions

A bunch of my coworkers at Super Good have been doing the thankless work of updating CI/CD configuration for various Solidus extensions to use GitHub Actions, much like we recently have on the main Solidus repository. (Historically, the Solidus organization used CircleCI.)

And more…

A few more interesting things for those of you who call yourselves completionists:

• There’s a discussion about improving how products propagate updates to taxons. (#4239)
• There were typos in some of the migrations included in 4.6.0 that would violate the latest Solidus model constraints. (#6341)
• There is a draft and a discussion about separating the users and admins into separate tables and models. (#6287, #6329)