upgrade cache action version

[nobodyiam]

What's the purpose of this PR

According to the github annoucement, the actions/cache@v1 will be deprecated in 2025/02, so we need to upgrade the version.

Brief changelog

• upgrade the cache action version to v4

Follow this checklist to help us incorporate your contribution quickly and easily:

• Read the Contributing Guide before making this pull request.
• Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
• Write necessary unit tests to verify the code.
• Run mvn clean test to make sure this pull request doesn't break anything.
• Update the CHANGES log.

Summary by CodeRabbit

• Chores
  • Updated the GitHub Actions workflow for improved caching of Maven dependencies.

[coderabbitai]

Walkthrough

The pull request modifies the GitHub Actions workflow for a Java project using Maven. Key updates include changing the actions/cache version from v1 to v4, adjusting the cache path from ~/.m2 to ~/.m2/repository, and updating the cache key format to enhance the caching mechanism for Maven dependencies. The restore keys have also been reformatted to a multi-line structure, improving the efficiency of the caching process.

Changes

File Path	Change Summary
.github/workflows/build.yml	Updated actions/cache from v1 to v4, changed cache path to ~/.m2/repository, modified cache key format, and adjusted restore keys to a multi-line format.

Possibly related PRs

• bump version to 2.4.0-SNAPSHOT #5202: This PR updates the versioning information in the pom.xml file, which is relevant to the main PR's focus on Maven project configuration and dependency management.
• Bump com.thoughtworks.xstream:xstream from 1.4.20 to 1.4.21 to fix CVE-2024-47072 #5280: This PR also modifies the pom.xml file to update a dependency version, indicating a direct connection to the changes made in the main PR regarding Maven configuration.

Suggested labels

lgtm

Poem

In the garden of code, we hop and play,
With caches updated, we brighten the day.
From v1 to v4, our paths now align,
Maven's dependencies, all neatly in line.
So let's dance and rejoice, with each little change,
For a smoother build process, we happily arrange! 🐇✨

Tip

CodeRabbit's docstrings feature is now available as part of our Early Access Program! Simply use the command @coderabbitai generate docstrings to have CodeRabbit automatically generate docstrings for your pull request. This feature will be included in our Pro Plan when released.

---

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

🧹 Outside diff range and nitpick comments (2)

.github/workflows/build.yml (2)

42-45: LGTM! Cache configuration follows best practices with room for enhancement.

The changes improve the caching mechanism by:

• Using the precise ~/.m2/repository path
• Using a descriptive cache key format
• Maintaining proper cache invalidation with pom.xml hash

Consider these optional enhancements:

 path: ~/.m2/repository
-key: ${{ runner.os }}-maven-${{ hashFiles('**/pom.xml') }}
+key: ${{ runner.os }}-maven-${{ matrix.jdk }}-${{ hashFiles('**/pom.xml', '**/settings.xml') }}
 restore-keys: |
-  ${{ runner.os }}-maven-
+  ${{ runner.os }}-maven-${{ matrix.jdk }}-
+  ${{ runner.os }}-maven-

These changes would:

1. Include JDK version in the cache key for better isolation
2. Add settings.xml to cache key if present (helps when using custom Maven settings)

---

Line range hint 35-37: Consider upgrading actions/setup-java to v4.

While updating the cache action, it would be beneficial to also upgrade actions/setup-java from v1 to v4 for improved features and security.

-      uses: actions/setup-java@v1
+      uses: actions/setup-java@v4
       with:
         java-version: ${{ matrix.jdk }}
+        distribution: 'temurin'  # Specify the Java distribution

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 28d2898 and 9bd27ba.

📒 Files selected for processing (1)

• .github/workflows/build.yml (1 hunks)

🔇 Additional comments (1)

.github/workflows/build.yml (1)

40-40: LGTM! Appropriate version upgrade to address deprecation.

The upgrade to actions/cache@v4 is a necessary change to address the upcoming deprecation of v1 in February 2025.