build: update artifact actions to v4

[alex-liang3]

Bumps the upload-artifact action to v4, following the deprecation of v3. The breaking changes shouldn't affect us, notably:

• None of the artifacts should contain hidden files
• Since artifacts are scoped per workflow invocation, we don't need to worry about them now becoming immutable; see run 1, and a re-run of the same workflow attempt both succeeding.

Symmetrically, download-artifact should also be bumped to v4.

Summary by CodeRabbit

• Chores
  • Updated GitHub Actions workflow files to use the latest versions of actions/upload-artifact and actions/download-artifact actions (v4)
  • Maintained existing workflow logic and structure while upgrading action versions

[coderabbitai]

Walkthrough

This pull request focuses on updating GitHub Actions workflow files to use the latest versions of actions/upload-artifact and actions/download-artifact. Specifically, the changes involve upgrading from version 3 to version 4 in two workflow files: .github/workflows/build-packages.yml and .github/workflows/release.yml. The updates are consistent across multiple jobs, targeting artifact upload and download steps, with no changes to the underlying workflow logic or control flow.

Changes

File	Change Summary
.github/workflows/build-packages.yml	Updated actions/upload-artifact from v3 to v4 in three steps: "Upload C++ Package," "Upload Python Package," and "Upload Documentation"
.github/workflows/release.yml	Updated actions/download-artifact from v3 to v4 in three jobs: deploy-package-cpp, deploy-package-python, and deploy-documentation

Possibly related PRs

• build: remove base image multi-stage build #129: Workflow modifications (not directly related to action version updates)

Suggested reviewers

• vishwa2710
• Derollez

Poem

🐰 Artifacts dancing, versions anew,
GitHub Actions leaping with version four!
From v3 to v4, smooth and bright,
Workflows upgrading with rabbit delight!
Code flows like carrots, clean and clear 🥕

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 722faed and 7cff4d8.

📒 Files selected for processing (2)

• .github/workflows/build-packages.yml (3 hunks)
• .github/workflows/release.yml (3 hunks)

✅ Files skipped from review due to trivial changes (2)

• .github/workflows/build-packages.yml
• .github/workflows/release.yml

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

• GitHub Check: Build and Push and Tag Base Image with Version / Build Development Image

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.

[alex-liang3]

Closed due to being covered in #147