chore(deps): bump actions/upload-pages-artifact v3 → v5 (supersedes #76)

[kienbui1995]

What

Bumps actions/upload-pages-artifact from v3 to v5 in .github/workflows/pages.yml.

Why

Supersedes #76. That PR was opened by Dependabot and its SonarCloud Scan check fails because Dependabot-triggered workflows don't receive SONAR_TOKEN — same GitHub-level secret scoping issue as #75. Re-submitting from a regular branch so the scan can authenticate.

How

One-line change: @v3 → @v5.

The v4 release excludes hidden files (dotfiles) from the artifact by default. This workflow uploads docs/site/, which contains only index.html — no dotfiles — so the breaking change does not affect this pipeline.

Test plan

• All CI checks pass on this PR, including SonarCloud Scan
• After merge, verify the next push to main that matches the Pages path filter successfully deploys
• Close ci: bump actions/upload-pages-artifact from 3 to 5 #76

https://claude.ai/code/session_01R2n6wKqFkYPvHkwaip8EnJ

Summary by CodeRabbit

• Chores
  • Updated the GitHub Pages deployment workflow to use a newer release of the upload artifact action (bumped from v3 to v5), keeping the artifact upload settings unchanged. This refreshes deployment tooling to align with the latest supported action version and reduces maintenance risk.

[gemini-code-assist]

Note

Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 268b76ba-d076-46dc-b9ab-30139874cd13

📥 Commits

Reviewing files that changed from the base of the PR and between beb3623 and 59dad9d.

⛔ Files ignored due to path filters (1)

• mc/Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (1)

• .github/workflows/pages.yml

✅ Files skipped from review due to trivial changes (1)

• .github/workflows/pages.yml

---

📝 Walkthrough

Walkthrough

Updated the GitHub Pages workflow: bumped actions/upload-pages-artifact from v3 to v5. Artifact upload configuration (with.path: _site) is unchanged. This is a minor CI action version upgrade.

Changes

Cohort / File(s)	Summary
GitHub Actions: Pages workflow ​.github/workflows/pages.yml	Bumped actions/upload-pages-artifact from v3 to v5; no other workflow inputs or the with.path: _site setting changed. New upstream releases include an updated upload-artifact dependency and an include-hidden-files input (not used here).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested labels

dependencies, github_actions

Poem

🐰 A tiny hop from three to five,
I nudged the workflow so Pages thrive.
Artifacts still go to _site with cheer,
A quiet update — biscuits and beer. 🍪🎉

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: bumping actions/upload-pages-artifact from v3 to v5, and includes context about superseding PR #76.
Description check	✅ Passed	The description covers What, Why, and How sections clearly. However, the Test plan section uses checkboxes rather than confirming completion, and references an external URL that seems out of scope for a PR description.
Linked Issues check	✅ Passed	The PR fulfills all coding requirements from issue #76: upgrades actions/upload-pages-artifact to v5, accounts for v4's breaking change (dotfile exclusion), and verifies workflow compatibility.
Out of Scope Changes check	✅ Passed	The PR contains only the single-line change required to bump the action version; no extraneous modifications are present.
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 chore/bump-upload-pages-artifact-v5

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[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