fix(cli): update version check tag to latest

[ymc9]

Summary by CodeRabbit

• Chores
  • Updated version check configuration to query the 'latest' npm tag instead of 'next' tag.

[claude]

Claude finished @ymc9's task —— View job

---

PR Review Analysis

Reviewing this pull request for code quality, potential issues, performance, security, and test coverage.

Todo List:

• Read and analyze the modified file
• Check for related test files
• Review for code quality and best practices
• Look for potential bugs or issues
• Assess performance considerations
• Check for security concerns
• Evaluate test coverage needs
• Provide comprehensive feedback

---

Code Review Feedback

This PR makes a simple but important change: updating the version check tag from 'next' to 'latest' in packages/cli/src/utils/version-utils.ts:8.

✅ Positive Aspects

1. Clear Intent: The change aligns with the commit message and appears to fix version checking to use stable releases instead of pre-release versions.

2. Minimal Scope: The change is focused and doesn't introduce unnecessary modifications.

3. Proper Implementation: The change correctly updates the constant that's used in the npm registry API call on line 36.

📝 Code Quality & Best Practices

• Good: The code follows consistent naming conventions and structure
• Good: Uses proper TypeScript typing and error handling
• Good: Includes appropriate timeout handling for the network request

🔍 Potential Considerations

1. Missing Context: The PR description is empty, which makes it difficult to understand:

   • Why was 'next' being used previously?
   • What prompted this change to 'latest'?
   • Is this related to a specific release strategy change?

2. Documentation: Consider adding a comment explaining the choice of 'latest' tag, especially if there are specific scenarios where different tags might be appropriate.

🧪 Test Coverage

• Gap Identified: No unit tests found for the version checking functionality
• Recommendation: Consider adding tests to verify:
  • Version check behavior with different registry responses
  • Error handling when registry is unreachable
  • Timeout behavior
  • Different tag values (latest, next, etc.)

🚀 Performance & Security

• Good: Includes proper timeout (2000ms) to prevent hanging requests
• Good: Uses AbortSignal for request cancellation
• Good: Proper error handling prevents crashes on network failures
• Security: The npm registry URL is hardcoded and trusted, which is appropriate

💡 Suggestions for Future Improvements

1. Configuration: Consider making the tag configurable via environment variable or CLI flag for development/testing scenarios
2. Logging: Add debug logging to help troubleshoot version check issues
3. Caching: Consider implementing basic caching to avoid excessive registry requests

⚠️ Impact Assessment

This change will affect all CLI users:

• Users will now see notifications for stable releases instead of pre-release versions
• This is likely the intended behavior for production users
• No breaking changes or backward compatibility issues

---

Overall Assessment: ✅ APPROVED

This is a straightforward and appropriate fix. The code change is correct and will improve the user experience by showing version notifications for stable releases rather than pre-release versions.

---

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2da0c21 and ce6091e.

📒 Files selected for processing (1)

• packages/cli/src/utils/version-utils.ts

---

📝 Walkthrough

Walkthrough

Changed the VERSION_CHECK_TAG constant in the version utilities from 'next' to 'latest', altering which npm tag is queried when checking for the latest version. No other logic or error handling modified.

Changes

Cohort / File(s)	Summary
Version Constants packages/cli/src/utils/version-utils.ts	Changed VERSION_CHECK_TAG constant from 'next' to 'latest', updating which npm tag is referenced for version checks.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 From "next" we hop to "latest" bright,
A simple tag makes all things right!
One line changed with purpose true,
The freshest version waits for you. ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main change: updating the VERSION_CHECK_TAG constant from 'next' to 'latest' in the version utility file.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

• 📝 Generate docstrings (stacked PR)
• 📝 Generate docstrings (commit on current branch)

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/version-check-tag

---

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