Solidus Status Update – May 2025

Hey, we’re trying something new. This is a quick summary of what was happening in open source for the Solidus organization last month.

A lot happens every month. We’re not going to overturn every stone, but we think it's worth highlighting where progress and improvements are being made, as well as the trajectory of the project as the community generates new discussions and issues—and as the world of e-commerce evolves.

Please let us know in the Solidus Slack organization or on GitHub Discussions if you like this or have any suggestions to help us make it more valuable.

The project roadmap

Lasse Diercks popped in to encourage the project to adopt a more transparent roadmap process. And after some discussion, there was movement on how we might proceed here: double-down on the existing GitHub project called "Roadmap".

You can read the whole discussion here.

I personally appreciate Lasse's nudge to be more communicative about the state of the project, which is part of the reason I wanted to make these Solidus status updates a thing.

New solidus_dev_support release

The solidus_dev_support gem, which is used to bootstrap and support Solidus extensions, received a new minor release (v2.12) that changes the custom RuboCop configuration included with the gem to be configured like standardrb.

The goal here is to help extension developers reduce code churn related to opinionated code style changes that occur with many RuboCop releases.

Work continues on the Solidus admin

Eugene Chaikin's work on solidus_admin (the next-generation Solidus admin interface) continues. For the last few months, Eugene has been consistently submitting new features, improvements, and bug fixes for various admin requirements. You can follow along on the GitHub project for the new admin.

Solidus 4.6 will include these notable improvements merged this month:

• New user management interfaces for admins.
• Zone creation and modification interfaces.
• A new alert component for showing error messages and success messages as toasts.
• Improvements to sorting and pagination of records.
• Improvements to the admin address form components.

There is even more in-progress Solidus admin work that we'll likely be able to call "merged" by my next status update.

New promotion calculator

solidus_promotions now includes a new calculator: PercentWithCap. An admin can now configure, for example, a promotion like "15% of the total order up to a maximum discount of $50 USD". This calculator will be available when Solidus 4.6 is released.

Configurable event subscribers

Yours truly and Adam Mueller merged some new functionality that allows application developers to easily unsubscribe from the event subscribers built into Solidus.

This means that it's easier than ever to turn off all or a subset of Solidus's built-in transactional emails. It also means that any event subscribers added to Solidus in the future will by default be configurable at the application level. This is a huge win for the flexibility of Solidus as a platform.

You can read the documentation about this on the "next" track of the Solidus Guides.

Work continues on an in-memory order updater

The Super Good team and I are slowly working away at a draft pull request that introduces a drop-in replacement to the current order updater that does all its work without writing to the database.

There are a bunch of benefits to this: speed and performance first and foremost. But it also opens up the ability to preview changes or orders or even simulate entire orders.

Improvements for Solidus developers

Nothing major, but application developers may be relieved about any of these things:

• Using Firefox for feature tests instead of Chrome. (#6230)
• Improvement to current_api_user and current_user_roles helpers which make them more accessible to framework and application developers. (#6246, #6245)
• New applications using solidus_auth_devise will have better Devise configuration generated for them. (solidus_auth_devise#257)
• The address book model now has improved constraints to harden user address management reliability. #6265
• A taxon association, that should only be applied if the solidus_legacy_promotions system is being used, has been removed from solidus_core. #6243
• Work continues on transitioning the project from using CircleCI to using GitHub Actions for all its CI/CD.