We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
As per the title. I don't believe there are any actual code conflicts, so expanding the version range should suffice.
I don't know how risky this would be, but does it make sense to expand the version constraint to only cover the major version rather than major+minor?
The text was updated successfully, but these errors were encountered:
As per the title. I don't believe there are any actual code conflicts, so expanding the version range should suffice. I don't know how risky this would be, but does it make sense to expand the version constraint to only cover the major version rather than major+minor?
Same is true for irb 1.13.2 with ruby 3.3.3. The proposed fix would be nice.
Sorry, something went wrong.
Thanks for your reports, I'll take a look within the next days
5f9ac3f
Ah, irb v1.14.0 has been recently released a couple of days ago. Could you do another update? 😅
Successfully merging a pull request may close this issue.
As per the title. I don't believe there are any actual code conflicts, so expanding the version range should suffice.
I don't know how risky this would be, but does it make sense to expand the version constraint to only cover the major version rather than major+minor?
The text was updated successfully, but these errors were encountered: