Update GitHub Actions to v4

[justanwar]

Closes #67

Summary by CodeRabbit

• New Features

  • Introduced a new job to merge build artifacts, enhancing the workflow's capability to manage outputs from different platforms.

• Improvements

  • Upgraded action versions for better performance and features, improving overall workflow efficiency.
  • Specified names for uploaded artifacts, providing clarity on their purposes across different platforms.

[coderabbitai]

Walkthrough

The updates to the GitHub Actions workflow enhance build processes by upgrading actions/checkout and actions/upload-artifact to their latest versions, improving functionality and security. A new merge job is introduced to consolidate artifacts from Linux, Windows, and macOS builds, enhancing artifact management and clarity with distinct naming for each platform's outputs.

Changes

Files	Change Summary
.github/workflows/build_release.yml	Upgraded actions/checkout from v1 to v4; upgraded actions/upload-artifact from v3 to v4; added actions/upload-artifact/merge@v4.

Assessment against linked issues

Objective	Addressed	Explanation
Update actions/checkout to a supported version (67)	✅
Update actions/upload-artifact to a supported version (67)	✅
Prevent deprecated actions usage (67)	✅

Poem

🐇 In the fields where code does play,
I hop along and cheer today!
With actions new and merges bright,
Our builds take off, a splendid flight!
Let's celebrate with joyful cheer,
For smooth workflows are finally here! 🎉

---

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

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 4c8f59c and 774c466.

Files selected for processing (1)

• .github/workflows/build_release.yml (6 hunks)

Additional comments not posted (10)

.github/workflows/build_release.yml (10)

24-24: Update to actions/checkout@v4 is correct.

The update to actions/checkout@v4 is necessary to comply with the latest GitHub Actions versions and avoid deprecation.

---

42-42: Update to actions/upload-artifact@v4 is correct.

The update to actions/upload-artifact@v4 ensures compatibility with the latest GitHub Actions versions and prevents future deprecation issues.

---

44-47: Specify artifact names for clarity.

The artifact names linux-bin are specified for clarity, which is a good practice.

---

56-56: Update to actions/checkout@v4 is correct.

The update to actions/checkout@v4 is necessary to comply with the latest GitHub Actions versions and avoid deprecation.

---

74-74: Update to actions/upload-artifact@v4 is correct.

The update to actions/upload-artifact@v4 ensures compatibility with the latest GitHub Actions versions and prevents future deprecation issues.

---

76-79: Specify artifact names for clarity.

The artifact names windows-bin are specified for clarity, which is a good practice.

---

87-87: Update to actions/checkout@v4 is correct.

The update to actions/checkout@v4 is necessary to comply with the latest GitHub Actions versions and avoid deprecation.

---

107-107: Update to actions/upload-artifact@v4 is correct.

The update to actions/upload-artifact@v4 ensures compatibility with the latest GitHub Actions versions and prevents future deprecation issues.

---

109-112: Specify artifact names for clarity.

The artifact names macos-bin are specified for clarity, which is a good practice.

---

113-118: Introduction of merge job is correct.

The introduction of the merge job to consolidate artifacts from different builds using actions/upload-artifact/merge@v4 is a good practice to enhance artifact management.