Rasa X Changelog

Rasa X version 0.33.0 or higher is only compatible with Rasa Open Source 2.x. If you are on Rasa Open Source 1.x, please check the compatibility matrix for a compatible version.

×

SearchK

All notable changes to this project will be documented in this file. This project adheres to Semantic Versioning.

[1.1.0] - 2022-03-29 #

Deprecations and Removals #

not running Rasa Enterprise in a containerized environment.

means that project data in the following formats is now incompatible:

Please follow the steps from the migration guide for the upgrade.

Features #

Please follow the steps from the migration guide for the upgrade.

Improvements #

expensive database queries.

Bugfixes #

in a 500 error code. Improved error handling by prompting for missing keys.

the domain warnings endpoint resulted in an error.

Miscellaneous internal changes #

This change is in scope of decoupling rasa x and rasa OSS.

[1.0.1] - 2021-12-17 #

Bugfixes #

[1.0.0] - 2021-12-02 #

Deprecations and Removals #

New endpoints will be added to the public API in the future as product development advances. The documentation for the currently available endpoints can be found at https://rasa.com/docs/rasa-x/pages/http-api.

Features #

When Rasa X starts, it will attempt to create an initial administrator user. The username of this user is admin by default. This value can be controlled via the RASA_X_USERNAME environment variable. In Server mode, if one or more users already exist in the database, Rasa X will not attempt to create the initial administrator user.

When Rasa X starts, it will also attempt to ensure that the initial administrator user has a password assigned to it. Assuming that the user exists, Rasa X will do this in different ways, depending on the context:

The me user will no longer be created during startup, and users are expected to use admin instead. However, existing me users in databases will not be modified or deleted by this update.

  1. Limits GET /conversations/slotValues to max 100 values
  2. Returns X-Total-Count header on GET /conversations/slotValues
  3. Refactors slot filters view to use search endpoint when filtering values

Improvements #

Show more error details when changing a connected repository branch doesn't work.

2. On completion of the project sync, the git service emits a websocket event, clearing the visual sync state in the frontend.

Bugfixes #

in a 500 error code. Improved error handling by prompting for missing keys.

In conjunction with https://github.com/RasaHQ/rasa/pull/10413, this allows multiple deployment environments to work when using Kafka as the event broker.

Miscellaneous internal changes #

[0.42.6] - 2021-11-23 #

Miscellaneous internal changes #

[0.42.5] - 2021-11-11 #

Bugfixes #

Set the definition of trainable as an entity extracted by an extractor known to be trainable, in line with the previous definition used by the frontend.

[0.42.4] - 2021-10-21 #

Bugfixes #

Miscellaneous internal changes #

[0.42.3] - 2021-09-29 #

Improvements #

Bugfixes #

[0.42.2] - 2021-09-07 #

Bugfixes #

[0.42.1] - 2021-09-02 #

Improvements #

Bugfixes #

due to Sanic being updated to a version not supported by Rasa Open Source.

Here is the usual error that was getting printed to the console when trying to start Rasa X:

Copy

AttributeError: 'Sanic' object has no attribute 'auth'

'Sanic' object has no attribute 'auth'

[0.42.0] - 2021-07-27 #

Features #

Bugfixes #

Miscellaneous internal changes #

[0.41.2] - 2021-07-12 #

Bugfixes #

[0.41.1] - 2021-06-25 #

Improvements #

[0.41.0] - 2021-06-23 #

Features #

Improvements #

enterprise license. Instead of starting with no environments, start only with the production and worker ones.

This speeds up bulk update for large-scale datasets.

Bugfixes #

[0.40.1] - 2021-05-28 #

Bugfixes #

[0.40.0] - 2021-05-26 #

Features #

Change behaviour of entity annotation in the NLU Inbox and Training Data screen. Add Edit message modal for table row entries in the NLU Inbox and Training Data screen.

Bugfixes #

Previously all stories were validated, also the ones from the database.

Miscellaneous internal changes #

to main. This default value should only impact you if you're doing a manual API call without specifying a branch name. You can read more about this initiative here.

[0.39.5] - 2021-07-29 #

Bugfixes #

[0.39.4] - 2021-06-15 #

Features #

Bugfixes #

[0.39.3] - 2021-05-05 #

Improvements #

Bugfixes #

[0.39.2] - 2021-04-30 #

Note: Due to a possible bug in a database migration, please upgrade to 0.39.3 directly.

