Update rpc version 051302 ss

[EvenLjj]

update rpc version to 5.13.2-SNAPSHOT

Summary by CodeRabbit

• New Features

  • Updated project version to 5.13.2-SNAPSHOT, indicating ongoing development.
  • Enhanced dependency version for Hessian from 3.5.4 to 3.5.5.

• Bug Fixes

  • Resolved versioning inconsistencies across project components.

• Documentation

  • Updated version constants to align with the new release in relevant documentation.

[coderabbitai]

Walkthrough

The pull request involves updates to the versioning of the project and its dependencies across multiple files. The project version for sofa-rpc-all has been incremented from 5.13.1 to 5.13.2-SNAPSHOT, indicating a shift to a new development snapshot. Additionally, the hessian dependency version has been updated from 3.5.4 to 3.5.5. These changes are reflected consistently in the pom.xml, bom/pom.xml, and the Version.java class.

Changes

File/Path	Change Summary
all/pom.xml, bom/pom.xml	Updated project version from 5.13.1 to 5.13.2-SNAPSHOT and hessian version from 3.5.4 to 3.5.5.
core/api/src/main/java/com/alipay/sofa/rpc/common/Version.java	Updated VERSION, RPC_VERSION, and BUILD_VERSION constants to reflect the new versioning.
pom.xml	Revised <revision> property from 5.13.1 to 5.13.2-SNAPSHOT.

Possibly related PRs

• update hessian version to 3.5.5 #1445: This PR updates the hessian version from 3.5.4 to 3.5.5, which directly relates to the main PR's change of the hessian dependency version in the pom.xml file.

Suggested reviewers

• Lo1nt
• chuailiwu

Poem

🐇 In the garden of code, a change takes flight,
Versions updated, oh what a sight!
From 5.13.1 to 5.13.2,
A hop, a skip, a leap anew!
With hessian now bright and bold,
Our project’s future, a tale to be told! 🌼

---

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

core/api/src/main/java/com/alipay/sofa/rpc/common/Version.java (1)

40-40: BUILD_VERSION update is consistent with the VERSION update.

The BUILD_VERSION constant is correctly updated to include the new version "5.13.2" and a timestamp "20240922142359", maintaining consistency with the VERSION constant update.

Consider adding a comment to clarify the timestamp format for better readability and maintainability. For example:

/**
 * Current build version, updated with each release.
 * Format: "<version>_<yyyyMMddHHmmss>"
 */
public static final String BUILD_VERSION = "5.13.2_20240922142359";

pom.xml (1)

80-80: Version update looks good, but exercise caution with snapshot versions.

Updating the <revision> property to 5.13.2-SNAPSHOT is a valid change for managing the project version. However, please keep in mind that snapshot versions indicate ongoing development and instability. They should be used cautiously and avoided in production environments until a stable release version is available.

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between d5b8c50 and 3e1cd76.

Files selected for processing (4)

• all/pom.xml (2 hunks)
• bom/pom.xml (2 hunks)
• core/api/src/main/java/com/alipay/sofa/rpc/common/Version.java (1 hunks)
• pom.xml (1 hunks)

Additional comments not posted (6)

core/api/src/main/java/com/alipay/sofa/rpc/common/Version.java (2)

30-30: Version update looks good!

The VERSION constant is correctly updated to "5.13.2", following the semantic versioning format. This aligns with the PR objective of updating the RPC version.

---

35-35: RPC_VERSION update is consistent with the VERSION update.

The RPC_VERSION constant is correctly updated to 51302, maintaining consistency with the VERSION constant update to "5.13.2".

bom/pom.xml (2)

13-13: LGTM!

Updating the <revision> property to 5.13.2-SNAPSHOT is appropriate for a new development version. The change aligns with the common versioning practices.

---

35-35: Verify compatibility and test functionality after upgrading the hessian dependency.

Upgrading the hessian dependency to version 3.5.5 looks good. As a minor version upgrade, it should be backward-compatible.

To ensure a smooth upgrade, please:

1. Verify that the new version is compatible with the project's usage of the hessian library.
2. Thoroughly test the functionality that depends on the hessian library to catch any potential issues introduced by the upgrade.

all/pom.xml (2)

9-9: LGTM!

The version update to 5.13.2-SNAPSHOT looks good for the development phase.

---

62-62: Verify compatibility of the hessian version update.

Updating the hessian dependency to version 3.5.5 is a good practice. However, please ensure this update does not introduce any breaking changes.

Run the following script to find usages of the hessian dependency and verify compatibility:

Verification successful

---

Hessian version update is compatible.

The hessian dependency update to version 3.5.5 is used only in test files, ensuring no impact on the production codebase.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Find usage of hessian and verify compatibility with the updated version.

# Test: Search for imports of hessian classes. Expect: Only imports from the updated version.
rg --type java 'import com\.alipay\.sofa\.hessian\.'

Length of output: 54

---

Script:

#!/bin/bash
# Description: Comprehensive search for hessian dependency usage.

# 1. Search for any imports containing 'hessian'
rg --type java 'hessian'

# 2. Search all pom.xml files for hessian dependencies
rg '<hessian\.version>' pom.xml

# 3. Search for hessian in configuration files
rg 'hessian' config/

Length of output: 41834