Skip to content

Quarkus Flow 1.0.0 released - #2914

Open
ricardozanini wants to merge 1 commit into
quarkusio:mainfrom
ricardozanini:announce-quarkus-flow-1-0-0
Open

Quarkus Flow 1.0.0 released#2914
ricardozanini wants to merge 1 commit into
quarkusio:mainfrom
ricardozanini:announce-quarkus-flow-1-0-0

Conversation

@ricardozanini

Copy link
Copy Markdown

Blog post announcing the first stable release of Quarkus Flow, a lightweight workflow engine for Quarkus based on the Open Workflow Specification (CNCF sandbox project).

Also adds the author entry for ricardozanini.

Copilot AI lite review requested due to automatic review settings August 21, 2026 19:58

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Announces Quarkus Flow 1.0.0 and adds Ricardo Zanini as an author.

Changes:

  • Adds a detailed Quarkus Flow release post.
  • Adds Ricardo Zanini’s author metadata.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File Summary
_posts/2026-08-21-quarkus-flow-1-0-0-released.adoc Critical issue (2 votes): the dependency example requires the Flow BOM or an explicit 1.0.0 version.
_data/authors.yaml Critical issue (3 votes): the new author key is concatenated to the previous scalar, making the YAML invalid; insert a newline.
Suppressed comments (2)

_posts/2026-08-21-quarkus-flow-1-0-0-released.adoc:86

  • The 1.0.0 messaging guide requires enabling the Flow bridge (quarkus.flow.messaging.defaults-enabled=true) and configuring the mp.messaging.* channels in production; having a Kafka or AMQP connector already configured is not sufficient for these tasks to work. Please qualify this sentence so readers do not expect emit/listen to work without that setup.
Quarkus Flow integrates with SmallRye Reactive Messaging out of the box. Workflows can emit and consume CloudEvents through any supported connector (Kafka, AMQP, and others), with no extra configuration beyond what you already have in your Quarkus app.

_posts/2026-08-21-quarkus-flow-1-0-0-released.adoc:52

  • set(Map.of(...)) is the map/literal overload, so ${ .name } is stored as text rather than evaluated. The Java example therefore does not produce the same greeting as the YAML example. Use the string/JQ overload here (or remove the interpolation and make the example explicitly literal).
                .tasks(set(Map.of("message", "Hello, ${ .name }!"))) // or you can use a jq string expression like in the YAML example

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread _data/authors.yaml Outdated
Comment thread _posts/2026-08-21-quarkus-flow-1-0-0-released.adoc Outdated
Add blog post and author entry for ricardozanini.

Signed-off-by: Ricardo Zanini <ricardozanini@gmail.com>
@ricardozanini
ricardozanini force-pushed the announce-quarkus-flow-1-0-0 branch from 5586d49 to 82f46cd Compare August 22, 2026 01:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants