rasa-pro 3.9.18__tar.gz → 3.10.3__tar.gz

{rasa_pro-3.9.18 → rasa_pro-3.10.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: rasa-pro
-Version: 3.9.18
+Version: 3.10.3
 Summary: State-of-the-art open-core Conversational AI framework for Enterprises that natively leverages generative AI for effortless assistant development.
 Home-page: https://rasa.com
 Keywords: nlp,machine-learning,machine-learning-library,bot,bots,botkit,rasa conversational-agents,conversational-ai,chatbot,chatbot-framework,bot-framework
@@ -19,6 +19,7 @@ Provides-Extra: full
 Provides-Extra: gh-release-notes
 Provides-Extra: jieba
 Provides-Extra: metal
+Provides-Extra: mlflow
 Provides-Extra: spacy
 Provides-Extra: transformers
 Requires-Dist: CacheControl (>=0.12.14,<0.13.0)
@@ -31,8 +32,9 @@ Requires-Dist: aiohttp (>=3.9.4,<3.10)
 Requires-Dist: apscheduler (>=3.10,<3.11)
 Requires-Dist: attrs (>=23.1,<23.2)
 Requires-Dist: azure-storage-blob (>=12.16.0,<12.17.0)
-Requires-Dist: boto3 (>=1.27.1,<2.0.0)
+Requires-Dist: boto3 (>=1.35.5,<1.36.0)
 Requires-Dist: certifi (>=2024.2.2)
+Requires-Dist: cloudpickle (>=2.2.1,<3.1)
 Requires-Dist: colorama (>=0.4.6,<0.5.0) ; sys_platform == "win32"
 Requires-Dist: colorclass (>=2.2,<2.3)
 Requires-Dist: coloredlogs (>=15,<16)
@@ -41,9 +43,10 @@ Requires-Dist: confluent-kafka (>=2.3.0,<3.0.0)
 Requires-Dist: cryptography (>=42.0.5)
 Requires-Dist: cvg-python-sdk (>=0.5.1,<0.6.0)
 Requires-Dist: dask (==2022.10.2) ; python_version >= "3.9" and python_version < "3.11"
+Requires-Dist: diskcache (>=5.6.3,<5.7.0)
 Requires-Dist: dnspython (==2.6.1)
 Requires-Dist: faiss-cpu (>=1.7.4,<2.0.0)
-Requires-Dist: faker (>=19.13.0,<20.0.0)
+Requires-Dist: faker (>=26.0.0,<27.0.0)
 Requires-Dist: fbmessenger (>=6.0.0,<6.1.0)
 Requires-Dist: github3.py (>=3.2.0,<3.3.0) ; extra == "gh-release-notes"
 Requires-Dist: google-auth (>=2.23.4,<3)
@@ -53,26 +56,31 @@ Requires-Dist: importlib-metadata (>=6.8.0,<7.0.0)
 Requires-Dist: importlib-resources (>=6.1.1,<7.0.0)
 Requires-Dist: jieba (>=0.42.1,<0.43) ; extra == "jieba" or extra == "full"
 Requires-Dist: jinja2 (>=3.1.4,<4.0.0)
+Requires-Dist: joblib (>=1.2.0,<1.3.0)
 Requires-Dist: jsonpatch (>=1.33,<2.0)
-Requires-Dist: jsonpickle (>=3.3.0,<3.4)
-Requires-Dist: jsonschema (>=4.20,<4.21)
+Requires-Dist: jsonpickle (>=3.0,<3.1)
+Requires-Dist: jsonschema (>=4.22)
 Requires-Dist: keras (==2.14.0)
-Requires-Dist: langchain (>=0.0.329,<0.0.330)
+Requires-Dist: langchain (>=0.2.0,<0.3.0)
+Requires-Dist: langchain-community (>=0.2.0,<0.3.0)
+Requires-Dist: litellm (>=1.44.7,<1.45.0)
 Requires-Dist: matplotlib (>=3.7,<3.8)
 Requires-Dist: mattermostwrapper (>=2.2,<2.3)
+Requires-Dist: mlflow (>=2.15.1,<3.0.0) ; extra == "mlflow"
 Requires-Dist: networkx (>=3.1,<3.2)
 Requires-Dist: numpy (>=1.23.5,<1.25.0) ; python_version >= "3.9" and python_version < "3.11"
-Requires-Dist: openai (>=0.28.1,<0.29.0)
+Requires-Dist: openai (>=1.40.0,<1.41.0)
+Requires-Dist: openpyxl (>=3.1.5,<4.0.0)
 Requires-Dist: opentelemetry-api (>=1.16.0,<1.17.0)
 Requires-Dist: opentelemetry-exporter-jaeger (>=1.16.0,<1.17.0)
 Requires-Dist: opentelemetry-exporter-otlp (>=1.16.0,<1.17.0)
 Requires-Dist: opentelemetry-sdk (>=1.16.0,<1.17.0)
-Requires-Dist: packaging (>=21.3,<21.4)
+Requires-Dist: packaging (>=23.2,<23.3)
 Requires-Dist: pep440-version-utils (>=1.1.0,<1.2.0)
 Requires-Dist: pluggy (>=1.2.0,<2.0.0)
 Requires-Dist: portalocker (>=2.7.0,<3.0.0)
 Requires-Dist: presidio-analyzer (>=2.2.33,<2.2.34)
-Requires-Dist: presidio-anonymizer (>=2.2.33,<2.2.34)
+Requires-Dist: presidio-anonymizer (>=2.2.354,<3.0.0)
 Requires-Dist: prompt-toolkit (>=3.0.28,<3.0.29)
 Requires-Dist: protobuf (>=4.23.3,<4.25.4)
 Requires-Dist: psutil (>=5.9.5,<6.0.0)
@@ -81,27 +89,26 @@ Requires-Dist: pycountry (>=22.3.5,<23.0.0)
 Requires-Dist: pydantic (>=2.0,<3.0)
 Requires-Dist: pydot (>=1.4,<1.5)
 Requires-Dist: pykwalify (>=1.8,<1.9)
-Requires-Dist: pymilvus (>=2.3.6,<3.0.0)
+Requires-Dist: pymilvus (<2.4.2)
 Requires-Dist: pymongo[srv,tls] (>=4.6.3,<4.7)
 Requires-Dist: pypred (>=0.4.0,<0.5.0)
 Requires-Dist: python-dateutil (>=2.8.2,<2.9.0)
 Requires-Dist: python-dotenv (>=1.0.1,<2.0.0)
 Requires-Dist: python-engineio (>=4.5.1,<6,!=5.0.0)
-Requires-Dist: python-keycloak (>=3.7.0,<4.0.0)
+Requires-Dist: python-keycloak (>=3.12.0,<4.0.0)
 Requires-Dist: python-socketio (>=5.8,<6)
 Requires-Dist: pytz (>=2022.7.1,<2023.0)
 Requires-Dist: pyyaml (>=6.0)
 Requires-Dist: qdrant-client (>=1.9.0,<2.0.0)
 Requires-Dist: questionary (>=1.10.0,<2.1.0)
 Requires-Dist: randomname (>=0.2.1,<0.3.0)
-Requires-Dist: rasa-sdk (==3.9.1)
+Requires-Dist: rasa-sdk (==3.10.0)
 Requires-Dist: redis (>=4.6.0,<6.0)
 Requires-Dist: regex (>=2022.10.31,<2022.11)
 Requires-Dist: requests (>=2.31.0,<2.32.0)
 Requires-Dist: rich (>=13.4.2,<14.0.0)
 Requires-Dist: rocketchat_API (>=1.30.0,<1.31.0)
 Requires-Dist: ruamel.yaml (>=0.17.21,<0.17.22)
-Requires-Dist: safetensors (>=0.4.5,<0.5.0)
 Requires-Dist: sanic (>=22.12,<22.13)
 Requires-Dist: sanic-cors (>=2.2.0,<2.3.0)
 Requires-Dist: sanic-jwt (>=1.8.0,<2.0.0)
@@ -112,7 +119,6 @@ Requires-Dist: sentencepiece[sentencepiece] (>=0.1.99,<0.2.0) ; extra == "transf
 Requires-Dist: sentry-sdk (>=1.14.0,<1.15.0)
 Requires-Dist: setuptools (>=70.0.0,<70.1.0)
 Requires-Dist: sklearn-crfsuite (>=0.3.6,<0.4.0)
-Requires-Dist: skops (>=0.10.0,<0.11.0)
 Requires-Dist: slack-sdk (>=3.27.1,<4.0.0)
 Requires-Dist: spacy (>=3.5.4,<4.0.0) ; extra == "spacy" or extra == "full"
 Requires-Dist: structlog (>=23.1.0,<23.2.0)
@@ -130,7 +136,7 @@ Requires-Dist: tensorflow-metal (==1.1.0) ; (sys_platform == "darwin" and platfo
 Requires-Dist: tensorflow-text (==2.14.0) ; sys_platform != "win32" and (platform_machine != "arm64" and platform_machine != "aarch64")
 Requires-Dist: tensorflow_hub (>=0.13.0,<0.14.0)
 Requires-Dist: terminaltables (>=3.1.10,<3.2.0)
-Requires-Dist: tiktoken (>=0.4.0,<0.5.0)
+Requires-Dist: tiktoken (>=0.7.0,<0.8.0)
 Requires-Dist: tqdm (>=4.66.2,<5.0.0)
 Requires-Dist: transformers (>=4.36.2,<4.37.0) ; extra == "transformers" or extra == "full"
 Requires-Dist: twilio (>=8.4,<8.5)
@@ -157,35 +163,39 @@ Description-Content-Type: text/markdown
 
 <hr />
 
+<img align="right" height="255" src="https://www.rasa.com/assets/img/sara/sara-open-source-2.0.png" alt="An image of Sara, the Rasa mascot bird, holding a flag that reads Open Source with one wing, and a wrench in the other" title="Rasa Pro">
 
-Rasa Pro is a framework for building scalable, dynamic conversational AI assistants that integrate large language models (LLMs) to enable more contextually aware and agentic interactions. Whether you’re new to conversational AI or an experienced developer, Rasa Pro offers enhanced flexibility, control, and performance for mission-critical applications.
+Rasa Pro is an open core product that extends Rasa Open Source. With over 50 million downloads, Rasa Open Source is the most popular open source framework for building chat and voice-based AI assistants.
 
-Building on the foundation of Rasa Open Source, Rasa Pro adds advanced features like CALM (Conversational AI with Language Models) and Dialogue Understanding (DU), which enable developers to shift from traditional intent-driven systems to LLM-based agents. This allows for more robust, responsive interactions that adhere strictly to business logic, while reducing risks like prompt injection and minimizing hallucinations.
+Rasa Pro introduces CALM, a generative AI-native approach to developing assistants, combined with enterprise-ready analytics, security, and observability capabilities. A paid license is required to run Rasa Pro, but all Rasa Pro code is visible to end users and can be customized as needed.
 
-**Key Features:**
+Rasa Pro is the pro-code component of our enterprise solution, Rasa Platform, for implementing resilient and trustworthy AI assistants at scale. Rasa Studio complements Rasa Pro with a low-code user interface, enabling anyone on your team to create and improve your assistant.
 
-- **Flows for Business Logic:** Easily define business logic through Flows, a simplified way to describe how your AI assistant should handle conversations. Flows help streamline the development process, focusing on key tasks and reducing the complexity involved in managing conversations.
-- **Automatic Conversation Repair:** Ensure seamless interactions by automatically handling interruptions or unexpected inputs. Developers have full control to customize these repairs based on specific use cases.
-- **Customizable and Open:** Fully customizable code that allows developers to modify Rasa Pro to meet specific requirements, ensuring flexibility and adaptability to various conversational AI needs.
-- **Robustness and Control:** Maintain strict adherence to business logic, preventing unwanted behaviors like prompt injection and hallucinations, leading to more reliable responses and secure interactions.
-- **Built-in Security:** Safeguard sensitive data, control access, and ensure secure deployment, essential for production environments that demand high levels of security and compliance.
+---
+- 🤓 [Read The Docs](https://rasa.com/docs/rasa-pro/)
 
+- 😁 [Install Rasa Pro](https://rasa.com/docs/rasa-pro/installation/python/installation)
 
+---
 
-A [free developer license](https://rasa.com/docs/rasa-pro/developer-edition/) is available so you can explore and get to know Rasa Pro. For small production deployments, the Extended Developer License allows you to take your assistant live in a limited capacity. A paid license is required for larger-scale production use, but all code is visible and can be customized as needed.
+## README Contents:
+- [Development Internals](#development-internals)
+- [Releases](#releases)
+- [Troubleshooting](#troubleshooting)
 
-To get started right now, you can 
+## Development Internals
 
-`pip install rasa-pro` 
+### Installing Poetry
 
-Check out our 
+Rasa uses Poetry for packaging and dependency management. If you want to build it from source,
+you have to install Poetry first. Please follow
+[the official guide](https://python-poetry.org/docs/#installation) to see all possible options.
 
-- [Rasa-pro Quickstart](https://rasa.com/docs/rasa-pro/installation/quickstart/),
-- [Conversational AI with Language Models (CALM) conceptual rundown](https://rasa.com/docs/rasa-pro/calm/),
-- [Rasa Pro / CALM tutorial](https://rasa.com/docs/rasa-pro/tutorial), and
-- [Rasa pro changelog](https://rasa.com/docs/rasa/rasa-pro-changelog/)
+To update an existing poetry version to the [version](.github/poetry_version.txt), currently used in rasa, run:
+```shell
+    poetry self update <version>
+```
 
-<<<<<<< HEAD
 ### Managing environments
 
 The official [Poetry guide](https://python-poetry.org/docs/managing-environments/) suggests to use
@@ -379,39 +389,6 @@ To check the types execute
 make types
 ```
 
-### Backporting
-
-In order to port changes to `main` and across release branches, we use the `backport` workflow located at
-the `.github/workflows/backport.yml` path.
-This workflow is triggered by the `backport-to-<release-branch>` label applied to a PR, for example `backport-to-3.8.x`.
-Current available target branches are `main` and maintained release branches.
-
-When a PR gets labelled `backport-to-<release-branch>`, a PR is opened by the `backport-github-action` as soon as the
-source PR gets closed (by merging). If you want to close the PR without merging changes, make sure to remove the `backport-to-<release-branch>` label.
-
-The PR author which the action assigns to the backporting PR has to resolve any conflicts before approving and merging.
-Release PRs should also be labelled with `backport-to-main` to backport the `CHANGELOG.md` updates to `main`.
-Backporting version updates should be accepted to the `main` branch from the latest release branch only.
-
-Here are some guidelines to follow when backporting changes and resolving conflicts:
-
-a) for conflicts in `version.py`: accept only the version from the latest release branch. Do not merge version changes
-from earlier release branches into `main` because this could cause issues when trying to make the next minor release.
-
-b) for conflicts in `pyproject.toml`: if related to the `rasa-pro` version, accept only the latest release branch; 
-if related to other dependencies, accept `main` or whichever is the higher upgrade (main usually has the updated 
-dependencies because we only do housekeeping on `main`, apart from vulnerability updates). Be mindful of dependencies that
-are removed from `main` but still exist in former release branches (for example `langchain`).
-
-c) for conflicts in `poetry.lock`: accept changes which were already present on the target branch, then run
-`poetry lock --no-update` so that the lock file contains your changes from `pyproject.toml` too.
-
-d) for conflicts in `CHANGELOG.md`: Manually place the changelog in their allocated section (e.g. 3.8.10 will go under the 
-3.8 section with the other releases, rather than go at the top of the file)
-
-If the backporting workflow fails, you are encouraged to cherry-pick the commits manually and create a PR to
-the target branch. Alternatively, you can install the backporting CLI tool as described [here](https://github.com/sorenlouv/backport?tab=readme-ov-file#install).
-
 ## Releases
 Rasa has implemented robust policies governing version naming, as well as release pace for major, minor, and patch releases.
 
@@ -494,12 +471,9 @@ Releasing a new version is quite simple, as the packages are build and distribut
 9. If however an error occurs in the build, then we should see a failure message automatically posted in the company's Slack (`dev-tribe` channel) like this [one](https://rasa-hq.slack.com/archives/C01M5TAHDHA/p1701444735622919)
    (In this case do the following checks):
     - Check the workflows in [Github Actions](https://github.com/RasaHQ/rasa-private/actions) and make sure that the merged PR of the current release is completed successfully. To easily find your PR you can use the filters `event: push` and `branch: <version number>` (example on release 2.4 you can see [here](https://github.com/RasaHQ/rasa/actions/runs/643344876))
-    - If the workflow is not completed, then try to re-run the workflow in case that solves the problem
+    - If the workflow is not completed, then try to re run the workflow in case that solves the problem
     - If the problem persists, check also the log files and try to find the root cause of the issue
     - If you still cannot resolve the error, contact the infrastructure team by providing any helpful information from your investigation
-10. If the release is successful, add the newly created release branch to the backporting configuration in the `.backportrc.json` file to
-the `targetBranchesChoices` list. This is necessary for the backporting workflow to work correctly with new release branches.
-
 
 ### Cutting a Patch release
 
@@ -548,6 +522,10 @@ steps.
 
 Please refer to the [Rasa Product Release and Maintenance Policy](https://rasa.com/rasa-product-release-and-maintenance-policy/) page.
 
+### Active workflows on the CI
+
+Please refer to the [WORKFLOW_README FILE](https://github.com/RasaHQ/rasa-private/blob/main/WORKFLOW_README.md)
+
 ## Troubleshooting
 
 - When running docker commands, if you encounter this error: `OSError No space left on device`, consider running:
@@ -557,7 +535,4 @@ Please refer to the [Rasa Product Release and Maintenance Policy](https://rasa.c
   ```
 
   For more information on this command, please see the [Official Docker Documentation](https://docs.docker.com/engine/reference/commandline/system_prune/).
-=======
-for more. Also feel free to reach out to us on the [Rasa forum](https://forum.rasa.com/).
->>>>>>> 2c5cd7bc639 (update readme.md from main branch on 3.10.x (#1597))
 

{rasa_pro-3.9.18 → rasa_pro-3.10.3}/README.md

@@ -10,35 +10,39 @@
 
 <hr />
 
+<img align="right" height="255" src="https://www.rasa.com/assets/img/sara/sara-open-source-2.0.png" alt="An image of Sara, the Rasa mascot bird, holding a flag that reads Open Source with one wing, and a wrench in the other" title="Rasa Pro">
 
-Rasa Pro is a framework for building scalable, dynamic conversational AI assistants that integrate large language models (LLMs) to enable more contextually aware and agentic interactions. Whether you’re new to conversational AI or an experienced developer, Rasa Pro offers enhanced flexibility, control, and performance for mission-critical applications.
+Rasa Pro is an open core product that extends Rasa Open Source. With over 50 million downloads, Rasa Open Source is the most popular open source framework for building chat and voice-based AI assistants.
 
-Building on the foundation of Rasa Open Source, Rasa Pro adds advanced features like CALM (Conversational AI with Language Models) and Dialogue Understanding (DU), which enable developers to shift from traditional intent-driven systems to LLM-based agents. This allows for more robust, responsive interactions that adhere strictly to business logic, while reducing risks like prompt injection and minimizing hallucinations.
+Rasa Pro introduces CALM, a generative AI-native approach to developing assistants, combined with enterprise-ready analytics, security, and observability capabilities. A paid license is required to run Rasa Pro, but all Rasa Pro code is visible to end users and can be customized as needed.
 
-**Key Features:**
+Rasa Pro is the pro-code component of our enterprise solution, Rasa Platform, for implementing resilient and trustworthy AI assistants at scale. Rasa Studio complements Rasa Pro with a low-code user interface, enabling anyone on your team to create and improve your assistant.
 
-- **Flows for Business Logic:** Easily define business logic through Flows, a simplified way to describe how your AI assistant should handle conversations. Flows help streamline the development process, focusing on key tasks and reducing the complexity involved in managing conversations.
-- **Automatic Conversation Repair:** Ensure seamless interactions by automatically handling interruptions or unexpected inputs. Developers have full control to customize these repairs based on specific use cases.
-- **Customizable and Open:** Fully customizable code that allows developers to modify Rasa Pro to meet specific requirements, ensuring flexibility and adaptability to various conversational AI needs.
-- **Robustness and Control:** Maintain strict adherence to business logic, preventing unwanted behaviors like prompt injection and hallucinations, leading to more reliable responses and secure interactions.
-- **Built-in Security:** Safeguard sensitive data, control access, and ensure secure deployment, essential for production environments that demand high levels of security and compliance.
+---
+- 🤓 [Read The Docs](https://rasa.com/docs/rasa-pro/)
 
+- 😁 [Install Rasa Pro](https://rasa.com/docs/rasa-pro/installation/python/installation)
 
+---
 
-A [free developer license](https://rasa.com/docs/rasa-pro/developer-edition/) is available so you can explore and get to know Rasa Pro. For small production deployments, the Extended Developer License allows you to take your assistant live in a limited capacity. A paid license is required for larger-scale production use, but all code is visible and can be customized as needed.
+## README Contents:
+- [Development Internals](#development-internals)
+- [Releases](#releases)
+- [Troubleshooting](#troubleshooting)
 
-To get started right now, you can 
+## Development Internals
 
-`pip install rasa-pro` 
+### Installing Poetry
 
-Check out our 
+Rasa uses Poetry for packaging and dependency management. If you want to build it from source,
+you have to install Poetry first. Please follow
+[the official guide](https://python-poetry.org/docs/#installation) to see all possible options.
 
-- [Rasa-pro Quickstart](https://rasa.com/docs/rasa-pro/installation/quickstart/),
-- [Conversational AI with Language Models (CALM) conceptual rundown](https://rasa.com/docs/rasa-pro/calm/),
-- [Rasa Pro / CALM tutorial](https://rasa.com/docs/rasa-pro/tutorial), and
-- [Rasa pro changelog](https://rasa.com/docs/rasa/rasa-pro-changelog/)
+To update an existing poetry version to the [version](.github/poetry_version.txt), currently used in rasa, run:
+```shell
+    poetry self update <version>
+```
 
-<<<<<<< HEAD
 ### Managing environments
 
 The official [Poetry guide](https://python-poetry.org/docs/managing-environments/) suggests to use
@@ -232,39 +236,6 @@ To check the types execute
 make types
 ```
 
-### Backporting
-
-In order to port changes to `main` and across release branches, we use the `backport` workflow located at
-the `.github/workflows/backport.yml` path.
-This workflow is triggered by the `backport-to-<release-branch>` label applied to a PR, for example `backport-to-3.8.x`.
-Current available target branches are `main` and maintained release branches.
-
-When a PR gets labelled `backport-to-<release-branch>`, a PR is opened by the `backport-github-action` as soon as the
-source PR gets closed (by merging). If you want to close the PR without merging changes, make sure to remove the `backport-to-<release-branch>` label.
-
-The PR author which the action assigns to the backporting PR has to resolve any conflicts before approving and merging.
-Release PRs should also be labelled with `backport-to-main` to backport the `CHANGELOG.md` updates to `main`.
-Backporting version updates should be accepted to the `main` branch from the latest release branch only.
-
-Here are some guidelines to follow when backporting changes and resolving conflicts:
-
-a) for conflicts in `version.py`: accept only the version from the latest release branch. Do not merge version changes
-from earlier release branches into `main` because this could cause issues when trying to make the next minor release.
-
-b) for conflicts in `pyproject.toml`: if related to the `rasa-pro` version, accept only the latest release branch; 
-if related to other dependencies, accept `main` or whichever is the higher upgrade (main usually has the updated 
-dependencies because we only do housekeeping on `main`, apart from vulnerability updates). Be mindful of dependencies that
-are removed from `main` but still exist in former release branches (for example `langchain`).
-
-c) for conflicts in `poetry.lock`: accept changes which were already present on the target branch, then run
-`poetry lock --no-update` so that the lock file contains your changes from `pyproject.toml` too.
-
-d) for conflicts in `CHANGELOG.md`: Manually place the changelog in their allocated section (e.g. 3.8.10 will go under the 
-3.8 section with the other releases, rather than go at the top of the file)
-
-If the backporting workflow fails, you are encouraged to cherry-pick the commits manually and create a PR to
-the target branch. Alternatively, you can install the backporting CLI tool as described [here](https://github.com/sorenlouv/backport?tab=readme-ov-file#install).
-
 ## Releases
 Rasa has implemented robust policies governing version naming, as well as release pace for major, minor, and patch releases.
 
@@ -347,12 +318,9 @@ Releasing a new version is quite simple, as the packages are build and distribut
 9. If however an error occurs in the build, then we should see a failure message automatically posted in the company's Slack (`dev-tribe` channel) like this [one](https://rasa-hq.slack.com/archives/C01M5TAHDHA/p1701444735622919)
    (In this case do the following checks):
     - Check the workflows in [Github Actions](https://github.com/RasaHQ/rasa-private/actions) and make sure that the merged PR of the current release is completed successfully. To easily find your PR you can use the filters `event: push` and `branch: <version number>` (example on release 2.4 you can see [here](https://github.com/RasaHQ/rasa/actions/runs/643344876))
-    - If the workflow is not completed, then try to re-run the workflow in case that solves the problem
+    - If the workflow is not completed, then try to re run the workflow in case that solves the problem
     - If the problem persists, check also the log files and try to find the root cause of the issue
     - If you still cannot resolve the error, contact the infrastructure team by providing any helpful information from your investigation
-10. If the release is successful, add the newly created release branch to the backporting configuration in the `.backportrc.json` file to
-the `targetBranchesChoices` list. This is necessary for the backporting workflow to work correctly with new release branches.
-
 
 ### Cutting a Patch release
 
@@ -401,6 +369,10 @@ steps.
 
 Please refer to the [Rasa Product Release and Maintenance Policy](https://rasa.com/rasa-product-release-and-maintenance-policy/) page.
 
+### Active workflows on the CI
+
+Please refer to the [WORKFLOW_README FILE](https://github.com/RasaHQ/rasa-private/blob/main/WORKFLOW_README.md)
+
 ## Troubleshooting
 
 - When running docker commands, if you encounter this error: `OSError No space left on device`, consider running:
@@ -410,6 +382,3 @@ Please refer to the [Rasa Product Release and Maintenance Policy](https://rasa.c
   ```
 
   For more information on this command, please see the [Official Docker Documentation](https://docs.docker.com/engine/reference/commandline/system_prune/).
-=======
-for more. Also feel free to reach out to us on the [Rasa forum](https://forum.rasa.com/).
->>>>>>> 2c5cd7bc639 (update readme.md from main branch on 3.10.x (#1597))

{rasa_pro-3.9.18 → rasa_pro-3.10.3}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "poetry.core.masonry.api"
 
 [tool.poetry]
 name = "rasa-pro"
-version = "3.9.18"
+version = "3.10.3"
 description = "State-of-the-art open-core Conversational AI framework for Enterprises that natively leverages generative AI for effortless assistant development."
 authors = [ "Rasa Technologies GmbH <hi@rasa.com>",]
 maintainers = [ "Tom Bocklisch <tom@rasa.com>",]
@@ -88,13 +88,13 @@ exclude = [ "eggs", ".git", ".pytest_cache", "build", "dist",]
 
 [tool.poetry.dependencies]
 python = ">=3.9,<3.11"
-boto3 = "^1.27.1"
+boto3 = "~1.35.5"
 google-cloud-storage = "^2.14.0"
 azure-storage-blob = ">=12.16.0, <12.17.0"
 requests = "~2.31.0"
 matplotlib = ">=3.7,<3.8"
 attrs = ">=23.1,<23.2"
-jsonpickle = ">=3.3.0,<3.4"
+jsonpickle = ">=3.0,<3.1"
 redis = ">=4.6.0, <6.0"
 absl-py = ">=2.0,<2.1"
 apscheduler = ">=3.10,<3.11"
@@ -110,8 +110,8 @@ webexteamssdk = ">=1.6.1,<1.7.0"
 mattermostwrapper = "~2.2"
 rocketchat_API = ">=1.30.0,<1.31.0"
 colorhash = ">=2.0,<2.1.0"
-jsonschema = ">=4.20,<4.21"
-packaging = "~21.3"
+jsonschema = ">=4.22"
+packaging = "~23.2"
 pytz = ">=2022.7.1,<2023.0"
 colorclass = "~2.2"
 terminaltables = "~3.1.10"
@@ -120,6 +120,7 @@ sanic-cors = "~2.2.0"
 sanic-jwt = "^1.8.0"
 sanic-routing = "^22.8.0"
 websockets = ">=10.4,<11.0"
+cloudpickle = ">=2.2.1,<3.1"
 aiohttp = ">=3.9.4,<3.10"
 questionary = ">=1.10.0,<2.1.0"
 prompt-toolkit = "^3.0.28,<3.0.29"
@@ -135,6 +136,7 @@ tensorflow_hub = "^0.13.0"
 setuptools = "~70.0.0"
 ujson = ">=5.8,<6.0"
 regex = ">=2022.10.31,<2022.11"
+joblib = ">=1.2.0,<1.3.0"
 sentry-sdk = ">=1.14.0,<1.15.0"
 aio-pika = ">=8.2.3,<8.2.4"
 aiogram = ">=2.15,<2.26"
@@ -151,9 +153,10 @@ portalocker = "^2.7.0"
 pypred = "^0.4.0"
 structlog = ">=23.1.0,<23.2.0"
 structlog-sentry = "^2.0.3"
-langchain = "^0.0.329"
+langchain = "~0.2.0"
+langchain-community = "~0.2.0"
 jinja2 = "^3.1.4"
-openai = "^0.28.1"
+openai = "~1.40.0"
 dnspython = "2.6.1"
 wheel = ">=0.40.0"
 certifi = ">=2024.2.2"
@@ -171,19 +174,20 @@ hvac = "^1.2.1"
 rich = "^13.4.2"
 cvg-python-sdk = "^0.5.1"
 presidio-analyzer = "^2.2.33, <2.2.34"
-presidio-anonymizer = "^2.2.33, <2.2.34"
-faker = "^19.13.0"
-python-keycloak = "^3.7.0"
-tiktoken = "^0.4.0"
+presidio-anonymizer = "^2.2.354"
+faker = "^26.0.0"
+python-keycloak = "^3.12.0"
+tiktoken = "~0.7.0"
 faiss-cpu = "^1.7.4"
 pycountry = "^22.3.5"
-pymilvus = "^2.3.6"
+pymilvus = "<2.4.2" # pinned because 2.4.2 introduces milvus-lite dependency that fails on windows
 qdrant-client = "^1.9.0"
 psutil = "^5.9.5"
-tenacity = "~8.4.1"
+tenacity = "~8.4.1" # pinned down because of langchain
 types-protobuf = "4.25.0.20240417"
-skops = "~0.10.0"
-safetensors = "~0.4.5"
+litellm = "~1.44.7"
+openpyxl = "^3.1.5"
+diskcache = "~5.6.3"
 [[tool.poetry.dependencies.tensorflow-io-gcs-filesystem]]
 version = "==0.31" # newer versions doesn't provide wheels for Windows
 markers = "sys_platform == 'win32'"
@@ -220,6 +224,10 @@ optional = true
 version = "^2.0"
 optional = true
 
+[[tool.poetry.dependencies.mlflow]]
+version = "^2.15.1"
+optional = true
+
 [tool.poetry.extras]
 spacy = [ "spacy",]
 jieba = [ "jieba",]
@@ -227,11 +235,26 @@ transformers = [ "transformers", "sentencepiece",]
 full = [ "spacy", "transformers", "sentencepiece", "jieba",]
 gh-release-notes = [ "github3.py",]
 metal = [ "tensorflow-metal",]
+mlflow = [ "mlflow",]
 
 [tool.poetry.scripts]
 rasa = "rasa.__main__:main"
 
 [tool.ruff.lint]
+# The following checks are disabled because they are not relevant for Rasa
+# - RUF001: Checks for ambiguous Unicode characters in strings. https://docs.astral.sh/ruff/rules/ambiguous-unicode-character-string/
+# - RUF002: Checks for ambiguous Unicode characters in docstrings. https://docs.astral.sh/ruff/rules/ambiguous-unicode-character-docstring/
+# - RUF003: Checks for ambiguous Unicode characters in comments. https://docs.astral.sh/ruff/rules/ambiguous-unicode-character-comment/
+# - RUF005: Use of + operator for string concatenation https://docs.astral.sh/ruff/rules/collection-literal-concatenation/
+# Following checks are currently disabled but will be enabled in the future
+# as part of the ticket https://rasahq.atlassian.net/browse/ATO-866
+# - D100: Missing docstring in public module
+# - D101: Missing docstring in public class
+# - D102: Missing docstring in public method
+# - D103: Missing docstring in public function
+# - D104: Missing docstring in public package
+# - D105: Missing docstring in magic method
+# - D107: Missing docstring in __init__
 ignore = [ "D100", "D101", "D102", "D103", "D104", "D105", "D107", "RUF001", "RUF002", "RUF003", "RUF005",]
 select = [ "D", "E", "F", "W", "RUF",]
 
@@ -246,7 +269,7 @@ timeout_func_only = true
 asyncio_mode = "auto"
 
 [tool.poetry.dependencies.rasa-sdk]
-version = "3.9.1"
+version = "3.10.0"
 allow-prereleases = true
 
 [tool.poetry.dependencies.keras]
@@ -324,11 +347,11 @@ pytest-cov = "^4.0.0"
 pytest-asyncio = "^0.20.0"
 pytest-xdist = "^3.2.1"
 pytest = "^7.1.3"
-freezegun = "^1.0.0"
+freezegun = "^1.5.1"
 responses = ">=0.22,<0.25"
 aioresponses = "^0.7.2"
-moto = "~=4.1.2"
-fakeredis = "^2.11.2"
+moto = "~5.0.3"
+fakeredis = "^2.23.2"
 mongomock = "^4.1.2"
 towncrier = "^22.8.0"
 toml = "^0.10.0"
@@ -337,15 +360,14 @@ mypy = "^1.0.0"
 bandit = "^1.6.3"
 types-pytz = "^2022.1.1"
 types-python-dateutil = "^2.8.19"
-types-requests = "^2.25.0"
+types-requests = "^2.31.0"
 types-setuptools = "^68.2.0"
 memory-profiler = "^0.61.0"
 mypy-extensions = ">=0.4.3,<1.1.0"
-sanic-testing = "^22.12.0"
+sanic-testing = "~23.6.0"
 analytics-python = "^1.4.0"
-datadog-api-client = "^2.0.0"
+datadog-api-client = "^2.25.0"
 datadog = "^0.49.1"
 types-redis = "^4.3.20"
-httpx = "0.23.3"
 types-protobuf = "^4.24.0"
 types-toml = "^0.10.8.7"

{rasa_pro-3.9.18 → rasa_pro-3.10.3}/rasa/__init__.py

@@ -1,7 +1,6 @@
 import logging
 
-from rasa import version, plugin  # noqa: F401
-from rasa.api import run, train, test  # noqa: F401
+from rasa import version
 
 # define the version before the other imports since these need it
 __version__ = version.__version__

{rasa_pro-3.9.18 → rasa_pro-3.10.3}/rasa/__main__.py

@@ -25,6 +25,7 @@ from rasa.cli import (
     visualize,
     x,
     evaluate,
+    llm_fine_tuning,
 )
 from rasa.cli.arguments.default_arguments import add_logging_options
 from rasa.cli.utils import (
@@ -76,6 +77,7 @@ def create_argument_parser() -> argparse.ArgumentParser:
     export.add_subparser(subparsers, parents=parent_parsers)
     x.add_subparser(subparsers, parents=parent_parsers)
     evaluate.add_subparser(subparsers, parents=parent_parsers)
+    llm_fine_tuning.add_subparser(subparsers, parent_parsers)
     plugin_manager().hook.refine_cli(
         subparsers=subparsers, parent_parsers=parent_parsers
     )
@@ -85,12 +87,15 @@ def create_argument_parser() -> argparse.ArgumentParser:
 
 def print_version() -> None:
     """Prints version information of rasa tooling and python."""
+    from rasa.utils.licensing import get_license_expiration_date
+
     print(f"Rasa Version      :         {version.__version__}")
     print(f"Minimum Compatible Version: {MINIMUM_COMPATIBLE_VERSION}")
     print(f"Rasa SDK Version  :         {rasa_sdk_version}")
     print(f"Python Version    :         {platform.python_version()}")
     print(f"Operating System  :         {platform.platform()}")
     print(f"Python Path       :         {sys.executable}")
+    print(f"License Expires   :         {get_license_expiration_date()}")
 
 
 def main() -> None:

{rasa_pro-3.9.18 → rasa_pro-3.10.3}/rasa/anonymization/anonymization_rule_executor.py

@@ -123,7 +123,7 @@ class AnonymizationRuleExecutor:
             else None
         )
 
-        self.anonymizer_engine = AnonymizerEngine()
+        self.anonymizer_engine = AnonymizerEngine()  # type: ignore
 
     @staticmethod
     def _validate_anonymization_rule_list(
@@ -146,7 +146,7 @@ class AnonymizationRuleExecutor:
 
         return True
 
-    def run(self, text: Text) -> Text:
+    def run(self, text: Text) -> Optional[Text]:
         """Anonymizes the given text using the given anonymization rule list."""
         if (
             self.analyzer is None