OroCommerce
B2B ecommerce
OroCommerce ships 7.0 LTS while quietly opening the back office to AI agents via MCP.
◆Recent moves
- 8d ago
OroCommerce 7.0 LTS is now available
⚡ SPARKOroCommerce 7.0 LTS is the first major LTS cut since 6.1 in mid-2025, formalizing the new long-term-support baseline that customers will run for years. As the standalone release entry it contains only a pointer to the public announcement, but the surrounding 6.1.x stream tells the actual story of what the line has been absorbing — MCP tools, SSO enforcement, headless-API improvements.
View source ↗ - 20d ago
OroCommerce 7.0.1 patch — bug fixes after the LTS cut
OroCommerce 7.0.1 is a fix-only patch immediately following the 7.0 LTS cut — the kind of post-release polish that catches HTML validation issues, shopping list permission edge cases, and large-catalog reindex failures. Reasonable churn for a new LTS in its first two weeks.
View source ↗ - 1mo ago
MCP back-office tools land in OroCommerce 6.1.8
⚡ SPARKThe 6.1.8 release introduces MCP tools for managing orders, customers, and customer users from the back office, plus storefront SSO enforcement, RabbitMQ 4 quorum queue support, and absolute-URL API options aimed at headless front-ends. The MCP tooling is the directional move — it opens OroCommerce records to AI agents through a standard protocol rather than a one-off integration.
View source ↗ - 1mo ago
Feed noise: scraped GitHub user profile
A GitHub user profile page that was scraped into the changelog feed. Not a release — content shows navigation, follower counts, and contribution-graph filler. Excluded from any meaningful read of the product's trajectory.
View source ↗ - 1mo ago
Feed noise: GitHub App profile page
Another scrape artifact — this one a GitHub App profile page for the Jenkins CI integration used by OroCommerce. No release content, no signal beyond confirming the feed source is over-broad.
View source ↗ - 1mo ago
Feed noise: scraped GitHub contributor profile
A third scraping artifact, this one a GitHub contributor profile rather than a release. Not actionable signal; pattern suggests the feed-ingest logic needs a filter to drop non-release pages from oroinc-adjacent GitHub URLs.
View source ↗