chore: bump version to 3.0.3; update README link to v3.0.3

[CAICAIIs]

Relate to #7

Summary by CodeRabbit

• Documentation

  • Updated README to reference binary release v3.0.3.
  • Clarified installation instructions for building from source, adding explicit steps (clone, change directory, build).
  • Retained go install example and PATH reminder.

• Chores

  • Bumped application version to 3.0.3 to align with the latest release.

[coderabbitai]

Walkthrough

Updated version constant to 3.0.3 and synchronized README: new binary release reference and expanded build-from-source steps (clone, cd, go build). No control flow or API changes.

Changes

Cohort / File(s)	Summary of Changes
Documentation update README.md	Updated binary release reference to v3.0.3; expanded Installation snippet to include clone, cd, and go build; retained existing go install command and PATH note.
Version bump internal/version/version.go	Changed exported Version constant from "3.0.0" to "3.0.3"; no other code modifications.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

I thump my paw: v3.0.3!
Carrots counted, tags agree.
README trails the freshest trail,
Build from source—no chance to fail.
With whiskers twitching happily,
I ship this hop in harmony. 🥕🚀

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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

• 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.
  • 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.
• 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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)

README.md (1)

22-26: Fix wording: it says “go get” but uses go install.

Minor doc mismatch—modern guidance is to use go install module@version. Recommend aligning the sentence with the command shown.

Apply this diff:

-To install `protoc-gen-go-triple`, you can use the `go get` command:
+To install `protoc-gen-go-triple`, use the `go install` command (Go 1.16+):

-go install github.com/dubbogo/protoc-gen-go-triple/v3@v3.0.3
+go install github.com/dubbogo/protoc-gen-go-triple/v3@v3.0.3

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between a5eebb3 and 734f563.

📒 Files selected for processing (2)

• README.md (1 hunks)
• internal/version/version.go (1 hunks)

🔇 Additional comments (3)

internal/version/version.go (1)

20-20: LGTM: Version bump to 3.0.3 verified and all references in sync

• internal/version/version.go: Version constant correctly set to "3.0.3".
• README.md: Installation instructions and release links updated to v3.0.3.
• go.mod: Module path includes the /v3 major-version suffix.
• GitHub release tag v3.0.3 exists (HTTP 200).

All checks pass—no stale 3.0.x references remain. Ready to merge.

README.md (2)

30-34: Main package confirmed at repository root – existing go build is sufficient

• Verified that package main is declared in main.go at the repository root (line 22), with no other main packages under cmd/
• Therefore, running go build at the repo root will produce the expected binary; no path adjustment is necessary

---

28-28: Release tag v3.0.3 verified – No further action required

Validation via HTTP 200 confirms that v3.0.3 is published and the link in the README will resolve correctly.

• README.md, line 28: release link to v3.0.3 is valid.