Skip to content

chore(deps): Bump actions/upload-pages-artifact from 3 to 5 - #35

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/actions/upload-pages-artifact-5
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/actions/upload-pages-artifact-5

chore(deps): Bump actions/upload-pages-artifact from 3 to 5

0fd739d
Select commit
Loading
Failed to load commit list.
GitzillaBot / gitzilla succeeded Sep 15, 2026 in 11s

Gitzilla review complete

No actionable issues found.

This PR is a straightforward, low-risk dependency bump that updates actions/upload-pages-artifact from major version 3 to 5 within the GitHub Actions Pages deploy workflow. The version reference is the only substantive change in the workflow file, and it aligns with the maintainers' published guidance for the action's major versions. Because the upgrade is confined to a single uses: line and does not alter any inputs, triggers, permissions, or surrounding steps, the behavioral surface of the workflow is preserved while inheriting any bug fixes, dependency updates, and deprecation cleanups shipped in versions 4 and 5.

The most important consideration for this kind of change is the potential for breaking changes across major versions, but the review found no indicators of incompatibility in the way the action is consumed here. The workflow does not pass any inputs to the action, relies solely on its default behavior of uploading the configured Pages artifact, and does not reference any outputs or downstream step semantics that have shifted between v3 and v5. There is also no evidence of workflow files being pinned to commit SHAs elsewhere in the repository that would need to be reconciled, and the permissions block remains appropriate for the action's requirements.

Overall, the change looks sound. No findings were raised during review. As a general recommendation for future bumps, it would be worthwhile to consult the actions/upload-pages-artifact v4 and v5 release notes before merging any further major upgrades to confirm there are no new required inputs or behavioral changes, and to consider pinning to a specific commit SHA in addition to the major-version tag for supply-chain hardening — but neither is required for this PR as submitted.

Details

No actionable issues found in this review pass.