ci: Fix release automation

[mtrezza]

New Pull Request Checklist

• I am not disclosing a vulnerability.
• I am creating this PR in reference to an issue.

Summary by CodeRabbit

• Chores
  • Updated build infrastructure dependencies to latest stable versions for improved compatibility and security.

[parse-github-assistant]

🚀 Thanks for opening this pull request! We appreciate your effort in improving the project. Please let us know once your pull request is ready for review.

[coderabbitai]

📝 Walkthrough

Walkthrough

Updates GitHub Actions in the release-automated workflow from v2 to v4 for checkout, setup-node, and cache. No changes to workflow logic or step structure.

Changes

Cohort / File(s)	Summary
GitHub Actions Upgrades \.github/workflows/release-automated.yml	Updated checkout, setup-node, and cache actions from v2 to v4

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Pre-merge checks and finishing touches

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description is incomplete. It only includes the checklist portion but omits critical sections: Issue Description (shows 'FILL_THIS_OUT'), Approach (empty), and TODOs (not addressed).	Complete the PR description by filling in the Issue Description section, providing a detailed Approach explaining the version upgrade rationale, and addressing relevant TODOs.
Title check	❓ Inconclusive	The title 'ci: Fix release automation' is vague and doesn't clearly describe what was fixed. It lacks specific details about the actual changes (GitHub Actions version upgrades).	Consider a more descriptive title like 'ci: Upgrade GitHub Actions to v4 in release workflow' to clearly indicate the specific changes made.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b22393c and b090f35.

📒 Files selected for processing (1)

• .github/workflows/release-automated.yml (2 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)

• GitHub Check: Xcode 16
• GitHub Check: Core Module, iOS 18
• GitHub Check: docs

🔇 Additional comments (3)

.github/workflows/release-automated.yml (3)

14-16: Approve: checkout@v4 upgrade is compatible.

The version bump to v4 is straightforward and the configuration (persist-credentials: false) remains compatible. This is a routine maintenance update.

---

17-20: Approve: setup-node@v4 upgrade is compatible.

The version bump to v4 maintains compatibility with the current configuration (Node 22 and npm caching). This is a routine maintenance update that enables npm dependency caching.

---

28-33: Approve: cache@v4 upgrade is compatible.

The version bump to v4 maintains compatibility with the cache configuration. The hash-based key strategy and restore-key pattern remain supported in v4, and the gem caching continues to complement the bundle install step.

---

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.}

[parseplatformorg]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[parseplatformorg]

🎉 This change has been released in version 6.0.0

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.65%. Comparing base (dd05d41) to head (b090f35).
⚠️ Report is 59 commits behind head on master.

Additional details and impacted files

@@             Coverage Diff             @@
##           master    #1871       +/-   ##
===========================================
+ Coverage   64.24%   82.65%   +18.41%     
===========================================
  Files         201      282       +81     
  Lines       23233    30622     +7389     
===========================================
+ Hits        14926    25312    +10386     
+ Misses       8307     5310     -2997     

☔ 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.