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 an initialize method for custom ProviderManager, enhancing flexibility.
  • Implemented parsing time based on a specified pattern for better JSON handling with @ApolloJsonValue.
  • Enhanced loading of mocked properties to simplify testing and configuration management.
  • Improved performance of namespace loading during startup, particularly under error conditions.
  • Upgraded to Spring Boot version 2.7.18 for better compatibility and security.

• Chores

  • Updated project versioning to reflect the transition to version 2.4.0-SNAPSHOT.

[coderabbitai]

Walkthrough

The update from version 2.3.0 to 2.4.0 of the Apollo Java project involves removing several specific enhancements and fixes from the release notes. The focus has shifted to a more streamlined approach, with a placeholder for future updates. Additionally, a new file has been created to document the changes made in version 2.3.0, while the project version in the pom.xml has been updated to reflect the transition to 2.4.0-SNAPSHOT.

Changes

File	Change Summary
CHANGES.md, changes/changes-2.3.0.md	Removed specific enhancements from 2.4.0 notes; created new file for detailed 2.3.0 release notes, highlighting major updates like new initialize method and performance improvements.
pom.xml	Updated project version to <revision>2.4.0-SNAPSHOT</revision>, indicating a transition to the next development phase.

Sequence Diagram(s)

sequenceDiagram
    participant Developer
    participant Apollo
    Developer->>Apollo: Inquire about updates
    Apollo-->>Developer: Release notes available
    Developer->>Apollo: Review changes
    Apollo-->>Developer: Highlights and new features

Loading

🐇✨
In fields of code, where rabbits roam,
We hop through changes, making new home.
With version fresh, and features bright,
We leap with joy, in the coding light!
Springing forward, we cheer and play,
For Apollo’s growth, hip-hip-hooray!

---

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 1fc9d27 and 1254437.

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 (2)

• CHANGES.md
• pom.xml

Additional comments not posted (3)

changes/changes-2.3.0.md (3)

1-3: Heading and Introduction: LGTM!

The heading and introductory lines are clear and well-formatted.

---

5-13: Change List: LGTM!

The list of changes is clear and well-documented, with links to relevant pull requests.

---

15-16: Closing Lines: LGTM!

The closing lines effectively provide additional information and context.