Fix Ruby 3.2 File.exists? Deprecation

[thdurante]

WHY

Ruby 3.2 removed the already deprecated File.exists? method.
https://www.ruby-lang.org/en/news/2022/12/25/ruby-3-2-0-released/

HOW

• Use File.exist? instead

Previews:

Summary by CodeRabbit

Summary by CodeRabbit

• Chores
  • Updated gem version from 1.2.6 to 1.2.7.
  • Changed dependency method for nio4r, rb-readline, and timers to the updated standard.
  • Modified environment variable for the "Setup credentials" step in the CI workflow.
• Bug Fixes
  • Corrected file existence check method from File.exists? to File.exist? in CLI module.

[coderabbitai]

Walkthrough

The pull request includes changes to the deploy-agent gem specification, where the version number is updated from 1.2.6 to 1.2.7, and the method for adding dependencies is modified from s.add_runtime_dependency to s.add_dependency for the dependencies nio4r, rb-readline, and timers. Additionally, the write_pid method in the CLI class is updated to use the current method File.exist? instead of the deprecated File.exists?. The CI workflow is also modified to change the source of the RUBYGEMS_API_KEY environment variable.

Changes

File	Change Summary
deploy-agent.gemspec	Version updated from 1.2.6 to 1.2.7; dependency method changed from s.add_runtime_dependency to s.add_dependency for nio4r, rb-readline, and timers.
lib/deploy_agent/cli.rb	Updated File.exists? to File.exist? in write_pid method.
.github/workflows/ci.yml	Environment variable updated from RUBYGEMS_API_KEY: ${{secrets.KRYSTAL_RUBYGEMS_API_KEY}} to RUBYGEMS_API_KEY: ${{secrets.RUBYGEMS_API_KEY}}.

Poem

🐰 A version hop, a method's grace,
Gems polished with a rabbit's trace.
exists? to exist?, a subtle dance,
Code refining with each small chance.
Deploy Agent leaps, version bright! 🚀

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between d489256 and 7992096.

📒 Files selected for processing (1)

• .github/workflows/ci.yml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: Analyze (ruby)

🔇 Additional comments (1)

.github/workflows/ci.yml (1)

51-51: LGTM! The secret reference follows security best practices.

The change to use secrets.RUBYGEMS_API_KEY maintains proper security practices:

• Uses the secrets context for sensitive data
• Credentials file has correct permissions (0600)
• Secret is properly scoped for its purpose

---

🪧 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.
  • 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 generate docstrings to generate docstrings for this PR. (Beta)
• @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 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 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.