chore(deps): update actions/upload-pages-artifact action to v5

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
actions/upload-pages-artifact	action	major	v4 → v5

---

Release Notes

actions/upload-pages-artifact (actions/upload-pages-artifact)

v5.0.0

Compare Source

Changelog

• Update upload-artifact action to version 7 @​Tom-van-Woudenberg (#​139)
• feat: add include-hidden-files input @​jonchurch (#​137)

See details of all code changes since previous release.

v5

Compare Source

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[doubleword-code]

Summary

This PR updates the actions/upload-pages-artifact GitHub Action from v4 to v5 in the documentation deployment workflow. The update is sourced from the official actions organization repository and introduces backward-compatible improvements: an internal upgrade to upload-artifact v7 and a new optional include-hidden-files input parameter. Verdict: Ready to approve — this is a standard dependency maintenance change with no identified risks.

Research notes

• v5.0.0 release notes (https://github.com/actions/upload-pages-artifact/releases/tag/v5.0.0): Published April 10, 2026. Changes include updating the underlying upload-artifact action to version 7 and adding the include-hidden-files input. No breaking changes documented.
• Action marketplace page (https://github.com/actions/upload-pages-artifact): Official GitHub-maintained composite action for packaging artifacts destined for GitHub Pages deployment. MIT licensed.
• GitHub Actions security guidance: Using official actions from the actions/ org with major-version pinning (e.g., @v5) aligns with recommended practices for supply chain security.

Suggested next steps

No action required. This PR can be merged as-is. If desired for enhanced supply chain security, the team could consider adopting commit-SHA pinning for actions in a separate initiative, but this is not a blocker for the current update.

General findings

None. The single-line change is correct, follows the existing workflow patterns in the repository, and references an officially-maintained action with no known security advisories or breaking changes.