chore: Fix release action

[hanzeINGH]

Change-Id: Ie8e4169c150e29c37f0531ee38337530695ac7a7

[coderabbitai]

Walkthrough

The GitHub Actions workflow for releases has been updated to run on macOS instead of Ubuntu. The change modifies only the environment specification in the release job, switching from ubuntu-latest to macos-latest. All other steps, such as code checkout and Java setup, remain unchanged.

Changes

File	Change Summary
.github/workflows/release.yml	Updated job environment from ubuntu-latest to macos-latest

Suggested labels

chore

Poem

I'm a hopping rabbit with code to share,
Skipping through changes light as air.
Ubuntu hopped away, now macOS takes the lead,
In our workflow garden where updates succeed.
With twitching ears and a joyful cheer,
Carrots and code make our future clear!

Tip

⚡🧪 Multi-step agentic review comment chat (experimental)

• We're introducing multi-step agentic chat in review comments. This experimental feature enhances review discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments.
  - To enable this feature, set early_access to true under in the settings.

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e15af3d and 255c78d.

📒 Files selected for processing (1)

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

🔇 Additional comments (1)

.github/workflows/release.yml (1)

9-9: Validate the macOS environment compatibility.

The change from ubuntu-latest to macos-latest is correctly applied. However, please verify that all steps—especially the Java setup and Maven deployment—are fully compatible with the macOS environment. Subtle differences in execution (e.g., available utilities, file system behavior) might affect the build and release process.

---

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.

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 77.70%. Comparing base (e15af3d) to head (255c78d).
Report is 1 commits behind head on main.

@@            Coverage Diff            @@
##               main      #73   +/-   ##
=========================================
  Coverage     77.70%   77.70%           
  Complexity      321      321           
=========================================
  Files            61       61           
  Lines          1583     1583           
  Branches        102      102           
=========================================
  Hits           1230     1230           
  Misses          280      280           
  Partials         73       73           

Flag	Coverage Δ	Complexity Δ
unittests	77.70% <ø> (ø)	321.00 <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.