bump version to 2.4.0-SNAPSHOT

[nobodyiam]

What's the purpose of this PR

bump version to 2.4.0-SNAPSHOT

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

• New Features

  • Introduced structured release notes for Apollo version 2.3.0, summarizing key updates, bug fixes, and UI enhancements.

• Documentation

  • Updated the release notes for Apollo version 2.4.0 to simplify and remove past details while directing users to the new milestone tracking for closed issues.

• Chores

  • Revised versioning information to indicate transition to a new development version (2.4.0-SNAPSHOT).

[coderabbitai]

Walkthrough

The Apollo project has transitioned from version 2.3.0 to 2.4.0, simplifying its release notes by removing detailed entries from the previous version. This change streamlines the documentation, focusing on current updates while redirecting users to the new milestone for closed issues. Additionally, versioning in the pom.xml file has been updated to reflect this new development phase. A new release notes file for version 2.3.0 has also been introduced, summarizing key enhancements and fixes.

Changes

Files	Change Summary
CHANGES.md, changes/changes-2.3.0.md	Updated release notes for version 2.4.0 by removing specific entries from 2.3.0; introduced new file summarizing enhancements and fixes from 2.3.0.
pom.xml	Updated <revision> from 2.3.0 to 2.4.0-SNAPSHOT, indicating a shift to a new development version.

Poem

🐰 In the fields of code, where changes bloom,
The Apollo leaps, dispelling gloom.
With notes now crisp and clear,
We celebrate the updates here!
From version to version, we joyfully hop,
🥳 New paths await, we’ll never stop!

---

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.
  • @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 as 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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between c28eb49 and ce711b8.

Files selected for processing (3)

• CHANGES.md (1 hunks)
• changes/changes-2.3.0.md (1 hunks)
• pom.xml (1 hunks)

Files skipped from review due to trivial changes (3)

• CHANGES.md
• changes/changes-2.3.0.md
• pom.xml