chore: upgrade upload-artifact@v4

[huhuanming]

Summary by CodeRabbit

• Chores
  • Updated GitHub Actions workflow files to use the latest version of actions/upload-artifact and actions/download-artifact actions across multiple workflow configurations
  • Version upgrades performed for iOS, web, Android, desktop, extension, and release workflows
  • No functional changes to the underlying workflow logic or processes were made

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[coderabbitai]

Walkthrough

The pull request encompasses updates to multiple GitHub Actions workflow files across the repository. The primary modification is a consistent upgrade of the actions/upload-artifact action from version 3 to version 4 in various release and build workflows. These changes span workflows for iOS, web, Android, desktop, extensions, and other platform-specific release processes. The updates appear to be a systematic version bump for artifact handling actions.

Changes

File	Change Summary
.github/workflows/bundlediff-ios.yml	Updated actions/upload-artifact from v3 to v4 in build jobs, updated actions/download-artifact to v4.1.7
.github/workflows/bundlediff-web.yml	Updated actions/upload-artifact from v3 to v4 in build jobs, updated actions/download-artifact to v4.1.7
.github/workflows/release-android-debug.yml	Updated actions/upload-artifact from v3 to v4 in multiple steps
.github/workflows/release-desktop-mas.yml	Updated actions/upload-artifact from v3 to v4
.github/workflows/release-desktop-snap.yml	Updated actions/upload-artifact from v3 to v4
.github/workflows/release-desktop-winms.yml	Updated actions/upload-artifact from v3 to v4 in two artifact upload steps
.github/workflows/release-desktop.yml	Updated actions/upload-artifact from v3 to v4 in multiple artifact upload steps
.github/workflows/release-ext.yml	Updated actions/upload-artifact from v3 to v4
.github/workflows/release-ios-debug.yml	Updated actions/upload-artifact from v3 to v4
.github/workflows/release-web.yml	Updated actions/upload-artifact from v3 to v4

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e10d090 and fdb8e83.

📒 Files selected for processing (10)

• .github/workflows/bundlediff-ios.yml (2 hunks)
• .github/workflows/bundlediff-web.yml (2 hunks)
• .github/workflows/release-android-debug.yml (1 hunks)
• .github/workflows/release-desktop-mas.yml (1 hunks)
• .github/workflows/release-desktop-snap.yml (1 hunks)
• .github/workflows/release-desktop-winms.yml (1 hunks)
• .github/workflows/release-desktop.yml (1 hunks)
• .github/workflows/release-ext.yml (1 hunks)
• .github/workflows/release-ios-debug.yml (1 hunks)
• .github/workflows/release-web.yml (1 hunks)

🧰 Additional context used

🪛 yamllint (1.35.1)

.github/workflows/release-android-debug.yml

[error] 114-114: trailing spaces

(trailing-spaces)

⏰ Context from checks skipped due to timeout of 90000ms (5)

• GitHub Check: release-desktop (20.x)
• GitHub Check: lint (20.x)
• GitHub Check: unittest (20.x)
• GitHub Check: Analyze (javascript-typescript)
• GitHub Check: Analyze (java-kotlin)

🔇 Additional comments (10)

.github/workflows/release-android-debug.yml (1)

102-102: LGTM! The upgrade to upload-artifact@v4 looks good.

The change consistently upgrades all three upload steps to v4. This new version brings performance improvements and better error handling.

Let's verify the compatibility with v4. Run this check:

Also applies to: 109-109, 116-116

✅ Verification successful

All upload-artifact actions consistently use v4 across the codebase ✅

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check if any workflow files still use older versions of upload-artifact
rg -l "uses: actions/upload-artifact@v[1-3]"

Length of output: 46

---

Script:

#!/bin/bash
# Show all uses of upload-artifact with surrounding context
rg -C 2 "uses: actions/upload-artifact@" .github/workflows/

Length of output: 6257

.github/workflows/release-ios-debug.yml (1)

115-115: LGTM! The upgrade to upload-artifact@v4 is consistent.

The change aligns with the v4 upgrade pattern seen in other workflows.

.github/workflows/bundlediff-ios.yml (1)

60-60: LGTM! The upgrade pattern matches the project standard.

Both upload steps are consistently upgraded to v4.

Also applies to: 111-111

.github/workflows/bundlediff-web.yml (1)

60-60: LGTM! The v4 upgrade is properly implemented.

Both upload steps are upgraded to v4, maintaining consistency with other workflows.

Also applies to: 111-111

.github/workflows/release-ext.yml (1)

108-108: LGTM! The upgrade follows the established pattern.

The upload step is properly upgraded to v4.

.github/workflows/release-web.yml (1)

102-102: LGTM! Upgrade to upload-artifact@v4 looks good.

The upgrade aligns with the latest version. The action maintains backward compatibility with v3.

Let's verify the compatibility of v4 with the current usage:

✅ Verification successful

Upload-artifact v4 upgrade is safe to use

This workflow only uploads artifacts and doesn't download any, so the v4 breaking changes won't affect it.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify compatibility of upload-artifact@v4 with current usage

# Check the action's release notes and breaking changes
gh api repos/actions/upload-artifact/releases/latest

Length of output: 2230

---

Script:

#!/bin/bash
# Get the v4.0.0 release to check for breaking changes from v3
gh api repos/actions/upload-artifact/releases/tags/v4.0.0

Length of output: 3248

---

Script:

#!/bin/bash
# Check for artifact action usage in the workflow file
cat .github/workflows/release-web.yml

Length of output: 4537

.github/workflows/release-desktop-snap.yml (1)

116-116: LGTM! Upgrade to upload-artifact@v4 looks good.

The upgrade matches the changes in other workflow files.

.github/workflows/release-desktop-winms.yml (1)

129-129: LGTM! Both upload-artifact@v4 upgrades look good.

The upgrades are consistent with the changes across other workflow files.

Also applies to: 136-136

.github/workflows/release-desktop.yml (1)

129-129: LGTM! All five upload-artifact@v4 upgrades look good.

The upgrades maintain consistency across all artifact upload steps.

Also applies to: 136-136, 143-143, 150-150, 157-157

.github/workflows/release-desktop-mas.yml (1)

163-163: LGTM! Upgrade to upload-artifact@v4 looks good.

The upgrade aligns with changes in other workflow files.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary or Summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.