Wanaku 0.1.3 and the road to 0.2.0

Wanaku 0.1.3 is out.

This release continues the work that landed across 0.1.1, 0.1.2, and 0.1.3, with a good mix of new capabilities and cleanup work. On the feature side, I am especially happy to see the new GitHub pull request tools, the non-blocking MCP operations, and the improvements around service template properties. There is also a steady batch of UI polish and small usability fixes that make the project easier to work with day to day.

Just as important, 0.1.3 also includes a number of practical fixes: CLI launch script improvements, runtime initialization fixes, OIDC tenant corrections, and the move to Quarkus 3.33.2. It is the kind of release that makes the project feel more solid.

If you want the full breakdown, check the official release post: Wanaku 0.1.3 Released.

I am already thinking ahead to 0.2.0. The area I want to keep pushing the most is better integration between Camel, Wanaku, and Kubernetes, so the path from local development to real deployment feels more natural and less pieced together. Beyond that, I expect 0.2.0 to continue the same discipline as 0.1.3: more fixes, more smoothing of rough edges, and more work to make the platform easier to operate in practice.

Wanaku is still moving quickly, but this release feels like a good step toward a more mature 0.2.0 line.