Upgrade GitHub Actions to latest versions

[salmanmkc]

Summary

Upgrade GitHub Actions to their latest versions for improved features, bug fixes, and security updates.

Changes

Action	Old Version(s)	New Version	Release	Files
actions/upload-pages-artifact	v3	v4	Release	docs.yml

Why upgrade?

Keeping GitHub Actions up to date ensures:

• Security: Latest security patches and fixes
• Features: Access to new functionality and improvements
• Compatibility: Better support for current GitHub features
• Performance: Optimizations and efficiency improvements

Security Note

Actions that were previously pinned to commit SHAs remain pinned to SHAs (updated to the latest release SHA) to maintain the security benefits of immutable references.

Testing

These changes only affect CI/CD workflow configurations and should not impact application functionality. The workflows should be tested by running them on a branch before merging.

[coderabbitai]

📝 Walkthrough

Walkthrough

Updated the GitHub Actions workflow to bump actions/upload-pages-artifact from v3 to v4; no other workflow paths or behavior were changed.

Changes

Cohort / File(s)	Summary
GitHub Actions Workflow Update \.github/workflows/docs\.yml	Bumped actions/upload-pages-artifact from @v3 to @v4; no other edits to workflow steps or paths.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I hopped through CI with a curious grin,
Swapped three for four—let the uploads begin! 🐇
Little change, lighter stride,
Pages sail on an updated tide,
A rabbit’s cheer for the workflow win! ✨

🚥 Pre-merge checks | ✅ 2

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately reflects the main change: upgrading GitHub Actions workflow dependencies to newer versions.
Description check	✅ Passed	The description is directly related to the changeset, providing clear context about the upgrade motivation, specific version changes, and testing considerations.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

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

---

No actionable comments were generated in the recent review. 🎉

---

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

[greptile-apps]

Greptile Overview

Greptile Summary

This PR updates the documentation GitHub Actions workflow to use actions/upload-pages-artifact@v4 instead of @v3 when uploading the built Sphinx HTML output (doc/_build/html) for GitHub Pages deployment.

The change is isolated to .github/workflows/docs.yml and affects only the artifact upload step in the build job; the downstream deploy job continues to deploy via actions/deploy-pages@v4 using the uploaded Pages artifact.

Confidence Score: 5/5

• This PR is safe to merge with minimal risk.
• The diff is a single, straightforward GitHub Actions version bump for actions/upload-pages-artifact (v3→v4) with no other workflow logic changes; the workflow remains internally consistent with actions/deploy-pages@v4 and the artifact path is unchanged.
• No files require special attention

Important Files Changed

Filename	Overview
.github/workflows/docs.yml	Bumps actions/upload-pages-artifact from v3 to v4 in the docs workflow; no functional issues found in the change itself.

Sequence Diagram

sequenceDiagram
  participant Dev as Developer
  participant GH as GitHub Actions
  participant DocsWF as .github/workflows/docs.yml
  participant Upload as actions/upload-pages-artifact@v4
  Dev->>GH: Push / PR update
  GH->>DocsWF: Trigger docs workflow
  DocsWF->>Upload: Upload built docs as Pages artifact
  Upload-->>GH: Store artifact for Pages deployment
  GH-->>Dev: Workflow status & logs

Loading

[greptile-apps]

_{1 file reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

_{1 file reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

_{1 file reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}