You can now configure a managed dependency
v1.0.0-rc.5 is released. environment.dependencies accepts an env: map, so a managed Postgres, Kafka or SQL Server can be configured the way a service already could.
Release notes, engineering write-ups and provider-ecosystem updates land here.
v1.0.0-rc.5 is released. environment.dependencies accepts an env: map, so a managed Postgres, Kafka or SQL Server can be configured the way a service already could.
I spent most of today pushing vouchfx further into the “AI can actually help author tests” space. Not a big marketing launch — more a day of shipping foundations, arguing with myself about product shape, and cleaning up the mess that follows when five docs sites must stay honest.
I already wrote about the broader agentic day — catalogue, scaffold, the boring foundations. This post is only about the Healer: diagnose_run on vouchfx-mcp, and the one rule I will not break.
The documentation site for vouchfx-mcp is live, at vouchfx-mcp.vouchfx.io. It is the fifth site in the family and probably the one that needs the most explaining, because "MCP server for an integration testing engine" does not tell you much on its own.
v1.0.0-rc.1 is released. This is the first release candidate for v1.0, following v1.0.0-alpha.10. I ran the whole fleet locally against the release commit before tagging: all four sample applications pass end-to-end on real Docker topologies, the community provider conformance suite runs clean, and the engine examples and MCP server are stable.
v1.0.0-alpha.9 is released. This is a single-fix correctness release addressing step timeout field enforcement. The engine now enforces declared timeouts as an upper bound on every step, regardless of verify mode, matching the documented behaviour.
vouchfx's documentation has migrated to a new Material for MkDocs site. The design, layout, and navigation remain consistent with the previous build, and this blog provides a new home for release notes and engineering write-ups.