chore(deps): bump actions/upload-pages-artifact from 3.0.1 to 4.0.0

[dependabot]

Bumps actions/upload-pages-artifact from 3.0.1 to 4.0.0.

Release notes

Sourced from actions/upload-pages-artifact's releases.

v4.0.0

What's Changed

• Potentially breaking change: hidden files (specifically dotfiles) will not be included in the artifact by @​tsusdere in actions/upload-pages-artifact#102 If you need to include dotfiles in your artifact: instead of using this action, create your own artifact according to these requirements https://github.com/actions/upload-pages-artifact?tab=readme-ov-file#artifact-validation
• Pin actions/upload-artifact to SHA by @​heavymachinery in actions/upload-pages-artifact#127

Full Changelog: actions/upload-pages-artifact@v3.0.1...v4.0.0

Commits

• 7b1f4a7 Merge pull request #127 from heavymachinery/pin-sha
• 4cc19c7 Pin actions/upload-artifact to SHA
• 2d163be Merge pull request #107 from KittyChiu/main
• c704843 fix: linted README
• 9605915 Merge pull request #106 from KittyChiu/kittychiu/update-readme-1
• e59cdfe Update README.md
• a2d6704 doc: updated usage section in readme
• 984864e Merge pull request #105 from actions/Jcambass-patch-1
• 45dc788 Add workflow file for publishing releases to immutable action package
• efaad07 Merge pull request #102 from actions/hidden-files
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[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

[jbdevprimary]

🔧 CI Fix Suggestion

Branch: dependabot/github_actions/actions/upload-pages-artifact-4.0.0

1. Root Cause: The download-artifact step failed because an artifact named build-output was not found in the specified workflow run. This indicates the previous job responsible for uploading this artifact either failed, was misconfigured, or did not run.

2. Suggested Fix: In the job that builds your project (e.g., a build job), ensure the actions/upload-artifact step is present and configured correctly. The name must match the download step.

   # In your 'build' job (or the job that generates the artifact)
   - name: Upload build artifact
     uses: actions/upload-artifact@v4 # Use a compatible version
     with:
       name: build-output # <-- This name MUST match
       path: dist/         # The directory to upload

   Also, ensure the job running the download-artifact step has a needs: <your-build-job-name> dependency.

3. Commands to Verify:

   1. Push a new commit to your branch to re-run the entire workflow.
   2. After the build job completes, check its logs for a message confirming the upload, such as Artifact name: build-output has been successfully uploaded.

---

_{🤖 Generated by Ecosystem Fixer using Ollama GLM 4.6}