[dependabot]

Bumps actions/upload-artifact from 4.6.2 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

v7.0.1

What's Changed

• Update the readme with direct upload details by @​danwkennedy in actions/upload-artifact#795
• Readme: bump all the example versions to v7 by @​danwkennedy in actions/upload-artifact#796
• Include changes in typespec/ts-http-runtime 0.3.5 by @​yacaovsnc in actions/upload-artifact#797

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

v7.0.0

v7 What's new

Direct Uploads

Adds support for uploading single files directly (unzipped). Callers can set the new archive parameter to false to skip zipping the file during upload. Right now, we only support single files. The action will fail if the glob passed resolves to multiple files. The name parameter is also ignored with this setting. Instead, the name of the artifact will be the name of the uploaded file.

ESM

To support new versions of the @actions/* packages, we've upgraded the package to ESM.

What's Changed

• Add proxy integration test by @​Link- in actions/upload-artifact#754
• Upgrade the module to ESM and bump dependencies by @​danwkennedy in actions/upload-artifact#762
• Support direct file uploads by @​danwkennedy in actions/upload-artifact#764

New Contributors

• @​Link- made their first contribution in actions/upload-artifact#754

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

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.

... (truncated)

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
• 043fb46 Merge pull request #797 from actions/yacaovsnc/update-dependency
• 634250c Include changes in typespec/ts-http-runtime 0.3.5
• e454baa Readme: bump all the example versions to v7 (#796)
• 74fad66 Update the readme with direct upload details (#795)
• bbbca2d Support direct file uploads (#764)
• 589182c Upgrade the module to ESM and bump dependencies (#762)
• 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 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)

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: 8677a346-22db-4951-87a7-9deda8126e81

📥 Commits

Reviewing files that changed from the base of the PR and between 2ca6a48 and 8a1f63c.

📒 Files selected for processing: 4

• .github/workflows/campaign-windows-hermes.yml
• .github/workflows/mutation-gate.yml
• .github/workflows/playground.yml
• .github/workflows/release.yml

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 8 remain after this review.

📝 Summary

Summary by CodeRabbit

• Chores
  • Updated automated artifact uploads across campaign, mutation, iOS build, and release workflows. Artifact names, contents, and upload conditions remain unchanged; there are no changes to app features or behavior.

Four GitHub Actions workflows now use actions/upload-artifact@v7.0.2 for artifact uploads. This updates eight upload steps, including one step that previously used v4. Artifact names, paths, conditions, and upload options remain unchanged.

Suggested reviewers: krassx

Priority: ⬇️ Low

Change: Other

Merge Risk: ⚪ Minimal · up to 8a1f6

The artifact uploads are ready to merge after normal workflow checks; no actionable compatibility issue is established.

Security architecture risk: 🔵 Low · up to 8a1f6

No introduced permission expansion or weakened release control was identified. The upgraded action preserves archived uploads by default, and the publication gates remain unchanged. Residual uncertainty concerns end-to-end compatibility with the existing download action and externally configured publishing restrictions.

Retained concerns
No architecture-level concerns identified.

Security review details

Security Blast Radius

• inferred — The security-sensitive reach of this dependency change is the release tarballs consumed by npm publication and repository release creation. The changed uploader remains in the read-only check job rather than either privileged consumer job; no additional publication authority is granted by the diff.

Trust Boundaries and Controls

• observed — The workflow retains separate authorities: publish uses the npm-publish environment, a main-ref guard and id-token write permission; github-release instead has contents write permission. Dispatch inputs reach publishing commands through quoted environment variables, and the publication script validates dist-tag names. These controls are unchanged; the environment's deployed branch restrictions were not independently verified.

Resilience and Maintainability Implications

• observed — Release runs retain a shared concurrency group without cancelling an in-progress release. Artifact upload fails when no files exist, and publication rejects missing expected tarballs rather than repacking them inside the privileged job.

Pre-merge checks: 5

Check name	Status	Explanation
Title check		The title clearly identifies the dependency and the version update from 4.6.2 to 7.0.2, which matches the pull request objective and workflow changes.
Description check		The description explains the dependency update and includes relevant release notes, which directly match the changeset.
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (4 skipped: 4 unsupported.)

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

_{Comment @coderabbitai help to get the list of available commands.}