Upgrade github action version to v4

[CrazyHZM]

Summary by CodeRabbit

• Chores
  • Updated GitHub workflow actions to newer versions for enhanced performance and stability.

[coderabbitai]

Walkthrough

The recent modifications to the GitHub workflows are primarily focused on updating the versions of the actions used. This includes transitions to newer versions for better functionality and possibly introducing new features or addressing previous issues in the workflow processes.

Changes

File Path	Change Summary
.github/workflows/maven.yml	Updated actions/checkout to v4, actions/setup-java to v4, codecov/codecov-action to v4
.github/workflows/release.yml	Updated actions/checkout and actions/setup-java to v4

🐇✨🎉
In the land of code and byte,
A rabbit hopped through the night.
With a flip and a skip, versions took flight,
From v2 to v4, oh what a sight!
Cheers to updates, done just right! 🌟🥕
🐇✨🎉

---

Recent Review Details

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 2ad93e1 and 154ada5.

Files selected for processing (2)

• .github/workflows/maven.yml (2 hunks)
• .github/workflows/release.yml (1 hunks)

Additional comments not posted (3)

.github/workflows/release.yml (1)

14-16: Updated versions of actions/checkout and actions/setup-java to v4.

.github/workflows/maven.yml (2)

21-25: Updated versions of actions/checkout and actions/setup-java to v4.

Verification successful

---

The specified versions (v4) of actions/checkout and actions/setup-java have been confirmed to exist in the repository. However, due to the limitations of this environment, detailed release notes were not retrieved, and the workflow was not tested. It is recommended to manually review the release notes for any potential breaking changes and to test the workflow to ensure it executes without errors.

• Confirm the existence of actions/checkout v4 and actions/setup-java v4.
• Manually review detailed release notes for potential breaking changes.
• Test the workflow to ensure proper execution.

Scripts Executed

The following scripts were executed for the analysis:

---

Script:

#!/bin/bash
# Verify that the new versions of the actions do not introduce breaking changes by checking the release notes and testing the workflow.
echo "Check the release notes for actions/checkout and actions/setup-java v4 for any breaking changes."
echo "Test the workflow to ensure it executes without errors."

Length of output: 323

---

---

Script:

#!/bin/bash
# Check the GitHub repository for actions/checkout to find the release notes for version 4
gh release view v4 --repo actions/checkout --json body -q .body

# Check the GitHub repository for actions/setup-java to find the release notes for version 4
gh release view v4 --repo actions/setup-java --json body -q .body

# Since testing the workflow execution is not feasible here, we will rely on the release notes to identify any breaking changes.

Length of output: 169

---

---

Script:

#!/bin/bash
# Attempt to list the latest releases for actions/checkout to verify the existence of version 4
gh release list --repo actions/checkout --limit 5

# Attempt to list the latest releases for actions/setup-java to verify the existence of version 4
gh release list --repo actions/setup-java --limit 5

Length of output: 490

---

37-37: Updated version of codecov/codecov-action to v4.

---

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.

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 a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 83.12%. Comparing base (2ad93e1) to head (154ada5).

Additional details and impacted files

@@             Coverage Diff              @@
##             master    #1308      +/-   ##
============================================
- Coverage     83.14%   83.12%   -0.03%     
+ Complexity     2961     2959       -2     
============================================
  Files           337      337              
  Lines          9707     9707              
  Branches       1168     1168              
============================================
- Hits           8071     8069       -2     
  Misses         1127     1127              
- Partials        509      511       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.