chore: update README badge

[ymc9]

No description provided.

[coderabbitai]

Warning

Rate limit exceeded

@ymc9 has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 15 minutes and 5 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.

📥 Commits

Reviewing files that changed from the base of the PR and between 0e14011 and efd0e4f.

📒 Files selected for processing (1)

• README.md

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/update-readme-badge-1

---

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

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

[claude]

Claude finished @ymc9's task —— View job

---

Code Review for README Badge Update

I've reviewed this pull request that updates a README badge. Here's my analysis:

Todo List:

• Read the current README.md file
• Check git diff to see exactly what changed
• Analyze the badge update for correctness
• Provide comprehensive review feedback

Review Feedback

Summary of Changes

The PR updates the npm version badge in README.md from showing the next tag to showing the latest tag:

• Before: https://img.shields.io/npm/v/%40zenstackhq%2Fcli/next
• After: https://img.shields.io/npm/v/%40zenstackhq%2Fcli/latest

This change is on line 10 of README.md:10.

Code Quality Assessment

✅ Positive aspects:

• Semantically correct: The change from next to latest tag suggests this is likely related to a stable release (v3.0.0 as seen in recent commits)
• Consistent formatting: The badge URL structure and HTML formatting remains consistent
• No syntax issues: The URL encoding for the scoped package name (%40zenstackhq%2Fcli) is correct

Technical Analysis

Code Quality: ✅ Excellent

• Clean, minimal change with clear intent
• Proper URL encoding maintained
• No formatting or syntax issues

Potential Issues: ✅ None identified

• No bugs or technical issues
• URL structure is valid and follows shields.io conventions

Performance: ✅ N/A

• Documentation change with no performance impact
• Badge loading is handled by external service (shields.io)

Security: ✅ Excellent

• No security concerns
• Using HTTPS URLs
• No exposure of sensitive information

Test Coverage: ✅ N/A

• Documentation change doesn't require test coverage
• Badge functionality is handled by external service

Recommendations

1. Context validation: Consider verifying that the latest tag accurately reflects the current stable version
2. Documentation consistency: Ensure other documentation references align with this version tag change

Overall Assessment

This is a straightforward, well-executed documentation update. The change from next to latest badge suggests the project has moved from pre-release to stable release status, which aligns with the v3.0.0 version seen in the commit history. The implementation is technically sound with no issues identified.

Recommendation: ✅ Approve - This is a clean, appropriate badge update with no technical concerns.

---

[Copilot]

Pull request overview

This PR updates the npm version badge in the README to display the latest stable release instead of the next pre-release version.

• Changes the npm badge URL parameter from next to latest to track stable releases

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.