Bugfixes #

[0.39.1] - 2021-04-24 #

Note: Due to a possible bug in a database migration, please upgrade to 0.39.3 directly.

Bugfixes #

Miscellaneous internal changes #

[0.39.0] - 2021-04-22 #

Note: Due to a possible bug in a database migration, please upgrade to 0.39.3 directly.

Deprecations and Removals #

Features #

Improvements #

Bugfixes #

Improved Documentation #

["Annotate NLU Examples" documentation page]( Intent Insights with information about NLU Insights and how to use it in combination with NLU Inbox.

Miscellaneous internal changes #

[0.38.2] - 2021-04-27 #

Bugfixes #

[0.38.1] - 2021-03-26 #

Bugfixes #

[0.38.0] - 2021-03-23 #

Features #

Improvements #

Bugfixes #

This results in the default pipelines or policies being applied as usual.

[0.37.4] - 2021-06-15 #

Features #

Bugfixes #

[0.37.3] - 2021-05-14 #

Bugfixes #

[0.37.2] - 2021-03-24 #

Bugfixes #

[0.37.1] - 2021-03-05 #

Bugfixes #

[0.37.0] - 2021-02-24 #

Deprecations and Removals #

Features #

Improvements #

Introduced Redis cache to improve performance of conversation screen. Now the endpoints.yml has one more section by default:

Copy

cache:

type:"redis"

url:""

port:6379

db:2

password:""

Bugfixes #

[0.36.0] - 2021-02-18 #

Features #

Intent Insights that provides suggestions to improve the NLU training data and helps prioritizing annotations in the NLU inbox.

The following endpoints were added as part of this feature:

Improvements #

Use the updated GET /insights/nlu API method to load the latest evaluation report for a specified status (in_progress, success or failure).

Add the new empty status for "Suggestions" and "Warnings" in intent insights table.

Bugfixes #

docker-compose deployment generated an invalid password for the RabbitMQ deployment.

In the project layout validation, updated the filenames so they pinpoint to the correcting missing files.

Fix Training Data filter panel to update to match the search query.

Miscellaneous internal changes #

[0.35.2] - 2021-03-19 #

Bugfixes #

[0.35.1] - 2021-02-03 #

Bugfixes #

[0.35.0] - 2021-01-13 #

Features #

Bugfixes #

Miscellaneous internal changes #

Known issues #

[0.34.0] - 2020-12-02 #

Features #

Improvements #

On click, the row is keyboard focused and the selected item doesn't scroll On hover, the icons of the row appear

Previously the response was always HTTP no content. Put evaluation for project responds with HTTP not found instead of bad request if model was not found.

that allow to implement suggestions in the "Responses" screen.

Show suggestions when users search for responses.

Bugfixes #

Update POST /projects/<project_id>/git_repositories/<repository_id>/branches/<branch_name>/commits to return BranchAlreadyExists errors in cases when users try to create a branch that already exists.

[0.33.2] - 2020-11-09 #

Improved Documentation #

[0.33.1] - 2020-11-05 #

Improvements #

This means that the corresponding keys in a domain file can contain values of more than 255 characters.

Bugfixes #

[0.33.0] - 2020-10-27 #

Features #

Since now the database migration is run as a separate service by default.

Improvements #

discovery has not finished, Rasa X now polls the connected Rasa Production service at its /status endpoint , which reports the model that's currently loaded, and associates this model with incoming NLU logs.

about events such as Git being connected and models being uploaded. The onboarding will react faster to these events and update the state of the onboarding without reloading the page.

docker-compose setup to use the latest versions. This fixes the security vulnerability CVE-2020-10878 for the updated images.

Talk to your Bot conversations created by that user can remain. Removed the created_by foreign key constraint in the conversations table to achieve this.

Added a new boolean query parameter deleteCreatedConversations (default: false) to the Rasa X HTTP API endpoint for deleting users (DELETE /api/users/<username>). The parameter controls whether conversations created by the user that is being deleted in the Talk to your Bot screen should be deleted as well.

Added a new optional command-line argument to the rasa_x_commands.py script called --delete-created-conversations. If set, the conversations created in the Talk to your Bot screen by the user that is being deleted will be deleted as well.

The full command for deleting users and their associated Talk to your Bot conversations is

Copy

cd /etc/rasa

sudo python rasa_x_commands.py delete --delete-created-conversations

Bugfixes #

Integrated Version Control when connecting Integrated Version Control to a branch which does not contain a valid Rasa Open Source project. A valid branch has to contain a domain.yml, a config.yml as well as a data/ directory with the training data.

where the event service was running as a separate service.

This message fixes the onboarding flow and allows users to progress beyond the "Your assistant is talking to users" step.

[0.32.5] - 2021-06-21 #

Features #

[0.32.4] - 2020-12-14 #

Improvements #

Changed the Conversations screen to request items sequentially rather than by offset, to improve speed.

Note: When upgrading from this version, you need to upgrade directly to version 0.35.0 or later.

[0.32.3] - 2020-11-17 #

No significant changes.

[0.32.2] - 2020-09-09 #

Bugfixes #

[0.32.1] - 2020-09-04 #

Bugfixes #

[0.32.0] - 2020-08-20 #

Features #

Added a keyboard shortcut for Conversation Context - 'c'.

Improvements #

CORS.

Ensure all HTTP API endpoints support OPTIONS requests.

Holding the shift key when selecting rows in the NLU inbox will select all rows in between the start and finish selections

Bugfixes #

Fix Select boxes not looking like the designs Fix Chat box vertical height Improve Select box performance

[0.31.6] - 2020-10-28 #

Deprecations and Removals #

Improvements #

Changed the Conversations screen to request items sequentially rather than by offset, to improve speed.

Note: When upgrading from this version, you need to upgrade directly to version 0.35.0 or later.

Bugfixes #

[0.31.5] - 2020-08-10 #

Bugfixes #

[0.31.4] - 2020-08-06 #

Bugfixes #

1.10.9 which means means user responses are no longer added to the domain’s actions section.

For local installations, rasa-x will continue to work with Rasa Open Source version 1.9.5 or higher. Please upgrade to rasa>=1.10.9 if you need the bug resolved.

[0.31.3] - 2020-08-04 #

Miscellaneous internal changes #

release. This ensures that new releases will always use the latest base images including the latest security fixes.

[0.31.2] - 2020-07-31 #

Improved Documentation #

[0.31.1] - 2020-07-30 #

Improvements #

Bugfixes #

from multiple files without removing the previously saved ones.

Miscellaneous internal changes #

[0.31.0] - 2020-07-16 #

Features #

authenticate with the WebSocket server, the client must send a JSON message with the following content: {"Authorization": "Bearer <JWT of user>"}.

Bugfixes #

[0.30.1] - 2020-07-07 #

Improved Documentation #

[0.30.0] - 2020-07-06 #

Features #

Improvements #

Show the confidence for the predicted intent or action in the Conversation Inspector.

You can also filter conversations by their review status.

Bugfixes #

overwritten by older minor releases of Rasa X.

Fixed the button link on an empty Training Data screen to NLU Inbox. Fixed the size of the Tab headings on Training Data screen.

Add ‘Anonymous user’ when users name from a conversation cannot be determined.

Miscellaneous internal changes #

Add Sphinx-related dependencies to the list of dependencies ignored by Dependabot.

[0.29.3] - 2020-06-25 #

Bugfixes #

[0.29.2] - 2020-06-19 #

Bugfixes #

Fix the layout and style of filter buttons on “Manage users” page.

[0.29.1] - 2020-06-10 #

Bugfixes #

Previously it could have happened that the deploy script provided a private URL which was unreachable from the outside.

[0.29.0] - 2020-06-08 #

Deprecations and Removals #

API endpoint. Rasa X already de-duplicates the message logs which has the same effect as using the distinct parameter.

Improvements #

This change makes these filters much more useful for reviewing failed conversations than before.

have conversations.

Add UI permission checks to show certain UI components only if the user has access to them.

Improve consistency between Rasa UI components Improve useMediaQuery hook

GET /projects/<project_id>/git_repositories/<repository_id>/status endpoint.

The previously suggested /tracker endpoint is blocked by AdBlockers. From the users perspective that would looks like conversation is not updated (is empty), because the polling was blocked. Now the only possible (and default) value of format is full_conversation, which returns a conversation tracker in exactly the same format as /tracker endpoint.

Close button added to the conversation inspector. Re-introduce the annotate highlighter button beside a user message on the conversations screen.

migrations were already completed.

Bugfixes #

database. Message logs no longer reference a model by ID, as models can be deleted. Instead, message logs now reference the model contained in the message’s parse_data. If this is unavailable, the model that’s currently marked as ‘production’ is used. To achieve this, a new column model is added to the message_log table. The previous column model_id and a foreign key constraint to the model table are removed.

Existing message logs were not associated with the model that was actually used. A model named ‘unavailable’ is assigned to existing logs in the migration.

The suggestions returned from GET /projects/<project_id>/logs/<log_hash> and GET /projects/<project_id>/logs no longer contain the project_id and team keys.

This could e.g. lead to failing model trainings.

switching from an invalid project layout to a valid one. When changes are discarded Rasa X will now no longer try to inject the old (invalid) state, but will instead switch to the latest state of the connected remote branch.

Miscellaneous internal changes #

[0.28.6] - 2020-06-04 #

Bugfixes #

[0.28.5] - 2020-05-28 #

Improvements #

to train, use the SANIC_RESPONSE_TIMEOUT environment variable to increase the timeout to avoid 503: Response Timeout errors.

Bugfixes #

[0.28.4] - 2020-05-26 #

Improvements #

/api/projects/{project_id}/data/{hash}` endpoints now return 404 instead of 400 when the requested entity was not found.

Bugfixes #

orange state after pushing changes to the target branch.

PUT /projects/<project_id>/git_repositories/<repository_id>/branches/<branch_name> endpoint to only return once the injection of repository data into the Rasa X database has been completed. This fixes a bug in Integrated Version Control where the new state of the database wasn’t immediately reflected in the UI after discarding changes.

when the bot_name or description fields have an invalid length. The maximum length for both fields is 255 characters.

Miscellaneous internal changes #

[0.28.3] - 2020-05-12 #

Bugfixes #

conversations to the backend side. This security fix is important, so we recommend all clients to upgrade as soon as possible.

Miscellaneous internal changes #

variable METRICS_CONSENT to true. Note that an external EventService has to be restarted for changes to take effect.

[0.28.2] - 2020-05-07 #

Improvements #

Bugfixes #

[0.28.1] - 2020-05-05 #

Improvements #

have conversations.

Add UI permission checks to show certain UI components only if the user has access to them.

Bugfixes #

[0.28.0] - 2020-04-30 #

Deprecations and Removals #

and /responses/<response_id>. The old endpoints are deprecated and will be removed in a future version of Rasa X.

Improvements #

now set dependent on a start via local.main (in general, this corresponds to a pip installation) or server.main (in general, this corresponds to a Docker Compose or Kubernetes installation).

these changes, template is now renamed to response everywhere in Rasa X.

This has the following implications for API requests:

For each of these, the old parameters are deprecated and will be removed in a future version of Rasa X.

Also, all API requests previously returning a template including a field template now return a response including a field response_name.

retrieval actions.

This feature requires Rasa 1.10 or higher.

any interaction with the Kubernetes clusters after the installation (e.g. through kubectl or helm) don’t require the usage of sudo anymore.

increases the throughput from Rasa Open Source to Rasa X.

Revisited the error handling when saving conversation events to the database in Rasa X. Errors are now handled centrally which avoids storing events partially.

and codes 400 or 409 in the case of failure.

Replaced Duckling image with version 0.1.6.3 which has a much smaller image size and fixes security issues.

single file. All popups are now opened declaratively rather than being non-controlled.

Bugfixes #

duplicated entries in tables.

Previously, such warnings always occured when starting Rasa X and when adding, updating or saving stories.

users with these roles to fetch models, responses, and stories.

are more than one model available and the active one is not the first one.

Improved Documentation #

Exposing the RabbitMQ Port.

can be applied to both, new and existing, deployments by (re)running the script.

Miscellaneous internal changes #

Fix Task was destroyed but it is pending! warning message appearing when exiting Rasa X using Ctrl-C (local mode).

everywhere else in Rasa X.

server. Note that the communication between Rasa Open Source and the action server is not affected by this and will continue to work as usual.

This avoids misleading errors when Rasa Open Source hasn’t finished its initialization phase.

[0.27.8] - 2020-05-13 #

Bugfixes #

[0.27.7] - 2020-04-23 #

Improvements #

[0.27.6] - 2020-04-20 #

Improvements #

there were changed files.

[0.27.5] - 2020-04-14 #

Bugfixes #

established with the exclude_tablespaces=[] SQLAlchemy option. Previously, Oracle tables that were created by the SYSTEM or SYSAUX users would not be retrieved, leading to errors during database migration such as

Copy

sqlalchemy.exc.DatabaseError: (cx_Oracle.DatabaseError) ORA-00942: table or view does not exist

model to Rasa X. Uploading models won’t affect the status of Integrated Version Control anymore.

Improved Documentation #

[0.27.4] - 2020-04-02 #

Improvements #

PostgreSQL schemas. Rasa X accesses schemas defined by the POSTGRESQL_SCHEMA environment variable.

In order to use a non-public schema for both the Rasa X and the Rasa tracker store database connections, the POSTGRESQL_SCHEMA environment variable has to be set on the rasa-x, event-service and rasa-production services.

The schema is added to the connection string option’s -csearch_path key, i.e. -options=-csearch_path=<SCHEMA_NAME> (see https://www.postgresql.org/docs/11/contrib-dblink-connect.html for more details). As before, if no POSTGRESQL_SCHEMA environment variable is defined, Rasa X uses the database’s default schema (public).

The schema has to exist in the database before connecting, i.e. it needs to have been created with

Copy

CREATE SCHEMA schema_name;

Bugfixes #

[0.27.3] - 2020-03-31 #

Bugfixes #

PUT /templates endpoints. This was previously fixed in version 0.25.0 but re-introduced in version 0.27.0.

[0.27.2] - 2020-03-30 #

Improvements #

ConversationCreationFailed error (code 422: Unprocessable Entity) if the tracker for the requested conversation ID cannot be fetched from the Rasa server. Previously this resulted in a 500: Internal Server Error.

Bugfixes #

Miscellaneous internal changes #

[0.27.1] - 2020-03-27 #

Improvements #

Improved Documentation #

[0.27.0] - 2020-03-26 #

Features #

The information about available updates is retrieved from the Rasa X Docker Hub release tags.

Improvements #

Also save the information about shown hints to the database in order to not show them again.

changes are no longer reflected on disk immediately, but with a delay of at most 60 seconds. This change improves the performance of annotations.

reducing the number of requests between the UI and the Rasa X backend.

requires the tests.create permission, and this permission is granted to all administrators and annotators by default.

The default file for tests is conversation_tests.md in tests directory but both directory and file names can be modified (DEFAULT_E2E_TESTS_DIR and DEFAULT_E2E_TEST_FILE_PATH are the corresponding environment variables).

based on whether any of its constituent conversation sessions are entirely in training data. A conversation session is considered to be in training data if all of its predicted actions were predicted by a memoization policy ( Memoization Policy or Augmented Memoization Policy).

In order to store the information based on individual sessions, the conversation_session table receives a new column in_training_data. New entries in the conversation_session table are now created based on incoming session_start events. This was done previously based on a period of user inactivity of 48 hours. This aligns the previous Rasa X concept of a conversation session with the session concept in Rasa Open Source introduced in Rasa 1.7.4.

in endpoints.yml. If this is the case, the first queue will be consumed. The consumer continues to support the queue argument. If queues is supplied, it takes precedences over queue.

longer required to add the /core/ prefix to the endpoint. Nginx will route http://<HOST>/webhooks/ requests to the rasa-production container.

Bugfixes #

Rasa 1.7.0, utterances need not be specified in the domain’s actions.

The POST /templates, PUT /templates and PUT /templates/<id> endpoints return status code 422 if the supplied response names do not start with the utter_ prefix (rasa.core.constants.UTTER_PREFIX).

Integrated Version Control. Rasa X also re-applies the required permissions in case they were changed over the lifetime of the deployment.

Improved Documentation #

documentation. helm init is not longer required since Helm version 3.

Miscellaneous internal changes #

joined eager loading for the nlu_training_data table’s relationship with the nlu_training_data_entity table.

[0.26.4] - 2020-05-13 #

Bugfixes #

[0.26.3] - 2020-03-24 #

Bugfixes #

[0.26.2] - 2020-03-23 #

Bugfixes #

Copy

sqlalchemy.exc.OperationalError: (psycopg2.errors.ProgramLimitExceeded) index row size 3176 exceeds maximum 2712 for index "conversation_slot_value_index"

synonyms when dumping them. They are now dumped in the same order as they were inserted.

Miscellaneous internal changes #

POST /projects/{project_id}/synonyms.

[0.26.1] - 2020-03-13 #

Improved Documentation #

documentation. helm init is no longer required since Helm version 3.

[0.26.0] - 2020-03-06 #

Deprecations and Removals #

Introduced GET /conversations/{conversation_id}/tracker as an alternative to the endpoint mentioned above

Features #

Now users can completely remove conversations with specified IDs using the REST API.

a public SSH key generated by Rasa X.

When connecting a Git repository to Rasa X, it’s now possible to specify a field use_generated_ssh_keys instead of providing an SSH key. Integrated Version Control will then use a generated SSH key to authenticate with the Git server. To make this work you have to store the public SSH key from the /projects/{project_id}/git_repositories/public_ssh_key endpoint at your Git server.

using an embedded Kubernetes cluster or with an existing Kubernetes cluster.

Added new input_channels parameter to the GET /conversations endpoint.

Added new GET /conversations/slotNames and GET /conversations/slotValues endpoints.

Restore the ability to filter Conversations by maximum NLU confidence

Improvements #

if no new model was trained because a model with the same training data and configuration already exists.

and try saving them again after a successful attempt to save another incoming event to the database.

The limit of pending events is set to 1000 to avoid excessive memory usage.

type_name columns of the conversation_event table. This is to ensure that events that are exported repeatedly using rasa export are not duplicated in the database.

note

Duplicate events in the converation_event table are deleted as part of the migration. Duplicate events are determined based on having more than one entry with the same conversation_id, timestamp and type_name values.

Rasa X from refusing to save stories when the domain is problematic.

is no longer compatible with Rasa Open Source 1.7 or older.

Bugfixes #

referenced with their absolute path by the NLU training files. This led to problems when training a Rasa Open Source model in the project directory since the lookup table files could not be found.

Prevent the main Rasa X UI from allowing login with a ShareYourBot session

Rasa X directory. Earlier the task backwards compatible credentials failed when doing this.

Improved Documentation #

Rasa X Helm chart.

rasa export to migrate conversations from Rasa to Rasa X. See 1. Import Existing Conversations from Rasa Open Source. This section now includes the existing section ‘Connect a Live Rasa Deployment’.

note

rasa export requires rasa>=1.8.0.

Miscellaneous internal changes #

originating from a rasa export call.

[0.25.3] - 2020-05-14 #

Bugfixes #

[0.25.2] - 2020-02-14 #

Features #

Bugfixes #

conversation events with an empty metadata field. This problem led to conversations not being loaded.

Improved Documentation #

[0.25.1] - 2020-02-07 #

Features #

request size for requests sent to Rasa X server. Default set to 800 MB, up from sanic’s default of 100MB.

Bugfixes #

This includes two empty migration for those who upgrade from 0.24.x, and two new migrations on top for those upgrading Rasa X from 0.25.0

Miscellaneous internal changes #

empty strings to eliminate the warning of these variables not being set.

[0.25.0] - 2020-02-05 #

Deprecations and Removals #

GET /conversations/<id> no longer returns flagged_messages.

Features #

Now users can assign/delete arbitrary tags to conversations via REST API.

Rasa X is started for the first time.

Improvements #

instead of dumping the whole training data.

Bugfixes #

a different branch at the same time.

Fixed bug where Integrated Version Control could not push changes due the lack of a configured Git identity. Commits by Rasa X will now use the author name Rasa X and the email rasa-x@rasa.com.

Improved Documentation #

training data will be overwritten when a Git Repository is connected to Rasa X.

open-sourced Helm chart.

Miscellaneous internal changes #

Made runtime telemetry configuration safe to read and write from different processes.

https://github.com/RasaHQ/rasa-x-helm.

when installing Docker as part of this script.

[0.24.8] - 2020-05-15 #

Bugfixes #

[0.24.7] - 2020-01-31 #

Bugfixes #

Integrated Version Control.

host network.

To keep compatibility with Rasa 1.6, Rasa X will continue to return responses within the templates section until the next minor release.

Miscellaneous internal changes #

we have the right permissions for the given repository.

PyPI package.

when installing Docker as part of this script.

[0.24.6] - 2020-01-27 #

Bugfixes #

Integrated Version Control.

Miscellaneous internal changes #

[0.24.5] - 2020-01-27 #

Miscellaneous internal changes #

[0.24.4] - 2020-01-23 #

Bugfixes #

explicit declaration of sequences is required for Oracle DB.

The event_service when forked as a subprocess now waits for migrations to finish before accessing the database.

[0.24.3] - 2020-01-22 #

Bugfixes #

exceeds the length of 30 characters allowed by Oracle DB 11.2. The index was renamed to nlu_train_dat_ent_orig_val_idx.

The column name carry_over_slots_to_new_session in table domain also exceeds 30 characters. The column was renamed to carry_over_slots.

Improved Documentation #

open-sourced Helm chart.

[0.24.2] - 2020-01-21 #

Bugfixes #

incompatible.

Improved Documentation #

the GET /conversations/<id> endpoint. A JSON dump of the tracker is returned as a file attachment if the Accept: application/json header is specified. A debug story dump of the tracker is returned as a file attachment if the Accept: text/markdown header is specified.

Removed outdated documentation for the GET /conversations/<id>/events endpoint.

conversations

Miscellaneous internal changes #

[0.24.1] - 2020-01-09 #

Bugfixes #

[0.24.0] - 2020-01-07 #

Features #

Bugfixes #

Improvements #

Deprecations and Removals #

[0.23.6] - 2020-01-07 #

Bugfixes #

Features #

[0.23.5] - 2019-12-18 #

Bugfixes #

[0.23.4] - 2019-12-12 #

Bugfixes #

Improvements #

[0.23.3] - 2019-12-06 #

Features #

Bugfixes #

Improvements #

[0.23.2] - 2019-11-29 #

Features #

Bugfixes #

Improvements #

Deprecations and Removals #

[0.23.1] - 2019-11-28 #

Bugfixes #

Copy

Error: UPGRADE FAILED: cannot patch "rasa-app" with kind Deployment: Deployment.apps "rasa-app" is invalid: spec.selector: Invalid value: v1.LabelSelector{MatchLabels:map[string]string{"app.kubernetes.io/instance":"rasa", "app.kubernetes.io/managed-by":"Helm", "app.kubernetes.io/name":"rasa-x", "app.kubernetes.io/version":"0.23.0", "app.name":"app-deployment.yaml", "helm.sh/chart":"rasa-x-0.23.0"}, MatchExpressions:[]v1.LabelSelectorRequirement(nil)}: field is immutable && cannot patch

The following workaround can be used to upgrade:

Copy

kubectl delete deployment --namespace -l app.kubernetes.io/instance=

After the upgrade the issue should not happen anymore.

[0.23.0] - 2019-11-26 #

Features #

Bugfixes #

Improvements #

[0.22.2] - 2019-11-08 #

Features #

Bugfixes #

Improvements #

[0.22.1] - 2019-10-29 #

Bugfixes #

[0.22.0] - 2019-10-22 #

Features #

Bugfixes #

Improvements #

Deprecations and Removals #

[0.21.5] - 2019-10-21 #

Improvements #

Bugfixes #

[0.21.4] - 2019-10-10 #

Features #

Bugfixes #

Deprecations and Removals #

[0.21.3] - 2019-10-03 #

Bugfixes #

[0.21.2] - 2019-10-01 #

Features #

Bugfixes #

[0.21.1] - 2019-09-26 #

Bugfixes #

[0.21.0] - 2019-09-24 #

Features #

Bugfixes #

Improvements #

These variables may also be set when Rasa X is started locally from the command line. The previous environment variable JWT_SECRET in combination with symmetric encryption is no longer supported. The rasa services still support the --jwt-secret command-line argument for encryption of the underlying Rasa server.

Deprecations and Removals #

[0.20.5] - 2019-10-09 #

Features #

Bugfixes #

[0.20.4] - 2019-19-08 #

[0.20.3] - 2019-09-18 #

Bugfixes #

Improvements #

[0.20.2] - 2019-08-28 #

Features #

Bugfixes #

Improvements #

[0.20.1] - 2019-08-12 #

Features #

Bugfixes #

Improvements #

[0.20.0] - 2019-07-26 #

Features #

Bugfixes #

Improvements #

[0.19.5] - 2019-07-09 #

Bugfixes #

[0.19.4] - 2019-07-09 #

Bugfixes #

Improvements #

[0.19.3] - 2019-07-05 #

Features #

Bugfixes #

Improvements #

[0.19.2] - 2019-06-17 #

Bugfixes #

[0.19.1] - 2019-06-13 #

Features #

Bugfixes #

Improvements #

[0.19.0] - 2019-05-21 #

Features #

Bugfixes #

Improvements #

We collect and process your personal information for the following purposes: Visitor Statistics, Browsing Behavior. Learn more...

OKDecline