kpumuk opened a new pull request, #3742:
URL: https://github.com/apache/thrift/pull/3742

   <!-- Explain the changes in the pull request below: -->
   
   Ruby 2.7 was released on December 25, 2019 and [reached end of life on March 
31, 2023](https://www.ruby-lang.org/en/downloads/branches/), but the Thrift 
Ruby gem still declares and tests Ruby 2.7 support.
   
   This raises the gem's minimum Ruby version to 3.0 and aligns the language 
matrix, Ruby documentation, RuboCop target, build matrix, and static-analysis 
workflow. The pure-Ruby CI variant moves to the new minimum instead of being 
removed.
   
   The updated lint target also exposes a few behavior-preserving idiomatic 
cleanups: direct collection mapping, an endless range for partial socket 
writes, removal of a redundant regexp freeze, and removal of obsolete gemspec 
boilerplate.
   
   This is a breaking support-policy change. Applications still running Ruby 
2.7 must remain on an earlier Thrift gem until they upgrade Ruby.
     
   
   <!-- We recommend you review the checklist/tips before submitting a pull 
request. -->
   
   - [x] Did you create an [Apache 
Jira](https://issues.apache.org/jira/projects/THRIFT/issues/) ticket?  
([THRIFT-6154](https://issues.apache.org/jira/browse/THRIFT-6154))
   - [x] If a ticket exists: Does your pull request title follow the pattern 
"THRIFT-NNNN: describe my issue"?
   - [x] Did you squash your changes to a single commit?  (not required, but 
preferred)
   - [ ] Did you do your best to avoid breaking changes?  If one was needed, 
did you label the Jira ticket with "Breaking-Change"?
   - [ ] If your change does not involve any code, include `[skip ci]` anywhere 
in the commit message to free up build resources.
   
   <!--
     The Contributing Guide at:
     https://github.com/apache/thrift/blob/master/CONTRIBUTING.md
     has more details and tips for committing properly.
   -->
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to