Skip to content

feat: derive version from gradle.properties, eliminate hardcoded versions#318

Merged
xinhuagu merged 1 commit into
mainfrom
feature/release-pipeline
Mar 19, 2026
Merged

feat: derive version from gradle.properties, eliminate hardcoded versions#318
xinhuagu merged 1 commit into
mainfrom
feature/release-pipeline

Conversation

@xinhuagu

Copy link
Copy Markdown
Owner

Summary

  • BuildVersion.java reads from version.properties generated at build time
  • gradle.properties is the single source of truth (bumped to 0.3.0-SNAPSHOT)
  • All 4 hardcoded 0.1.0-SNAPSHOT references replaced
  • Release workflow (release.yml) already bumps gradle.properties via git-cliff — now the version flows through to Java code automatically

Test plan

  • ./gradlew build passes
  • version.properties generated with correct content
  • DaemonIntegrationTest updated (no longer asserts specific version string)

🤖 Generated with Claude Code

Replace 4 hardcoded '0.1.0-SNAPSHOT' references with BuildVersion
that reads from version.properties generated at build time.

- gradle.properties: single source of truth (now 0.3.0-SNAPSHOT)
- aceclaw-core/build.gradle.kts: generates version.properties resource
- BuildVersion.java: reads version from classpath resource
- AceClawMain, RequestRouter: use BuildVersion.version()
- Release workflow already bumps gradle.properties via git-cliff

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

@greptile-apps greptile-apps Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.

@coderabbitai

coderabbitai Bot commented Mar 19, 2026

Copy link
Copy Markdown

Warning

Rate limit exceeded

@xinhuagu has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 14 minutes and 11 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 4369d1c5-66c4-473e-9525-8305afa82e3f

📥 Commits

Reviewing files that changed from the base of the PR and between c9259b6 and 1401e45.

📒 Files selected for processing (6)
  • aceclaw-cli/src/main/java/dev/aceclaw/cli/AceClawMain.java
  • aceclaw-core/build.gradle.kts
  • aceclaw-core/src/main/java/dev/aceclaw/core/BuildVersion.java
  • aceclaw-daemon/src/main/java/dev/aceclaw/daemon/RequestRouter.java
  • aceclaw-daemon/src/test/java/dev/aceclaw/daemon/DaemonIntegrationTest.java
  • gradle.properties
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feature/release-pipeline
📝 Coding Plan
  • Generate coding plan for human review comments

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@xinhuagu xinhuagu merged commit 480788c into main Mar 19, 2026
4 checks passed
@xinhuagu xinhuagu deleted the feature/release-pipeline branch March 19, 2026 23:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant