Bump actions/upload-artifact from 5 to 6

[dependabot]

Bumps actions/upload-artifact from 5 to 6.

Release notes

Sourced from actions/upload-artifact's releases.

v6.0.0

v6 - What's new

[!IMPORTANT] actions/upload-artifact@v6 now runs on Node.js 24 (runs.using: node24) and requires a minimum Actions Runner version of 2.327.1. If you are using self-hosted runners, ensure they are updated before upgrading.

Node.js 24

This release updates the runtime to Node.js 24. v5 had preliminary support for Node.js 24, however this action was by default still running on Node.js 20. Now this action by default will run on Node.js 24.

What's Changed

• Upload Artifact Node 24 support by @​salmanmkc in actions/upload-artifact#719
• fix: update @​actions/artifact for Node.js 24 punycode deprecation by @​salmanmkc in actions/upload-artifact#744
• prepare release v6.0.0 for Node.js 24 support by @​salmanmkc in actions/upload-artifact#745

Full Changelog: actions/upload-artifact@v5.0.0...v6.0.0

Commits

• b7c566a Merge pull request #745 from actions/upload-artifact-v6-release
• e516bc8 docs: correct description of Node.js 24 support in README
• ddc45ed docs: update README to correct action name for Node.js 24 support
• 615b319 chore: release v6.0.0 for Node.js 24 support
• 017748b Merge pull request #744 from actions/fix-storage-blob
• 38d4c79 chore: rebuild dist
• 7d27270 chore: add missing license cache files for @​actions/core, @​actions/io, and mi...
• 5f643d3 chore: update license files for @​actions/artifact@​5.0.1 dependencies
• 1df1684 chore: update package-lock.json with @​actions/artifact@​5.0.1
• b5b1a91 fix: update @​actions/artifact to ^5.0.0 for Node.js 24 punycode fix
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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)

---

Resolves #745
Resolves #744
Resolves actions/upload-artifact#719
Resolves actions/upload-artifact#744
Resolves actions/upload-artifact#745

[github-actions]

🤖 Claude Code Review

Code Review Analysis

Overview

This PR updates the GitHub Actions upload-artifact action from v5 to v6 across three workflow files. This is a straightforward dependency update.

---

Review Checklist Results

Code Quality

• ✅ Code follows style guide: The changes are minimal YAML updates in GitHub workflow files. The formatting is consistent with existing style.

• ✅ No commented-out code: No commented code present in the diff.

• ✅ Meaningful variable names: Not applicable - only version number changes.

• ✅ DRY principle followed: The change is consistently applied across all three workflow files (darwin, linux, windows), maintaining parallel structure.

• ✅ Identify Defects: No bugs, logic errors, or security vulnerabilities introduced. This is a standard action version bump. Note: The upload-artifact@v6 action has breaking changes from v5 (different artifact handling), but this appears to be intentional based on recent commit history showing this as a deliberate upgrade.

• ✅ Project memory configuration: No .claude/CLAUDE.md file found in the repository to consider.

Testing

• ✅ Unit tests for new functions: Not applicable - no new functions added.

• ✅ Integration tests for new endpoints: Not applicable - no new endpoints.

• ✅ Edge cases covered: Not applicable - this is an infrastructure change.

• ⚠️ Test coverage > 80%: Cannot verify from this diff alone. The workflows themselves run pytest with coverage, so this change doesn't affect test coverage directly.

Documentation

• ✅ Readme updated if needed: Not needed - this is an internal CI/CD change that doesn't affect users.

• ✅ API docs updated: Not applicable.

• ✅ Inline comments for complex logic: Not applicable - the change is self-explanatory.

• ⚠️ CHANGELOG.md updated: Cannot verify if CHANGELOG was updated as it's not included in the diff. For a dependency update like this, it may warrant a CHANGELOG entry depending on project conventions.

• ✅ Markdown formatting: Not applicable - no markdown files modified.

Security

• ✅ No hardcoded credentials: None present.

• ✅ Input validation implemented: Not applicable.

• ✅ Proper error handling: Not applicable.

• ✅ No sensitive data in logs: None present.

