Skip to content

Revert breaking change of minimum required ruby version introduced due to the latest io-event gem#399

Merged
ioquatix merged 1 commit intosocketry:mainfrom
jjatinggoyal:revert-breaking-change
Jul 24, 2025
Merged

Revert breaking change of minimum required ruby version introduced due to the latest io-event gem#399
ioquatix merged 1 commit intosocketry:mainfrom
jjatinggoyal:revert-breaking-change

Conversation

@jjatinggoyal
Copy link
Copy Markdown
Contributor

I'm using async 2.25.0 in a Rails app running on Ruby 3.2.2. I tried to upgrade to async 2.26.0, but the io-async gem's latest version (commit) has introduced a breaking change on the minimum required Ruby version (now requires Ruby >=3.2.6 instead of >=3.2).

This commit reverts the minimum required version of io-async gem in async to ~> 1.11 to maintain async gem's compatibility with Ruby >=3.2

Type of Change

  • Revert Breaking change.

Contribution

@jjatinggoyal jjatinggoyal force-pushed the revert-breaking-change branch from 6ad2a57 to 10a052b Compare July 16, 2025 12:37
@ioquatix
Copy link
Copy Markdown
Member

A better option would be for you to move to the latest 3.2.x release, as there are some issues with earlier releases. However, I'm willing to entertain this request.

@jjatinggoyal
Copy link
Copy Markdown
Contributor Author

@ioquatix I agree we should just use the latest 3.2.x, but I can't upgrade Ruby in our app without getting a bunch of approvals (I work at a corporate).

So I'd be grateful if this PR can be merged for the benefit of apps on < 3.2.6

@jjatinggoyal
Copy link
Copy Markdown
Contributor Author

Hey @ioquatix, can this be merged?

@ioquatix ioquatix merged commit 8af530a into socketry:main Jul 24, 2025
35 of 38 checks passed
@ioquatix
Copy link
Copy Markdown
Member

Yes, thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants