fix: example dependency

[hanzeINGH]

Fix the dependence on the SDK in the example package.

[coderabbitai]

Walkthrough

The pull request modifies the pom.xml file in the example project, specifically changing the version specification for the coze-api dependency. The change replaces a dynamic version reference using ${project.parent.version} with a hardcoded version 0.2.0, which explicitly sets the dependency version instead of inheriting it from the parent project.

Changes

File	Change Summary
example/pom.xml	Updated coze-api dependency version from parent project reference to hardcoded 0.2.0

Possibly related PRs

• fix: Fix User Agent reporting #20: Changes to coze-api dependency versioning in pom.xml files

Suggested labels

chore

Suggested reviewers

• chyroc

Poem

🐰 A Maven tale of version might,
From dynamic to static, clear and bright
Dependency pinned with careful care
No more floating versions to ensnare
A rabbit's precision, version set right! 📦

---

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 generate docstrings to generate docstrings for this PR. (Beta)
• @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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

example/pom.xml (1)

19-19: Consider using Maven properties for version management.

Instead of hardcoding the version, consider defining it as a property in the parent POM or this module's POM. This approach:

1. Makes version management more maintainable
2. Reduces the risk of version inconsistencies
3. Follows Maven best practices

+    <properties>
+        <coze.api.version>0.2.0</coze.api.version>
+    </properties>
+
     <dependencies>
         <dependency>
             <groupId>com.coze</groupId>
             <artifactId>coze-api</artifactId>
-            <version>0.2.0</version>
+            <version>${coze.api.version}</version>
         </dependency>

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between e25a777 and bbd9dde.

📒 Files selected for processing (1)

• example/pom.xml (1 hunks)

🔇 Additional comments (1)

example/pom.xml (1)

19-19: Verify compatibility with version 0.2.0.

The dependency version has been updated from inheriting the parent version (0.1.0) to explicitly using version 0.2.0. Please ensure:

1. Version 0.2.0 is available in the repository
2. No breaking changes exist between 0.1.0 and 0.2.0
3. The example project is compatible with the new version

✅ Verification successful

Version 0.2.0 appears safe to use

The version is officially released and contains improvements (API enhancements, deserialization fixes) without any breaking changes. Since no other modules depend on coze-api, the version update is isolated to this example module.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the availability and compatibility of coze-api version 0.2.0

# Check if version 0.2.0 exists in the repository
gh release view v0.2.0 2>/dev/null || echo "Warning: Release v0.2.0 not found"

# Look for any breaking changes or compatibility notes
rg -i "breaking|compat|upgrade" CHANGELOG.md README.md docs/ 2>/dev/null || echo "No explicit breaking changes found"

# Check if other modules also use coze-api to ensure version alignment
rg "com.coze['\"]?\s*,\s*['\"]?coze-api" -g "pom.xml" || echo "No other modules depend on coze-api"

Length of output: 864