Skip to content

fix: slack importer not importing messages correctly #57107

fix: slack importer not importing messages correctly

fix: slack importer not importing messages correctly #57107

Re-run triggered April 6, 2026 14:42
Status Success
Total duration 11m 11s
Artifacts 34

ci.yml

on: pull_request
⚙️ Variables Setup
12s
⚙️ Variables Setup
🚀 Notify external services - draft
5s
🚀 Notify external services - draft
📦 Build Packages
2m 9s
📦 Build Packages
Matrix: 🔎 Code Check / code-check
🔨 Test Unit  /  Unit Tests
5m 36s
🔨 Test Unit / Unit Tests
Matrix: build
🔨 Test Storybook  /  Test Storybook
1m 47s
🔨 Test Storybook / Test Storybook
Matrix: 🚢 Build Docker
🚢 Publish Docker Images (ghcr.io)
26s
🚢 Publish Docker Images (ghcr.io)
Matrix: 🔨 Test API (EE) / test
Matrix: 🔨 Test API Livechat (EE) / test
Matrix: 🔨 Test UI (EE) / test
🔨 Test Federation Matrix
7m 36s
🔨 Test Federation Matrix
Matrix: 🔨 Test API Livechat (CE) / test
Matrix: 🔨 Test API (CE) / test
Matrix: 🔨 Test UI (CE) / test
🚀 Publish build assets
🚀 Publish build assets
📦 Track Image Sizes
40s
📦 Track Image Sizes
📊 Report Coverage
36s
📊 Report Coverage
✅ Tests Done
5s
✅ Tests Done
🚀 Publish Docker Images (DockerHub)
🚀 Publish Docker Images (DockerHub)
🚀 Notify external services
🚀 Notify external services
Update Version Durability  /  update-versions
Update Version Durability / update-versions
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
🔨 Test API Livechat (EE) / MongoDB 8.0 coverage (1/1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, denoland/setup-deno@v1, docker/login-action@v3, rharkor/caching-for-turbo@v1.8. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
📊 Report Coverage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
coverage-api-livechat-1
2.87 MB
sha256:c2994096564ae4f47b6c52e58f28ee96d1a30cd8c380486af7945e16ce474d23
reports-coverage
504 KB
sha256:909288374147bf2fc9fff195399f4621a581336f2c82045102881ff1396d504e