chore(deps): update dependency pry-byebug to "~> 3.12.0"

[renovate-bot]

This PR contains the following updates:

Package	Change	Age	Confidence
pry-byebug (changelog)	"~> 3.11.0" → "~> 3.12.0"

---

Release Notes

deivid-rodriguez/pry-byebug (pry-byebug)

v3.12.0

Compare Source

Added

• Allow usage with Byebug 13 (#​466).
• Allow pry 0.16 (#​462).

Removed

• Support for Ruby 3.1. Pry-byebug no longer installs on these platforms (#​467).

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[gemini-code-assist]

Summary of Changes

Hello @renovate-bot, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the pry-byebug gem to its latest patch version, ~> 3.12.0. This ensures the project benefits from the newest features and compatibility improvements, specifically enabling usage with Byebug 13 and Pry 0.16, while also aligning with the updated Ruby version support policy of the gem.

Highlights

• Dependency Update: The pry-byebug gem has been updated from version ~> 3.11.0 to ~> 3.12.0.
• pry-byebug v3.12.0 Release Notes: This new version introduces support for Byebug 13 and Pry 0.16. It also removes support for Ruby 3.1.

Changelog

• Gemfile
  • Updated the version constraint for the pry-byebug gem from ~> 3.11.0 to ~> 3.12.0.

Activity

• This pull request was automatically generated by renovate-bot to update the pry-byebug dependency.
• Automerge is currently disabled for this PR, requiring a manual merge.
• The PR is configured to rebase automatically if conflicts arise or if the rebase/retry checkbox is ticked.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates the pry-byebug dependency to version ~> 3.12.0. This update introduces a critical compatibility issue, as the new version of pry-byebug drops support for Ruby 3.1, while this project still officially supports it according to the .gemspec file. This would break the development environment for anyone using Ruby 3.1. I have added a comment recommending that this change be reverted to maintain compatibility.

[gemini-code-assist]

This update to pry-byebug v3.12.0 introduces a critical compatibility issue. The release notes for this version state that support for Ruby 3.1 has been dropped. However, the project's activerecord-spanner-adapter.gemspec file still lists Ruby 3.1 as a supported version (required_ruby_version = ">= 3.1").

This will break the development environment for anyone using Ruby 3.1, as bundle install will fail. To maintain compatibility, please revert this change. If dropping Ruby 3.1 support is intended, it should be done as a separate, deliberate change that also updates the .gemspec.

gem "pry-byebug", "~> 3.11.0"