Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

release rpc version 5.14.0-SNAPSHOT #1458

Merged
merged 1 commit into from
Nov 1, 2024

Conversation

EvenLjj
Copy link
Collaborator

@EvenLjj EvenLjj commented Nov 1, 2024

release rpc version 5.14.0-SNAPSHOT

Summary by CodeRabbit

  • New Features

    • Updated project version to 5.14.0-SNAPSHOT, indicating ongoing development with potential new features.
  • Bug Fixes

    • Corrected the Javadoc generation property in the release profile for improved build process reliability.

These updates enhance the project's versioning and build processes, preparing it for future developments.

@sofastack-cla sofastack-cla bot added cla:yes CLA is ok size/S labels Nov 1, 2024
Copy link
Contributor

coderabbitai bot commented Nov 1, 2024

Walkthrough

The changes in this pull request primarily involve updating version numbers in various pom.xml files and the Version class within the core package of the sofa-rpc project. The version is incremented from 5.13.2 to 5.14.0-SNAPSHOT, indicating a transition to a new development snapshot. Additionally, a minor correction was made to a property in the pom.xml related to Javadoc generation. No structural changes to dependencies or configurations were made.

Changes

File Path Change Summary
all/pom.xml Updated version from 5.13.2 to 5.14.0-SNAPSHOT.
bom/pom.xml Updated revision property from 5.13.2 to 5.14.0-SNAPSHOT.
core/api/src/main/java/com/alipay/sofa/rpc/common/Version.java Updated version fields: VERSION from "5.13.2" to "5.14.0", RPC_VERSION from 51302 to 51400, BUILD_VERSION from "5.13.2_20241016193119" to "5.14.0_20241101180137".
pom.xml Updated <revision> from 5.13.2 to 5.14.0-SNAPSHOT and corrected <maven.javadoc.quite> to <maven.javadoc.quiet> in the release profile.

Possibly related PRs

  • Update rpc version 051302 ss #1448: This PR updates the RPC version to 5.13.2-SNAPSHOT, which is directly related to the versioning changes in the main PR that updates to 5.14.0-SNAPSHOT.
  • release rpc version 5.13.2 #1455: This PR releases the RPC version 5.13.2, which is relevant as it follows the versioning updates in the main PR, indicating a progression in the versioning scheme.

Suggested reviewers

  • Lo1nt
  • chuailiwu

🐇 In the meadow, hop and play,
A new version's here today!
From five-thirteen to fourteen we leap,
With changes made, our code runs deep.
Javadoc's quiet, the build's just right,
Hooray for updates, oh what a sight! 🌼


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
🪧 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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Outside diff range and nitpick comments (1)
pom.xml (1)

Line range hint 449-452: Fix typo in Javadoc property name

The property maven.javadoc.quite contains a typo and should be maven.javadoc.quiet. This incorrect property name prevents Maven from properly controlling Javadoc output during releases.

Apply this fix:

             <properties>
-                <maven.javadoc.quite>true</maven.javadoc.quite>
+                <maven.javadoc.quiet>true</maven.javadoc.quiet>
                 <maven.javadoc.skip>false</maven.javadoc.skip>
             </properties>
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 3e317ff and 9feb05b.

📒 Files selected for processing (4)
  • all/pom.xml (1 hunks)
  • bom/pom.xml (1 hunks)
  • core/api/src/main/java/com/alipay/sofa/rpc/common/Version.java (1 hunks)
  • pom.xml (1 hunks)
✅ Files skipped from review due to trivial changes (2)
  • all/pom.xml
  • core/api/src/main/java/com/alipay/sofa/rpc/common/Version.java
🔇 Additional comments (1)
bom/pom.xml (1)

13-13: LGTM! Version update follows semantic versioning.

The version change from 5.13.2 to 5.14.0-SNAPSHOT is appropriate for a new development cycle, indicating new features will be added without breaking changes.

Let's verify version consistency across all pom files:

✅ Verification successful

Version consistency verified across the project

The verification shows that:

  1. The revision property is correctly set to 5.14.0-SNAPSHOT in the BOM
  2. All modules properly inherit the version through ${revision} or ${project.version}
  3. No references to the old version 5.13.2 were found
  4. The version inheritance chain is intact through parent-child relationships
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check version consistency across pom files
# Expected: All pom files should reference the same version (5.14.0-SNAPSHOT)

echo "Checking version consistency across pom files..."
# Find all pom.xml files and check for version references
fd --type f "pom.xml$" --exec grep -l "5\.14\.0-SNAPSHOT\|revision" {} \;

# Verify no old version references remain
echo "Checking for old version references..."
rg "5\.13\.2" --type xml

Length of output: 2149


Script:

#!/bin/bash
# Let's check the actual version references in pom files
# First, check for direct version references
echo "Checking direct version references..."
fd "pom.xml$" --exec grep -A 1 "<version>" {} \;

# Then check revision property references
echo -e "\nChecking revision property references..."
fd "pom.xml$" --exec grep -A 1 "<revision>" {} \;

# Finally check parent version references
echo -e "\nChecking parent version references..."
fd "pom.xml$" --exec grep -A 3 "<parent>" {} \;

Length of output: 43170

@@ -77,7 +77,7 @@

<properties>
<!-- Build args -->
<revision>5.13.2</revision>
<revision>5.14.0-SNAPSHOT</revision>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codebase verification

Version update needs attention

The version update to 5.14.0-SNAPSHOT is inconsistent across the codebase:

  • POM files correctly use 5.14.0-SNAPSHOT version
  • However, Version.java uses non-snapshot versions:
    • VERSION = "5.14.0"
    • BUILD_VERSION = "5.14.0_20241101180137"

This inconsistency between POM files and Version.java should be addressed. The Version.java constants should reflect that this is a SNAPSHOT release.

🔗 Analysis chain

Version update looks good!

The version bump from 5.13.2 to 5.14.0-SNAPSHOT follows semantic versioning and aligns with the release objectives.

Let's verify version consistency across all POM files:

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check version consistency across all POM files
# Expected: All POMs should reference 5.14.0-SNAPSHOT

echo "Checking version references in POM files..."
find . -name "pom.xml" -type f -exec grep -H "<revision>" {} \;

Length of output: 277


Script:

#!/bin/bash
# Let's also check for any direct version references in POM files
# that might not be using the revision property

echo "Checking for direct version references..."
find . -name "pom.xml" -type f -exec grep -H "<version>5" {} \;

# Also check Version.java file for consistency
echo -e "\nChecking Version.java file..."
find . -name "Version.java" -type f -exec grep -H "VERSION" {} \;

Length of output: 793

@EvenLjj EvenLjj merged commit be93251 into sofastack:master Nov 1, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants