Announcing Flower 1.36

The Flower team is excited to announce the release of Flower 1.36 stable, packed with new updates!

Flower is a friendly framework for collaborative AI and data science. It makes novel approaches such as federated learning, federated evaluation, federated analytics, and fleet learning accessible to a wide audience of researchers and engineers.

Thanks to our contributors

We would like to give our special thanks to all the contributors who made the new version of Flower possible (in git shortlog order):

Charles Beauville, Daniel J. Beutel, Dimitris Stripelis, Heng Pan, Javier, Lorenzo Sani, Taner Topal, Yan Gao

What's new?

• Prepare the Flower CLI to use HTTP Control API (#8005, #8008, #8009, #8018, #8019, #8020, #8021, #8023, #8025, #8026, #8027, #8032)

  The HTTP Control API now reaches parity coverage with its gRPC counterpart. A new ControlHttpClient supports the existing endpoints, authentication, and bounded streaming error responses, while CLI error and log paths are prepared for a future HTTP transport switch; the CLI continues to use gRPC in this release.

• Find, run, and publish AgentApps (#7928, #7929, #7930, #7988, #8000, #8002, #8031)

  Updated Flower Agent guidance explains how to discover apps in Flower Hub, run them locally or on SuperGrid, use Ollama or the OpenAI SDK, and publish frontend-visible output with agent.events.emit(...). The agent template demonstrates streaming through /v1/runtime/responses, and queued events are drained before the publisher shuts down.

• Use consistent Runtime API address options (#8010, #8011, #8012, #8014, #8029, #8050)

  Task-process commands now require --runtime-api-address instead of --clientappio-api-address or --serverappio-api-address. Custom task-process launch configurations must be updated. flower-superexec continues to accept its former --appio-api-address option as a deprecated alias.

• Fix sending shared reply objects reliably from SuperNodes (#8033)

  SuperNodes now deduplicate content-addressed objects before uploading a reply, preventing shared descendants in an ObjectTree from triggering duplicate push requests and leaving reply objects unavailable to the ServerApp.

• General improvements (#7996, #7998, #8004, #8013, #8016, #8034, #8038, #8039, #8041, #8042, #8043, #8044)

  As always, many parts of the Flower framework and quality infrastructure were improved and updated.