Bump upload-artifact version

[lawrence-forooghian]

Jobs seem to be randomly failing now that it’s deprecated; e.g. this job gave

Error: This request has been automatically failed because it uses a deprecated version of actions/upload-artifact: v3. Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/

Summary by CodeRabbit

• Chores
  • Updated GitHub Actions workflow configuration to use the latest version of the upload artifact action.

[coderabbitai]

Walkthrough

The pull request involves updating the GitHub Actions workflow configuration in the .github/workflows/check-pod.yaml file. Specifically, the change upgrades the upload-artifact action from version 3 to version 4. This modification ensures the workflow uses the latest version of the artifact upload action, maintaining compatibility with GitHub's current CI/CD infrastructure.

Changes

File	Change Summary
.github/workflows/check-pod.yaml	Upgraded actions/upload-artifact from v3 to v4

Possibly related issues

• ably/ably-cocoa#1969: This issue directly relates to the PR, as it highlights the deprecation of older versions of actions/upload-artifact. The current PR proactively addresses the need to upgrade to a newer action version.

Poem

🐰 A Rabbit's CI Update Delight 🚀

Workflows dance with actions so bright,
From v3 to v4, we take flight!
Artifacts uploaded with grace and ease,
GitHub's latest magic never fails to please.
Hop, hop, hurray for smooth CI might! 🌟

Finishing Touches

• 📝 Generate Docstrings

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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 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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

.github/workflows/check-pod.yaml (1)

Line range hint 12-12: Consider updating the checkout action version.

The workflow is using an outdated version of actions/checkout@v2. Consider upgrading to v4 for improved performance and security.

-      - uses: actions/checkout@v2
+      - uses: actions/checkout@v4

For reference, see the checkout action changelog.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between cbdc913 and 8f6ec60.

📒 Files selected for processing (1)

• .github/workflows/check-pod.yaml (1 hunks)

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

• GitHub Check: check (macOS, test_macOS)
• GitHub Check: check (tvOS, test_tvOS17_2)
• GitHub Check: check (iOS, test_iOS17_2)
• GitHub Check: build
• GitHub Check: check
• GitHub Check: check

🔇 Additional comments (1)

.github/workflows/check-pod.yaml (1)

55-55: LGTM! Good upgrade to address the deprecated action.

The update from upload-artifact@v3 to v4 is necessary and will resolve the job failures caused by the deprecated version.

[lawrence-forooghian]

I suggest that we merge this one since the check-pod workflow is now passing; tests will be fixed in #2008.