Apart from Unit and Integration tests, we should also run the st2-self-check script for every PR as part of the CI pipeline.
Something we do in e2e and manual testing.

It should be possible with the Github Actions and would help us to catch bugs before merging into master.
Ex #5489.

Is your feature request related to a problem? Please describe.

The latest released BotKube image has a few vulnerabilities. The report can be seen at artifacthub: https://artifacthub.io/packages/helm/infracloudio/botkube?modal=security-report

Describe the solution you'd like

We should -

• Fix the image vulnerabilities
• And, add a CI check to catch such vulnerabilities early be

Description

Randomly the matrix connector will crash when connected to a public room.

Steps to Reproduce

Create a skill and point it to #geeklab:linuxdelta.com and wait for people t

Reproducible in:

slack-sdk==3.13.0
Python 3.8.8
ProductName:	macOS
ProductVersion:	12.0
BuildVersion:	21A5506j
Darwin Kernel Version 21.1.0: Thu Aug 19 02:54:44 PDT 2021; root:xnu-8019.40.29~26/RELEASE_ARM64_T8101

Steps to reproduce:

(Share the commands to run, source code, and project settings (e.g., set

Related: yetibot/yetibot#371

Current API (AlphaVantage) is rate limited to 3 reqs per 5 min 😖

name: test
match: command
args:
  - var1

to

name: test
match: command
expose_args:
  - var1

This is consistent with expose_json_fields. So, any time we expose variable from within rules we would use the expose_ prefix.