Housekeeping, Sprint 48

[vcidst]

Proposed changes:

• https://github.com/RasaHQ/rasa-sdk/pull/1006
• https://github.com/RasaHQ/rasa-sdk/pull/1002
• https://github.com/RasaHQ/rasa-sdk/pull/1001
• https://github.com/RasaHQ/rasa-sdk/pull/976

There are no changes needed in pyproject.toml for the following so I'll be closing these PRs after updating the poetry.lock file with poetry update ruamel-yaml typing-extensions requests,

• https://github.com/RasaHQ/rasa-sdk/pull/1005
• https://github.com/RasaHQ/rasa-sdk/pull/993
• https://github.com/RasaHQ/rasa-sdk/pull/982

Status (please check what you already did):

• [x] made PR ready for code review
• [ ] added some tests for the functionality
• [ ] updated the documentation in the rasaHQ/rasa
• [ ] updated the changelog (please check changelog for instructions)
• [ ] reformat files using black (please check Readme for instructions)

[vcidst]

@ancalita As per your comment here, how should I test that updating prompt-toolkit doesn't break commands in rasa-oss?

[ancalita]

@ancalita As per your comment here, how should I test that updating prompt-toolkit doesn't break commands in rasa-oss?

I think this needs to be tested on a rasa-oss branch where you pin rasa-sdk branch to this branch. Then you test rasa interactive. Let me try to dig around Slack to see if i can find more details beyond my faded memories 😆

[ancalita]

@vcidst Managed to find this PR that describes that the prompt toolkit upgrade was breaking unit tests in rasa-oss (with a link to submitted ticket in prompt-toolkit repo). It seems that beyond testing rasa shell and rasa interactive we need to be careful CI passes on OSS end as well. Hope this helps!

[vcidst]

@ancalita Thank you for the insight! I'll leave prompt-toolkit out of this housekeeping PR in that case and create a ticket to update it

https://rasahq.atlassian.net/browse/ATO-1303