chore(release): release and bump versions of packages (#1829)

Author: asyncapi-bot

.changeset/slack-auto-routing.md

@@ -1,5 +1,71 @@
 # @asyncapi/generator
 
+## 3.1.0
+
+### Minor Changes
+
+- 11a1b8d: - **Updated Component**: `OnMessage` (Python) - Added discriminator-based routing logic that automatically dispatches messages to operation-specific handlers before falling back to generic handlers
+
+  - **New Helpers**:
+    - `getMessageDiscriminatorData` - Extracts discriminator key and value from individual messages
+    - `getMessageDiscriminatorsFromOperations` - Collects all discriminator metadata from receive operations
+  - Enhanced Python webSocket client generation with **automatic operation-based message routing**:
+
+  ## How python routing works
+
+  - Generated WebSocket clients now automatically route incoming messages to operation-specific handlers based on message discriminators. Users can register handlers for specific message types without manually parsing or filtering messages.
+  - When a message arrives, the client checks it against registered discriminators (e.g., `type: "hello"`, `type: "events_api"`)
+  - If a match is found, the message is routed to the specific operation handler (e.g., `onHelloMessage`, `onEvent`)
+  - If no match is found, the message falls back to generic message handlers
+  - This enables clean separation of message handling logic based on message types
+
+  > `discriminator` is a `string` field that you can add to any AsyncAPI Schema. This also means that it is limited to AsyncAPI Schema only, and it won't work with other schema formats, like for example, Avro.
+
+  The implementation automatically derives discriminator information from your AsyncAPI document:
+
+  - Discriminator `key` is extracted from the `discriminator` field in your AsyncAPI spec
+  - Discriminator `value` is extracted from the `const` property defined in message schemas
+
+  Example AsyncAPI Schema with `discriminator` and `const`:
+
+  ```yaml
+  schemas:
+    hello:
+      type: object
+      discriminator: type # you specify name of property
+      properties:
+        type:
+          type: string
+          const: hello # you specify the value of the discriminator property that is used for routing
+          description: A hello string confirming WebSocket connection
+  ```
+
+  ## Fallback
+
+  When defaults aren't available in the AsyncAPI document, users must provide **both** `discriminator_key` and `discriminator_value` when registering handlers. Providing only one parameter is not supported - you must provide either both or neither.
+
+  > **Why this limitation exists**: When a receive operation has multiple messages sharing the same discriminator key (e.g., all use `"type"` field), we need the specific value (e.g., `"hello"`, `"disconnect"`) to distinguish between them. Without both pieces of information, the routing becomes ambiguous.
+
+  Example:
+
+  ```python
+  # Default case - discriminator info auto-derived from AsyncAPI doc
+  client.register_on_hello_message_handler(my_handler)
+
+  # Custom case - must provide both key AND value
+  client.register_on_hello_message_handler(
+      my_handler,
+      discriminator_key="message_type",
+      discriminator_value="custom_hello"
+  )
+  ```
+
+### Patch Changes
+
+- Updated dependencies [11a1b8d]
+  - @asyncapi/generator-components@0.5.0
+  - @asyncapi/generator-helpers@1.1.0
+
 ## 3.0.1
 
 ### Patch Changes

apps/generator/CHANGELOG.md

@@ -1,6 +1,6 @@
 {
   "name": "@asyncapi/generator",
-  "version": "3.0.1",
+  "version": "3.1.0",
   "description": "The AsyncAPI generator. It can generate documentation, code, anything!",
   "main": "./lib/generator.js",
   "engines": {

apps/generator/package.json

@@ -1,5 +1,70 @@
 # @asyncapi/generator-components
 
+## 0.5.0
+
+### Minor Changes
+
+- 11a1b8d: - **Updated Component**: `OnMessage` (Python) - Added discriminator-based routing logic that automatically dispatches messages to operation-specific handlers before falling back to generic handlers
+
+  - **New Helpers**:
+    - `getMessageDiscriminatorData` - Extracts discriminator key and value from individual messages
+    - `getMessageDiscriminatorsFromOperations` - Collects all discriminator metadata from receive operations
+  - Enhanced Python webSocket client generation with **automatic operation-based message routing**:
+
+  ## How python routing works
+
+  - Generated WebSocket clients now automatically route incoming messages to operation-specific handlers based on message discriminators. Users can register handlers for specific message types without manually parsing or filtering messages.
+  - When a message arrives, the client checks it against registered discriminators (e.g., `type: "hello"`, `type: "events_api"`)
+  - If a match is found, the message is routed to the specific operation handler (e.g., `onHelloMessage`, `onEvent`)
+  - If no match is found, the message falls back to generic message handlers
+  - This enables clean separation of message handling logic based on message types
+
+  > `discriminator` is a `string` field that you can add to any AsyncAPI Schema. This also means that it is limited to AsyncAPI Schema only, and it won't work with other schema formats, like for example, Avro.
+
+  The implementation automatically derives discriminator information from your AsyncAPI document:
+
+  - Discriminator `key` is extracted from the `discriminator` field in your AsyncAPI spec
+  - Discriminator `value` is extracted from the `const` property defined in message schemas
+
+  Example AsyncAPI Schema with `discriminator` and `const`:
+
+  ```yaml
+  schemas:
+    hello:
+      type: object
+      discriminator: type # you specify name of property
+      properties:
+        type:
+          type: string
+          const: hello # you specify the value of the discriminator property that is used for routing
+          description: A hello string confirming WebSocket connection
+  ```
+
+  ## Fallback
+
+  When defaults aren't available in the AsyncAPI document, users must provide **both** `discriminator_key` and `discriminator_value` when registering handlers. Providing only one parameter is not supported - you must provide either both or neither.
+
+  > **Why this limitation exists**: When a receive operation has multiple messages sharing the same discriminator key (e.g., all use `"type"` field), we need the specific value (e.g., `"hello"`, `"disconnect"`) to distinguish between them. Without both pieces of information, the routing becomes ambiguous.
+
+  Example:
+
+  ```python
+  # Default case - discriminator info auto-derived from AsyncAPI doc
+  client.register_on_hello_message_handler(my_handler)
+
+  # Custom case - must provide both key AND value
+  client.register_on_hello_message_handler(
+      my_handler,
+      discriminator_key="message_type",
+      discriminator_value="custom_hello"
+  )
+  ```
+
+### Patch Changes
+
+- Updated dependencies [11a1b8d]
+  - @asyncapi/generator-helpers@1.1.0
+
 ## 0.4.1
 
 ### Patch Changes

packages/components/CHANGELOG.md

@@ -1,6 +1,6 @@
 {
   "name": "@asyncapi/generator-components",
-  "version": "0.4.1",
+  "version": "0.5.0",
   "description": "Package with reusable components for generation using React render engine",
   "scripts": {
     "test": "npm run build && jest --coverage",

packages/components/package.json

@@ -1,5 +1,65 @@
 # @asyncapi/generator-helpers
 
+## 1.1.0
+
+### Minor Changes
+
+- 11a1b8d: - **Updated Component**: `OnMessage` (Python) - Added discriminator-based routing logic that automatically dispatches messages to operation-specific handlers before falling back to generic handlers
+
+  - **New Helpers**:
+    - `getMessageDiscriminatorData` - Extracts discriminator key and value from individual messages
+    - `getMessageDiscriminatorsFromOperations` - Collects all discriminator metadata from receive operations
+  - Enhanced Python webSocket client generation with **automatic operation-based message routing**:
+
+  ## How python routing works
+
+  - Generated WebSocket clients now automatically route incoming messages to operation-specific handlers based on message discriminators. Users can register handlers for specific message types without manually parsing or filtering messages.
+  - When a message arrives, the client checks it against registered discriminators (e.g., `type: "hello"`, `type: "events_api"`)
+  - If a match is found, the message is routed to the specific operation handler (e.g., `onHelloMessage`, `onEvent`)
+  - If no match is found, the message falls back to generic message handlers
+  - This enables clean separation of message handling logic based on message types
+
+  > `discriminator` is a `string` field that you can add to any AsyncAPI Schema. This also means that it is limited to AsyncAPI Schema only, and it won't work with other schema formats, like for example, Avro.
+
+  The implementation automatically derives discriminator information from your AsyncAPI document:
+
+  - Discriminator `key` is extracted from the `discriminator` field in your AsyncAPI spec
+  - Discriminator `value` is extracted from the `const` property defined in message schemas
+
+  Example AsyncAPI Schema with `discriminator` and `const`:
+
+  ```yaml
+  schemas:
+    hello:
+      type: object
+      discriminator: type # you specify name of property
+      properties:
+        type:
+          type: string
+          const: hello # you specify the value of the discriminator property that is used for routing
+          description: A hello string confirming WebSocket connection
+  ```
+
+  ## Fallback
+
+  When defaults aren't available in the AsyncAPI document, users must provide **both** `discriminator_key` and `discriminator_value` when registering handlers. Providing only one parameter is not supported - you must provide either both or neither.
+
+  > **Why this limitation exists**: When a receive operation has multiple messages sharing the same discriminator key (e.g., all use `"type"` field), we need the specific value (e.g., `"hello"`, `"disconnect"`) to distinguish between them. Without both pieces of information, the routing becomes ambiguous.
+
+  Example:
+
+  ```python
+  # Default case - discriminator info auto-derived from AsyncAPI doc
+  client.register_on_hello_message_handler(my_handler)
+
+  # Custom case - must provide both key AND value
+  client.register_on_hello_message_handler(
+      my_handler,
+      discriminator_key="message_type",
+      discriminator_value="custom_hello"
+  )
+  ```
+
 ## 1.0.1
 
 ### Patch Changes

packages/helpers/CHANGELOG.md

@@ -1,6 +1,6 @@
 {
   "name": "@asyncapi/generator-helpers",
-  "version": "1.0.1",
+  "version": "1.1.0",
   "description": "Package with reusable helpers that make it easier to work with AsyncAPI structures.",
   "scripts": {
     "test": "jest --coverage",

packages/helpers/package.json

@@ -18,7 +18,7 @@
     "lint:fix": "eslint --fix --max-warnings 0 --config ../../../../../../.eslintrc --ignore-path ../../../../../../.eslintignore ."
   },
   "dependencies": {
-    "@asyncapi/generator-helpers": "1.0.1",
+    "@asyncapi/generator-helpers": "1.1.0",
     "@asyncapi/generator-react-sdk": "^1.1.2"
   },
   "devDependencies": {

packages/templates/clients/kafka/java/quarkus/package.json

@@ -12,8 +12,8 @@
   "license": "Apache-2.0",
   "dependencies": {
     "@asyncapi/generator-react-sdk": "*",
-    "@asyncapi/generator-helpers": "1.0.1",
-    "@asyncapi/generator-components": "0.4.1"
+    "@asyncapi/generator-helpers": "1.1.0",
+    "@asyncapi/generator-components": "0.5.0"
   },
   "devDependencies": {
     "@asyncapi/parser": "^3.4.0",

packages/templates/clients/websocket/dart/package.json

@@ -18,8 +18,8 @@
     "lint:fix": "eslint --fix --max-warnings 0 --config ../../../../../../.eslintrc --ignore-path ../../../../../../.eslintignore ."
   },
   "dependencies": {
-    "@asyncapi/generator-helpers": "1.0.1",
-    "@asyncapi/generator-components": "0.4.1",
+    "@asyncapi/generator-helpers": "1.1.0",
+    "@asyncapi/generator-components": "0.5.0",
     "@asyncapi/generator-react-sdk": "^1.1.2"
   },
   "devDependencies": {