AAP Chatbot: GH Actions fix.

Signed-off-by: romartin <roger600@gmail.com>

Author: romartin

.github/workflows/ui_release_aap_chatbot.yml

@@ -30,6 +30,10 @@ jobs:
         run: npm run test
         working-directory: ${{env.WORKING_DIRECTORY}}
 
+      - name: Run linter
+        run: npm run eslint
+        working-directory: ${{env.WORKING_DIRECTORY}}
+
       - name: Versioning
         # Consider patch/minor/major versions later on, maybe as a workflow input.
         run: npm version patch

aap_chatbot/README.md

@@ -72,3 +72,16 @@ CHATBOT_DEFAULT_PROVIDER=wisdom
   }
 }
 ```
+
+## Releasing and publishing
+
+Run the following GH workflows, in order:
+
+1.- [AAP Chatbot - Release](../.github/workflows/ui_release_aap_chatbot.yml)
+It validates the package by running tests, if successful, it releases a new version and commits the package information into the `main` branch.
+
+2.- [AAP Chatbot - Publish](../.github/workflows/ui_publish_aap_chatbot.yml)
+It validates the package by running tests, if successful, it builds, assembles and publishes the new [package version into npmjs](https://www.npmjs.com/package/@ansible/ansible-ai-connect-chatbot?activeTab=versions).
+
+NOTE: Split the whole process into two different workflows so it gives a bit more flexibility on how to release and when to publish.
+NOTE: Based on the [npmjs guideline for publishing new packages](https://docs.npmjs.com/updating-your-published-package-version-number).

aap_chatbot/src/App.test.tsx

@@ -295,6 +295,7 @@ function mockFetchEventSource() {
     const ok = status === 200;
     await init.onopen({ status, ok });
     if (status === 200) {
+      // eslint-disable-next-line no-nested-ternary
       const streamData = agent
         ? streamAgentNormalData
         : errorCase