Blog
Releases, announced.
What we ship and why it matters, written as the organization. The people who build these frameworks write in their own voice on the project sites.
Green Tea 26.9.0-beta.1: three crashes closed, and a registry that now works
A CORS predicate, a custom error handler and a connection cap could each take a process down. All three are fixed, the JSR package resolves for the first time, and boot no longer waits on providers that do not depend on each other.
Green Tea 26.8.0-beta.1: an observability contract, and a second registry
A correlated event stream and an injectable logger, shutdown you can hook into, a routing change to read before upgrading, and the first publish to JSR alongside npm.
How a release reaches you
Two registries, build provenance without a stored token, release notes that are published rather than only tagged, and documentation that ships on its own clock.
Expressive Tea 2.0.1, and what maintenance means from here
The 2.0 line is where Expressive Tea stops adding and starts holding. What still gets patched, what never will, and which version you should not be running.
Green Tea: declare intent, derive execution
The framework Expressive Tea Software is building now. Your API is a graph of steps that declare what they need and what they produce — the order is computed, not maintained by hand.
A rebrand that did not redraw the logo
Expressive Tea Software had been sharing its name with one of its own frameworks — the one that stopped taking features. Fixing that took a hierarchy, not a new cup.