Solidus Status Update – July 2025

It's my third month writing these project status updates. I hope you're enjoying them. Here's what happened in the world of Solidus over the course of July 2025.

We're now using Github Actions for project CI/CD

Historically, the Solidus project has used CircleCI to run its test suite against all supported Ruby and Rails versions. We're now using GitHub Actions instead.

Note that other repositories in the solidusio and solidusio-contrib Solidus extension repositories may still be using CircleCI orbs for CI/CD. We’re looking forward to moving everything over, and if you feel so inclined to contribute to an extension, we’d love that!

Old issue grooming

If you're following old issues, you may have noticed that the team is sorting out and closing them. Expect more of this.

Work continues on the in-memory order updater

Yours truly and the team from Super Good have a working version of the in-memory order updater. Before the work can be reviewed and merged, we're now in the stage where we're testing the new updater against real applications, ensuring the Solidus test suite passes if the new updater is set as the default, and cleaning up the pull request so everyone can make sense of the new functionality. We've already pulled out some small improvements we've made as part of this work into isolated, easy-to-merge pull requests. We will probably do this a few more times over the coming month.

Stay tuned. We can hopefully get the Solidus core maintainer team to start seriously considering this for merge soon.

Using flickwerk for application overrides

There was some movement on the issue where monkeypatches in an app/overrides directory can end up being loaded more than once, thanks to Solidus contributor Martin Meyerhoff's new flickwerk gem. Since one of the tenets of Solidus is customizability, overrides being loaded twice can be an annoyance for application developers, for sure. The issue has been closed as "wontfix," but we now recommend using app/patches and flickwerk as a resolution for this issue in the future. There is more documentation and communication to be done in service of this change for application developers.

Senem Soy has created a pull request to use flickwerk in the solidus_starter_frontend which would be a much better experience for new Solidus stores.

Work continues on the new Solidus admin interface

But work has slowed down, a bit. Eugene Chaikin has taken a new job and the project is need of another developer to pick up this work. We’re grateful to Eugene for all his work on the admin. Wishing you the best at the new gig! Anyway, there is some new in-progress interface work and there are new helper methods for dealing with admin notifications.

More improvements to model associations

In June, a bunch of small improvements to existing model relationships were merged. And in July, there have been a few more. Realistically, all of these changes will be invisible 99% of the time, but they mean that data integrity and error messages are improved when something isn't quite right with your application. (See #6309, #6308, #6303, and #6305 for more info.)

And more

For the nerds:

• No longer an informal requirement, contributors must ensure their changes use I18n-localized strings in their pull requests. (solidusio/.github#17)
• Order state transition tracking is now performed in a background job, which should make your checkout page responses a tiny bit faster. #6304