Pinned Slack GitHub Action to latest SHA

[EvanHahn]

no ref

We should pin all of our GitHub Actions to specific SHAs for security and reproducibility.

Notably, this updates from v2.1.1 to v3.0.1. The breaking change in 3.0 shouldn't affect us because we're using GitHub-hosted CI runners.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 67da6922-a3c1-4292-9041-89b59b5ba495

📥 Commits

Reviewing files that changed from the base of the PR and between b453e78 and 8f3fa5f.

📒 Files selected for processing (1)

• .github/actions/deploy-tinybird/action.yml

---

Walkthrough

The pull request updates a GitHub composite action that handles deployments. The Slack notification step in .github/actions/deploy-tinybird/action.yml is updated to use a newer version of the Slack GitHub action, moving from v2.1.1 to v3.0.1 (commit af78098f536edbc4de71162a307590698245be95). The conditional execution (if: always()) and the webhook/payload configurations remain unchanged. This is a dependency version bump with no modification to the action's public interface.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Pinned Slack GitHub Action to latest SHA' directly and clearly summarizes the main change: updating a GitHub Action dependency to a pinned SHA version.
Description check	✅ Passed	The description is fully related to the changeset, explaining the security rationale for pinning to SHAs, the version upgrade from v2.1.1 to v3.0.1, and addressing potential breaking changes.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch github-slack-action-pin-to-exact-version

---

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 and usage tips.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 73.45%. Comparing base (8ec8482) to head (6613820).
⚠️ Report is 56 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #27212      +/-   ##
==========================================
- Coverage   73.45%   73.45%   -0.01%     
==========================================
  Files        1545     1545              
  Lines      123642   123642              
  Branches    14954    14954              
==========================================
- Hits        90825    90822       -3     
- Misses      31820    31822       +2     
- Partials      997      998       +1     

Flag	Coverage Δ
admin-tests	54.38% <ø> (-0.03%)	⬇️
e2e-tests	73.45% <ø> (-0.01%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[troyciesco]

@EvanHahn i'm gonna close this because this file was moved to a different repo (I made a PR already and added you as reviewer)