Skip to content

feat(inbox): create connect chat channel connections #25854

feat(inbox): create connect chat channel connections

feat(inbox): create connect chat channel connections #25854

Triggered via pull request April 14, 2026 16:17
@djabarovgeorgedjabarovgeorge
synchronize #10671
Status Failure
Total duration 20s
Artifacts

conventional-commit.yml

on: pull_request_target
Validate PR titles
14s
Validate PR titles
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 warning
Validate PR titles
Unknown scope "inbox" found in pull request title "feat(inbox): create connect chat channel connections". Scope must match one of: root, api-service, dashboard, inbound-mail, webhook, worker, ws, ee-ai, ee-api, ee-auth, ee-billing, ee-shared-services, ee-translation, step-resolver-worker, application-generic, automation, dal, api, maily-core, maily-render, maily-tailwind-config, maily-tsconfig, notifications, testing, add-inbox, agent-toolkit, framework, js, nextjs, novu, providers, react, react-native, shared, stateless, nestjs, nextjs.
Validate PR titles
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: amannn/action-semantic-pull-request@v5, marocchino/sticky-pull-request-comment@v2, pnpm/action-setup@v3. 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/