ci: Bump actions/deploy-pages from 4 to 5

[mtrezza]

Closes #1130

Bumps actions/deploy-pages from v4 to v5 across the release workflows (release-manual-docs.yml and release-publish.yml, 3 occurrences).

Changes

• v5.0.0: Updates the action's JavaScript runtime from Node.js 20 to Node.js 24 (Update Node.js version to 24.x actions/deploy-pages#404). This runtime upgrade is the sole reason for the major version bump.

Breaking Changes

None affecting these workflows. Verified action.yml between v4.0.5 and v5.0.0: the only difference is runs.using: 'node20' -> 'node24'. All inputs (token, timeout, error_count, reporting_interval, artifact_name, preview) and the page_url output are unchanged. Node.js 24 is supported on GitHub-hosted ubuntu-latest runners used by these jobs.

Code Changes Required

None — drop-in replacement, action version tag change only.

Summary by CodeRabbit

• Chores
  • Updated the documentation publishing process to use the latest GitHub Pages deployment action.
  • No changes to package publishing or documentation generation behavior.

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

Tip

• Keep pull requests small. Large PRs will be rejected. Break complex features into smaller, incremental PRs.
• Use Test Driven Development. Write failing tests before implementing functionality. Ensure tests pass.
• Group code into logical blocks. Add a short comment before each block to explain its purpose.
• We offer conceptual guidance. Coding is up to you. PRs must be merge-ready for human review.
• Our review focuses on concept, not quality. PRs with code issues will be rejected. Use an AI agent.
• Human review time is precious. Avoid review ping-pong. Inspect and test your AI-generated code.

Note

Please respond to review comments from AI agents just like you would to comments from a human reviewer. Let the reviewer resolve their own comments, unless they have reviewed and accepted your commit, or agreed with your explanation for why the feedback was incorrect.

Caution

Pull requests must be written using an AI agent with human supervision. Pull requests written entirely by a human will likely be rejected, because of lower code quality, higher review effort and the higher risk of introducing bugs. Please note that AI review comments on this pull request alone do not satisfy this requirement. Our CI and AI review are safeguards, not development tools. If many issues are flagged, rethink your development approach. Invest more effort in planning and design rather than using review cycles to fix low-quality code.

[mtrezza]

@coderabbitai review

[coderabbitai]

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[coderabbitai]

📝 Walkthrough

Walkthrough

GitHub Pages deployment steps in the manual documentation and release publishing workflows are updated from actions/deploy-pages@v4 to actions/deploy-pages@v5.

Changes

GitHub Pages deployment upgrade

Layer / File(s)	Summary
Update documentation deployment actions .github/workflows/release-manual-docs.yml, .github/workflows/release-publish.yml	The manual documentation deployment and Dart and Flutter documentation publishing jobs now use actions/deploy-pages@v5.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

• parse-community/Parse-SDK-Flutter#1127: Modifies GitHub Pages deployment steps in the same workflows.

---

Important

Pre-merge checks failed

Please resolve all errors before merging. Addressing warnings is optional.

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Engage In Review Feedback	❓ Inconclusive	No review-thread data is available in the repo, and the branch only shows a single version-bump commit; feedback engagement can’t be verified.	Need PR review comments or linked discussion showing the author responded to feedback (via commit or retraction) before marking this check pass/fail.

✅ Passed checks (6 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	The PR directly addresses issue #1130 by updating 'actions/deploy-pages' from v4 to v5 across both release workflows, matching the linked issue requirements.
Out of Scope Changes check	✅ Passed	All changes are in-scope, limited to updating action version tags in release workflow files with no extraneous modifications introduced.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Security Check	✅ Passed	The diff only bumps three actions/deploy-pages references from v4 to v5; no permissions, inputs, or code paths changed, and I found no new security-sensitive pattern.
Title check	✅ Passed	The title matches the PR scope and uses the required ci: prefix with a clear action version bump.
Description check	✅ Passed	The description covers the issue, approach, and change impact, but it omits the template's task checklist and boilerplate sections.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 44.42%. Comparing base (4baa3ea) to head (6243429).

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #1153   +/-   ##
=======================================
  Coverage   44.42%   44.42%           
=======================================
  Files          62       62           
  Lines        3730     3730           
=======================================
  Hits         1657     1657           
  Misses       2073     2073           

☔ View full report in Codecov by Harness.
📢 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.