UN-3413 [MISC] Upgrade GitHub Actions from deprecated Node.js 20 runtime#1916
UN-3413 [MISC] Upgrade GitHub Actions from deprecated Node.js 20 runtime#1916muhammad-ali-e merged 1 commit intomainfrom
Conversation
…2/24 - actions/create-github-app-token: v2 -> v3 (Node 22) - stefanzweifel/git-auto-commit-action: v5 -> v7 (Node 24) - slackapi/slack-github-action: v2.1.0 -> v3.0.1 (Node 24)
WalkthroughGitHub Actions workflow files were updated to use newer versions of external actions. Four workflows had their action dependencies bumped: Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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. Comment |
|
Test ResultsSummary
Runner Tests - Full Report
SDK1 Tests - Full Report
|
|
| Filename | Overview |
|---|---|
| .github/workflows/create-release.yaml | Bumps actions/create-github-app-token from v2 to v3 (Node 20 → 22); no logic changes. |
| .github/workflows/uv-lock-automation.yaml | Bumps stefanzweifel/git-auto-commit-action from v5 to v7 (Node 20 → 24), skipping v6; only basic commit inputs are used, unaffected by v6 removals. |
| .github/workflows/release-notification.yaml | Bumps slackapi/slack-github-action from v2.1.0 to v3.0.1 (Node 20 → 24); uses unchanged incoming-webhook technique. |
| .github/workflows/production-build.yaml | Bumps slackapi/slack-github-action from v2.1.0 to v3.0.1 (Node 20 → 24); uses unchanged incoming-webhook technique with payload and env-based webhook URL. |
Flowchart
%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[create-release.yaml] -->|uses| B["actions/create-github-app-token\nv2 → v3 ✅ Node 20→22"]
C[uv-lock-automation.yaml] -->|uses| D["stefanzweifel/git-auto-commit-action\nv5 → v7 ✅ Node 20→24"]
E[release-notification.yaml] -->|uses| F["slackapi/slack-github-action\nv2.1.0 → v3.0.1 ✅ Node 20→24"]
G[production-build.yaml] -->|uses| H["slackapi/slack-github-action\nv2.1.0 → v3.0.1 ✅ Node 20→24"]
F -->|incoming-webhook| I[Slack]
H -->|incoming-webhook| I
Reviews (1): Last reviewed commit: "[MISC] Upgrade GitHub Actions from depre..." | Re-trigger Greptile



What
Why
How
create-release.yamlactions/create-github-app-token@v2@v3uv-lock-automation.yamlstefanzweifel/git-auto-commit-action@v5@v7release-notification.yamlslackapi/slack-github-action@v2.1.0@v3.0.1production-build.yamlslackapi/slack-github-action@v2.1.0@v3.0.1Can this PR break any existing features. If yes, please list possible items. If no, please explain why. (PS: Admins do not merge the PR without this section filled)
create-github-app-token@v3: Proxy handling changed (we don't use proxies), requires runner v2.327.1+ (met byubuntu-latest).git-auto-commit-action@v7: v6 removedcreate_branch/skip_checkout/skip_fetchinputs, v7 restored them. We don't use any of these inputs.slack-github-action@v3.0.1: Only breaking change is Node 24 runtime requirement (met byubuntu-latest). Theincoming-webhooktechnique and inputs are unchanged.Database Migrations
Env Config
Relevant Docs
Related Issues or PRs
Dependencies Versions
actions/create-github-app-token: v2 → v3stefanzweifel/git-auto-commit-action: v5 → v7slackapi/slack-github-action: v2.1.0 → v3.0.1Notes on Testing
Checklist
I have read and understood the Contribution Guidelines.