We just tagged v1.0.1-alpha-4. Here is a summary of what changed.
UI Library Extracted
The biggest change in this release is a dedicated ui-style library. All shared UI styles that were previously scattered across the stack now live in a single, independently publishable package. This brings the total library count from 19 to 20 and makes it straightforward to apply a consistent visual language across applications without pulling in unrelated dependencies.
Extended Ecommerce API Example
The ecommerce-api example has been significantly extended. It now covers more of the order lifecycle — product catalogue, cart, checkout, and order history — and demonstrates how Boundary’s HTTP, database and validation layers work together in a realistic context. If you are evaluating Boundary for a commercial project, this is the best place to start.
Bug Fixes
Several issues reported since v1.0.0-alpha have been resolved, including:
-
Incorrect default middleware ordering in the HTTP layer
-
Missing transaction rollback on constraint violations in the database layer
-
Race condition in the scheduler when multiple jobs share the same cron expression
Documentation
Documentation coverage has been expanded across multiple libraries. Notable additions include a reference page for the ui-style library, an updated library overview reflecting the new count, and improved inline examples throughout the getting-started guide.
What’s Next
The focus for the next alpha will be on stabilising the authentication and session management libraries and shipping a production deployment guide.
Feedback and issues welcome on GitHub.