• ✅ No license files (.lic) or AQAAAD strings: None present.

---

Summary

Status: ✅ APPROVED

This is a clean, straightforward dependency update that upgrades the actions/upload-artifact action from v5 to v6 consistently across all three platform-specific pytest workflows (Darwin, Linux, Windows).

Considerations:

1. Breaking Changes: The upload-artifact@v6 action has breaking changes from v5, particularly around artifact naming and merging. Verify that downstream jobs or processes that download these artifacts are compatible with v6's behavior.

2. CHANGELOG: Consider documenting this infrastructure update in CHANGELOG.md if your project tracks such changes.

3. Testing: Once merged, monitor the workflow runs to ensure artifacts are uploaded and retrievable as expected.

No blocking issues identified. ✅

Automated code review analyzing defects and coding standards

[github-actions]

Coverage report

This PR does not seem to contain any modification to coverable code.

[github-actions]

🤖 Claude Code Review

Code Review Analysis

Pull Request Summary

This PR updates the actions/upload-artifact GitHub Action from v5 to v6 across three workflow files for pytest runs on different platforms (Darwin/macOS, Linux, and Windows).

---

Review Checklist Results

Code Quality

• ✅ Code follows style guide: The changes are minimal version updates to GitHub Actions. No Python or application code style issues.

• ✅ No commented-out code: No commented code present in the diff.

• ✅ Meaningful variable names: N/A - Only GitHub Actions version updates.

• ✅ DRY principle followed: The same change is consistently applied across all three platform workflows, which is appropriate.

• ✅ Identify Defects: No bugs, logic errors, or security vulnerabilities introduced. This is a straightforward dependency version bump. Note: actions/upload-artifact@v6 has breaking changes from v5, but the usage in these workflows appears compatible (using name and path parameters which are still supported).

• ✅ Project memory configuration: No .claude/CLAUDE.md file found to consider.

Files Changed:

• .github/workflows/pytest-darwin.yaml:93
• .github/workflows/pytest-linux.yaml:93
• .github/workflows/pytest-windows.yaml:86

Testing

• ⚠️ Unit tests for new functions: N/A - No application code changes, only CI/CD configuration.

• ⚠️ Integration tests for new endpoints: N/A - No new endpoints.

• ⚠️ Edge cases covered: N/A - GitHub Actions version update.

• ⚠️ Test coverage > 80%: Cannot be determined from this diff, but the change doesn't affect test coverage.

Note: Testing criteria are not applicable to GitHub Actions version updates. The workflows themselves will validate the change.

Documentation

• ✅ README updated if needed: No README update needed for internal CI/CD dependency updates.

• ✅ API docs updated: N/A - No API changes.

• ✅ Inline comments for complex logic: N/A - GitHub Actions YAML doesn't require additional comments for version bumps.

• ❌ CHANGELOG.md updated: No CHANGELOG.md update detected in the diff. This dependency update should be documented.

• ✅ Markdown formatting: N/A - No markdown files changed.

Security

• ✅ No hardcoded credentials: No credentials in the diff.

• ✅ Input validation implemented: N/A - No input handling code.

• ✅ Proper error handling: N/A - GitHub Actions handles errors internally.

• ✅ No sensitive data in logs: No sensitive data introduced.

• ✅ No license files (.lic) or AQAAAD strings: No license files or suspicious strings detected.

---

Summary

Overall Assessment: ✅ APPROVED with minor documentation note

This is a clean, straightforward dependency update that bumps actions/upload-artifact from v5 to v6 consistently across all three platform-specific pytest workflows.

Required Action:

• ❌ CHANGELOG.md should be updated to document this infrastructure change (e.g., "Updated actions/upload-artifact from v5 to v6 in CI/CD workflows").

Recommendations:

1. Verify that the v6 action works as expected in CI/CD runs since v6 has some breaking changes from v5 (though your usage appears compatible).
2. Consider if this aligns with the recent commit history showing a similar bump from v5 to v6 (commit 96ed9a8).

No blocking issues found. The code quality is good, and the changes are minimal and consistent.

Automated code review analyzing defects and coding standards