Update actions/cache to v4

[duongcao-ea]

What's this PR do?

• Update actions/cache to v4.

Why are we doing this?

• The current version v1 is deprecated so it makes the job failed.
  

Summary by CodeRabbit

• Chores
  • Upgraded the caching mechanism used in automated processes to enhance dependency management. This improvement contributes to smoother and more reliable background operations without altering visible functionality.

[coderabbitai]

Walkthrough

The changes update the version of the actions/cache GitHub Action in three workflow files. For each file, the version is modified from v1 to v4. The workflows remain focused on caching Python dependencies, and no additional modifications were made to the logic or behavior.

Changes

File(s)	Change Summary
.github/workflows/archive.yml .github/workflows/ci.yml .github/workflows/cron.yml	Updated actions/cache usage from version v1 to v4 to manage Python dependency caching

Poem

With a hop and a skip, I code all day,
Upgraded cache actions now lead the way.
From v1 to v4, the workflows gleam bright,
Python dependencies cached just right.
CodeRabbit cheers with a joyous delight! 🐰

---

📜 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 0a92a86 and 99d7627.

📒 Files selected for processing (3)

• .github/workflows/archive.yml (1 hunks)
• .github/workflows/ci.yml (1 hunks)
• .github/workflows/cron.yml (1 hunks)

🔇 Additional comments (3)

.github/workflows/ci.yml (1)

34-41: Update Cache Action Version to v4

The caching step now correctly uses actions/cache@v4, which resolves the deprecation issues and job failures associated with the older v1 version. Ensure that the rest of the workflow continues to function as expected with this update.

.github/workflows/cron.yml (1)

38-45: Apply Cache Action Update in Cron Workflow

This change updates the caching action to actions/cache@v4, aligning it with the broader set of workflow updates. The structure and key settings remain correct for caching Python dependencies.

.github/workflows/archive.yml (1)

31-38: Update Archive Workflow to Use Cache Action v4

The workflow now utilizes actions/cache@v4, which is in line with the overall PR objective to move away from deprecated v1. The configuration for caching within the .venv directory remains unchanged and appears correct.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
• @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.

[lamle-ea]

LGTM