ci: Bump actions/configure-pages from 5 to 6

[mtrezza]

Bumps the actions/configure-pages GitHub Action from v5 to v6 across the release workflows. Replaces #1132 (Dependabot) with a commit under the maintainer identity.

Changes

• v6.0.0: The action's JavaScript runtime was upgraded from Node 20 to Node 24. No action inputs or outputs were changed; there are no new required inputs and no defaults were altered.

Affected workflow files:

• .github/workflows/release-manual-docs.yml
• .github/workflows/release-publish.yml (2 occurrences)

In all cases the action is invoked as uses: actions/configure-pages@v6 with no with: inputs, so the runtime bump is the only relevant change.

Breaking Changes

None affecting these workflows. The only major-version change is the internal Node 20 -> Node 24 runtime upgrade, which is transparent to GitHub-hosted ubuntu-latest runners used here. The action's input/output interface is unchanged.

Code Changes Required

None -- drop-in replacement (workflow YAML version tag only).

Closes #1132

Summary by CodeRabbit

• Chores
  • Updated the documentation publishing workflow to use the latest GitHub Pages configuration action.
  • Applied the update consistently to both Dart and Flutter documentation deployments.

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

📝 Walkthrough

Walkthrough

The documentation publishing workflows update actions/configure-pages from version 5 to version 6 across manual, Dart, and Flutter Pages jobs.

Changes

GitHub Pages action upgrade

Layer / File(s)	Summary
Update Pages configuration actions .github/workflows/release-manual-docs.yml, .github/workflows/release-publish.yml	Manual, Dart, and Flutter documentation publishing jobs now use actions/configure-pages@v6 instead of @v5.

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

Possibly related PRs

• parse-community/Parse-SDK-Flutter#1127: Introduced the Pages publishing workflow that this update now advances to actions/configure-pages@v6.

---

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 repository-visible review thread or reply history exists; this is a straight workflow version bump, so review-engagement can’t be verified here.	Provide the PR review thread or GitHub conversation history showing the feedback, author response, and either a follow-up commit or reviewer retraction.

✅ Passed checks (6 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	The changes satisfy #1132 by bumping actions/configure-pages from v5 to v6 in all targeted workflows.
Out of Scope Changes check	✅ Passed	No unrelated code changes are present; the PR only updates the workflow action version in the specified docs-release jobs.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Security Check	✅ Passed	Only a version-tag bump from configure-pages@v5 to @v6; official action metadata shows identical inputs/outputs and only node20→node24 runtime change.
Title check	✅ Passed	The title uses the required ci: prefix and accurately summarizes the workflow dependency bump.
Description check	✅ Passed	The description covers the issue, approach, breaking changes, and closure, though it does not match the template headings exactly.

✨ 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 (0678293).

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #1154   +/-   ##
=======================================
  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.