chore: skip TLS verification for the Mattermost webhook

[artembelik]

No description provided.

[coderabbitai]

Warning

Review limit reached

@artembelik, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 54 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 559938d7-c91d-432a-aba3-e5e037a0ee77

📥 Commits

Reviewing files that changed from the base of the PR and between 9f96068 and e076dbb.

📒 Files selected for processing (2)

• .github/workflows/pr-notification.yml
• .github/workflows/publish.yml

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Visit the preview URL for this PR (updated for commit e076dbb):

https://data-grid-next--data-grid-pr-209-vntjgrk9.web.app

_{(expires Fri, 14 Aug 2026 12:09:35 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

_{Sign: b9d49913f5b5988e9af8690a8b37f16143707448}

[Copilot]

Pull request overview

This PR updates GitHub Actions workflows to bypass TLS certificate verification when sending Mattermost webhook notifications.

Changes:

• Adds NODE_TLS_REJECT_UNAUTHORIZED: '0' to the Mattermost notify step in the publish workflow.
• Adds the same TLS-bypass env var to both notification steps in the PR notification workflow.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
.github/workflows/publish.yml	Disables TLS verification for the Mattermost notification step in the release publish job.
.github/workflows/pr-notification.yml	Disables TLS verification for Mattermost notifications sent on pull_request_target.

Suppressed comments (1)

.github/workflows/pr-notification.yml:34

• Disabling TLS verification via NODE_TLS_REJECT_UNAUTHORIZED='0' in this step weakens transport security for the webhook call. Prefer keeping verification on and addressing the underlying certificate/CA trust (runner CA install, NODE_EXTRA_CA_CERTS, or a publicly trusted cert).

        uses: mattermost/action-mattermost-notify@v2.1.0
        env:
          NODE_TLS_REJECT_UNAUTHORIZED: '0'
        with:

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.