He-Pin opened a new pull request, #3293:
URL: https://github.com/apache/pekko/pull/3293

   ### Motivation
   Several `ActorMaterializerSettings` builder methods (`withInputBuffer`, 
`withDispatcher`), the `IOSettings` factory/constructor, and the 
`StreamRefSettings` factory were deprecated since Akka 2.6.0. Since Pekko 2.0.0 
is a major version bump, these can be safely removed from the public API.
   
   ### Modification
   - Remove `ActorMaterializerSettings.withInputBuffer` (deprecated since Akka 
2.6.0)
   - Change `ActorMaterializerSettings.withDispatcher` from public deprecated 
to `private[pekko]` (still used internally by the remote module's 
`ArterySettings`)
   - Remove `IOSettings.apply(config)` factory and deprecated binary-compat 
constructor `IOSettings(tcpWriteBufferSize: Int)`
   - Change `IOSettings` constructor from `private` to `private[stream]` for 
internal instantiation
   - Remove `StreamRefSettings.apply(config)` factory
   - Inline `IOSettings` and `StreamRefSettings` construction in 
`ActorMaterializerSettings.apply`
   - Add MiMa exclusion filters for the removed methods
   
   ### Result
   Deprecated Akka 2.6.0 era APIs are removed from the public surface while 
preserving internal functionality used by the remote module.
   
   ### Tests
   - `sbt "stream / Compile / compile" "remote / Compile / compile"` - success
   - `sbt "stream / Test / compile" "remote / Test / compile"` - success
   - `sbt "+stream / mimaReportBinaryIssues" "+remote / 
mimaReportBinaryIssues"` - no issues
   
   ### References
   None - proactive cleanup of deprecated APIs before Pekko 2.0.0 release


-- 
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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to