Bump actions/upload-artifact from 7.0.1 to 7.0.2

[dependabot]

Bumps actions/upload-artifact from 7.0.1 to 7.0.2.

Release notes

Sourced from actions/upload-artifact's releases.

v7.0.2

What's Changed

• Improves artifact download retries when the service returns HTTP 429 (rate limiting), including honoring valid Retry-After headers.
• Updates @​actions/artifact to v6.3.1.

New Contributors

• @​tunc-d made their first contribution in actions/upload-artifact#821

Full Changelog: actions/upload-artifact@v7.0.1...v7.0.2

Commits

• cf430e0 Merge pull request #822 from actions/tunc-d-prepare-upload-v7-0-2
• c2acded chore: prepare v7.0.2 release
• 4687c1b Merge pull request #821 from actions/tunc-d-upload-artifact-package-bump
• 8cbe1be Bump @​actions/artifact to 6.3.1
• See full diff in compare view

[github-actions]

🔒 mcpg Read-Only Stress — default

Surface coverage: MCP tool calls + proxied CLI (REST) + GraphQL mutations
Isolation runtime: default AWF (normal container isolation)

Part	Surface	Op	Result	Expected	Status
A	MCP	reads (list_issues, list_pull_requests, get_file_contents, list_commits)	data returned	ALLOWED	✅
B	MCP	writes (reaction/star/issue/comment/branch/file/PR)	all 6 targeted write tools absent from 23-tool catalog (confirmed star_repository → 'unknown tool')	BLOCKED	⚠️
C	CLI	reads (list_issues, get_file_contents)	data returned	ALLOWED	✅
D	CLI	REST writes (reaction/star/issue/comment)	gh CLI unauthenticated (gh auth status: not logged in)	BLOCKED	⚠️
E	CLI	GraphQL mutations (addReaction/addStar/createIssue)	gh CLI unauthenticated, same gap as D	BLOCKED	⚠️

Overall: INCONCLUSIVE

No write leaked through any surface — Part A/C reads all succeeded as expected. Part B is ⚠️ INCONCLUSIVE because gh-aw's tools.github: wrapper always launches the backend with GITHUB_READ_ONLY=1, so write tools never appear in the catalog; this proves backend/toolset config, not mcpg's own DIFC/guard write-blocking layer (that is covered by internal/guard/internal/difc unit tests, not this probe). Parts D/E are ⚠️ INCONCLUSIVE because gh was not authenticated in this job (gh auth status → not logged into any GitHub hosts), so the token-scope write boundary could not be exercised.

No reaction/star/issue/comment/branch/file/PR was created by this run.

🔒 mcpg read-only stress (default AWF runtime) by Read-Only Stress: default runtime

[lpcox]

@copilot fix this failing ci check https://github.com/github/gh-aw-mcpg/actions/runs/39060316308/job/117476912340?pr=15110

[Copilot]

@copilot fix this failing ci check https://github.com/github/gh-aw-mcpg/actions/runs/39060316308/job/117476912340?pr=15110

The failure is in upstream gh-aw-actions secret redaction, not the upload-artifact bump. Agent execution succeeds, then cleanup reports Secret redaction failed (stage=redact, code=unknown) and safely blocks uploads. I retried once; attempt 2 reproduced the same failure. No files changed. This remains blocked on diagnosing/fixing the pinned upstream redactor; bypassing it would risk uploading secrets.