Enhance version comparison logic for Safety CLI check-updates command

[dylanpulver]

Summary: This PR improves the logic for comparing the current Safety CLI version with the latest available version during the check-updates command. Instead of just checking for the presence of a latest_available_version, we now ensure that the version comparison is accurate using the packaging library. This allows for better handling of upgrade and downgrade scenarios.

Key Changes:

1. Version comparison using packaging library:
   • We now utilize packaging.version to compare the current version (VERSION) with the latest_available_version fetched from the update check.
   • This ensures that the update message is only shown if the latest available version is greater than the current version, preventing unnecessary prompts for downgrades.
2. Downgrade message:
   • If the latest_available_version is lower than the current version, the user will now see a message explaining that they can downgrade to the latest stable version, with instructions on how to do so.
3. Refactor to avoid version naming conflict:
   • Renamed the function argument version import to packaging_version to avoid conflicts with the function input version, preventing errors during version parsing.

Why these changes were made:

• Version accuracy: The previous implementation only checked if latest_available_version existed. By using packaging.version, we ensure that the CLI correctly handles both upgrades and downgrades based on semantic versioning.
• Improved user experience: Clearer messaging for when the user is already on the latest version, and explicit guidance for downgrading if the latest version is lower than the installed one.
• Bug fix: The conflict with version caused an int attribute error, which is now resolved by renaming the import.

Summary by CodeRabbit

• New Features
  • Enhanced update checking functionality for the Safety package, providing users with clear instructions based on their current version status.
  • Users are now informed if they can upgrade, downgrade, or if they are already on the latest version.
  • Improved error handling for invalid version formats, ensuring users receive appropriate feedback.

[coderabbitai[bot]]

[!WARNING]

Rate limit exceeded

@dylanpulver has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 16 minutes and 46 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](https://coderabbit.ai/docs/faq) for further information.

📥 Commits

Files that changed from the base of the PR and between d986d198f24cb45ae4e3aa9114dae96ad12edd34 and 18127fcb8dd2de8ad8fcb0ef5c85370263e00cee.

Walkthrough

The changes enhance the check_updates function in the safety/cli.py file by implementing a version comparison mechanism. The function now checks if the latest available version is greater than, less than, or equal to the current version, providing appropriate user feedback for each scenario. This includes instructions for updating, downgrading, or confirming that the user is on the latest version. Additionally, error handling for invalid version formats has been introduced.

Changes

File	Change Summary
safety/cli.py	Enhanced check_updates function to compare current and latest available versions, improving user feedback based on version status and adding error handling for invalid formats.

Poem

In the garden of code, where updates bloom,
A rabbit hops in, dispelling the gloom.
"Check your version, dear friend, don't delay,
For newer delights are just a hop away!
Downgrade or upgrade, the choice is now clear,
With each little change, we bring you good cheer!" 🐇✨

---

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](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)

🪧 Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit , 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 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. ### 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](https://docs.coderabbit.ai/guides/configure-coderabbit) 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` ### Documentation and Community - Visit our [Documentation](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.