Update GitHub Actions to Use Latest Versions

[firstcryptoman]

Description

This pull request updates our GitHub Actions workflow configurations to utilize the latest versions of actions/checkout and actions/upload-artifact. The updates bring a variety of improvements, ensuring our workflows are more efficient and aligned with the best practices recommended by GitHub.

Changes

Update actions/checkout to v4:

Update actions/upload-artifact and actions/download-artifact to v4:

[coderabbitai]

Warning

Rate limit exceeded

@firstcryptoman has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 8 minutes and 42 seconds before requesting another review.

How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

Commits

Files that changed from the base of the PR and between ee76f29 and fd63116.

Walkthrough

The .github/workflows/ci-master.yml file has been updated to improve the GitHub Actions workflow by using the latest versions (v4) of actions/checkout, actions/upload-artifact, and actions/download-artifact. Additionally, a new step has been added to list the files in the source directory.

Changes

File	Change Summary
.github/.../ci-master.yml	Updated actions/checkout from v2 to v4, actions/upload-artifact from v1 to v4, and actions/download-artifact from v1 to v4. Added a step to list files in the source directory.

Poem

In the land of code, where actions flow,
Updated steps make workflows glow.
From v1 to v4, we've made the leap,
Now artifacts and checkouts run deep.
Listing files, we see what's stored,
Efficiency and clarity, now restored.
🌟🐇✨

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between bcaacd4 and e747c50.

Files selected for processing (1)

• .github/workflows/ci-master.yml (9 hunks)

Additional comments not posted (10)

.github/workflows/ci-master.yml (10)

25-25: Updated GitHub Action to v4: actions/checkout

The update from actions/checkout@v2 to actions/checkout@v4 is aligned with the PR objectives to use the latest versions. This should bring improvements such as faster performance and more features.

---

44-44: Updated GitHub Action to v4: actions/upload-artifact

The update from actions/upload-artifact@v1 to actions/upload-artifact@v4 is correctly implemented. Ensure that the new version's features and potential breaking changes have been considered.

---

57-62: Updated GitHub Action to v4: actions/download-artifact

The update from actions/download-artifact@v1 to actions/download-artifact@v4 is correctly implemented. The additional parameters (pattern, merge-multiple, run-id) are used correctly according to the new version's capabilities.

---

63-66: New step added: List downloaded files and directories

Adding a step to list files and directories is a good practice for debugging and verifying the artifacts' presence and structure. This aligns with the PR's aim to enhance workflow transparency and troubleshooting.

---

97-97: Repeated use of updated GitHub Action: actions/upload-artifact

The repeated update for actions/upload-artifact@v4 in another job is consistently implemented. This ensures uniformity across different jobs within the workflow.

---

118-118: Repeated use of updated GitHub Action: actions/upload-artifact

The consistent update to actions/upload-artifact@v4 for uploading test logs in case of failures is correctly implemented. This ensures that all artifacts use the latest version of the action.

---

130-130: Repeated use of updated GitHub Action: actions/download-artifact

The consistent update to actions/download-artifact@v4 for the Windows build job is correctly implemented. This ensures that all artifact downloads across different platforms use the latest version of the action.

---

159-159: Repeated use of updated GitHub Action: actions/upload-artifact

The update for the Windows build job to use actions/upload-artifact@v4 is correctly implemented. This consistency across different platform builds is crucial for maintaining uniform behavior and leveraging the latest action features.

---

171-171: Repeated use of updated GitHub Action: actions/download-artifact

The update to actions/download-artifact@v4 for the macOS build job is correctly implemented. This consistent application across various jobs ensures that the workflow benefits uniformly from the latest improvements.

---

199-199: Repeated use of updated GitHub Action: actions/upload-artifact

The update to actions/upload-artifact@v4 for the macOS build job is correctly implemented. This ensures that all artifacts, regardless of the platform, are using the latest version of the GitHub Action.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between e747c50 and ee76f29.

Files selected for processing (1)

• .github/workflows/ci-master.yml (9 hunks)

Files skipped from review as they are similar to previous changes (1)

• .github/workflows/ci-master.yml

[firstcryptoman]

We decided to close this PR in favor of a new one from Anwar, which will include the update and commit messages. This will be helpful for future updates if needed.