3.3.8

• #12235

3.5.4

Rasa 3.5.4 (2023-04-05)

Bugfixes

• #12226: Fix issue with failures while publishing events to RabbitMQ after a RabbitMQ restart.
  The fix consists of pinning aio-pika dependency to 8.2.3, since this issue was introduced in aio-pika v8.2.4.

Miscellaneous internal changes

• #12230, #12232, #12238

3.4.9

• #12234

3.4.8

Rasa 3.4.8 (2023-04-03)

Bugfixes

• #12186: Fix issue with failures while publishing events to RabbitMQ after a RabbitMQ restart.
  The fix consists of pinning aio-pika dependency to 8.2.3, since this issue was introduced in aio-pika v8.2.4.

3.4.7

Rasa 3.4.7 (2023-03-30)

Improvements

• #12144: Add a self-reference of the synonym in the EntitySynonymMapper to handle entities extracted in a casing different to synonym case. (For example if a synonym austria is added, entities extracted with any alternate casing of the synonym will also be mapped to austria). It addresses ATO-616

Bugfixes

• #12139: Fix 2 issues detected with the HTTP API:
  • The GET /conversations/{conversation_id}/tracker endpoint was not returning the tracker with all sessions when include_events query parameter was set to ALL.
    The fix constituted in using TrackerStore.retrieve_full_tracker method instead of TrackerStore.retrieve method in the function handling the GET /conversations/{conversation_id}/tracker endpoint.
    Implemented or updated this method across all tracker store subclasses.
  • The GET /conversations/{conversation_id}/story endpoint was not returning all the stories for all sessions when all_sessions query parameter was set to true.
    The fix constituted in using all events of the tracker to be converted in stories instead of only the applied_events.
• #12189: Make custom actions inheriting from rasa-sdk FormValidationAction parent class an exception of the selective_domain rule and always send them domain.

3.3.7

• #12144: Add a self-reference of the synonym in the EntitySynonymMapper to handle entities extracted in a casing different to synonym case. (For example if a synonym austria is added, entities extracted with any alternate casing of the synonym will also be mapped to austria). It addresses ATO-616

Bugfixes

• #12187: Fix issue with failures while publishing events to RabbitMQ after a RabbitMQ restart.
  The fix consists of pinning aio-pika dependency to 8.2.3, since this issue was introduced in aio-pika v8.2.4.
• #12192: Fix 2 issues detected with the HTTP API:
  • The GET /conversations/{conversation_id}/tracker endpoint was not returning the tracker with all sessions when include_events query parameter was set to ALL.
    The fix constituted in using TrackerStore.retrieve_full_tracker method instead of TrackerStore.retrieve method in the function handling the GET /conversations/{conversation_id}/tracker endpoint.
    Implemented or updated this method across all tracker store subclasses.
  • The GET /conversations/{conversation_id}/story endpoint was not returning all the stories for all sessions when all_sessions query parameter was set to true.
    The fix constituted in using all events of the tracker to be converted in stories instead of only the applied_events.

3.5.3

Rasa 3.5.3 (2023-03-30)

Improved Documentation

• #12209: Add new Rasa Pro page in docs, together with minimal content changes.

3.5.2

Rasa 3.5.2 (2023-03-30)

Improvements

• #12144: Add a self-reference of the synonym in the EntitySynonymMapper to handle entities extracted in a casing different to synonym case. (For example if a synonym austria is added, entities extracted with any alternate casing of the synonym will also be mapped to austria). It addresses ATO-616

Bugfixes

• #12189: Make custom actions inheriting from rasa-sdk FormValidationAction parent class an exception of the selective_domain rule and always send them domain.
• #12193: Fix 2 issues detected with the HTTP API:
  • The GET /conversations/{conversation_id}/tracker endpoint was not returning the tracker with all sessions when include_events query parameter was set to ALL.
    The fix constituted in using TrackerStore.retrieve_full_tracker method instead of TrackerStore.retrieve method in the function handling the GET /conversations/{conversation_id}/tracker endpoint.
    Implemented or updated this method across all tracker store subclasses.
  • The GET /conversations/{conversation_id}/story endpoint was not returning all the stories for all sessions when all_sessions query parameter was set to true.
    The fix constituted in using all events of the tracker to be converted in stories instead of only the applied_events.

Improved Documentation

• #12110: Add documentation for secrets managers.

3.5.1

Rasa 3.5.1 (2023-03-24)

Bugfixes

• #12174: Fixes training DIETCLassifier on the GPU.

  A deterministic GPU implementation of SparseTensorDenseMatmulOp is not currently available

Improved Documentation

• #12127: Updated Test your assistant section to describe the new end-to-end testing feature.
  Also updated CLI and telemetry reference docs.
• #12169: Update Compatibility Matrix.

3.5.0

Rasa 3.5.0 (2023-03-21)

Features

• #12053: Add a new required key (assistant_id) to config.yml to uniquely identify assistants in deployment.
  The assistant identifier is extracted from the model metadata and added to the metadata of all dialogue events.
  Re-training will be required to include the assistant id in the event metadata.

  If the assistant identifier is missing from the config.yml or the default identifier value is not replaced, a random
  identifier is generated during each training.

  An assistant running without an identifier will issue a warning that dialogue events without identifier metadata will be
  streamed to the event broker.

Improvements

• #11998: Add capability to send compressed body in HTTP request to action server.
  Use COMPRESS_ACTION_SERVER_REQUEST=True to turn the feature on.

Bugfixes

• #12136: Address potentially missing events with Pika consumer due to weak references on asynchronous tasks,
  as specifcied in Python official documentation.
• #12155: Sets a global seed for numpy, TensorFlow, keras, Python and CuDNN, to ensure consistent random number generation.

Improved Documentation

• #11893: Clarify in the docs, how rules are designed and how to use this behaviour to abort a rule

Miscellaneous internal changes

• #11924, #11926, #12006, #12022, #12092, #12135, #12137, #12140, #12154