Kazuhiro Sera

Let us close this issue now. If you have any follow-up questions on it, please feel free to write in!

@roman-somyk-sp >Do you have any estimates of when it will be released? We don't have anything that we can share at this moment. To know the progress on that later...

@musketyr As I mentioned at https://github.com/slackapi/java-slack-sdk/pull/1056#issuecomment-1255879894, you can use your own service instance with the additional method.

Hi @musketyr, please consider implementing something like this on your own. I believe that this is flexible enough for any enhancements that you may want to add in the future....

@musketyr Regarding the Amazon S3 implementation, I see your point. However, we still don't plan to add all the requested method supports to the interface. So, for your specific use...

Happy to see you've implemented your own solution for this issue: https://github.com/agorapulse/micronaut-slack/blob/master/libs/micronaut-slack-core/src/main/java/com/agorapulse/slack/install/enumerate/AmazonS3InstallationEnumerationService.java Great work! Since we've shared all the information we have for this topic, let us close this issue...

Still waiting for logback-classic 1.3.0 release: https://github.com/qos-ch/logback/tags

**EDIT:** I might be wrong. Perhaps, if we release a new version with slf4j-api 2.0 dependency, real-world apps such as Spring Boot web apps would be suffered from behavior changes....

Another factor we should consider for this upgrade is that logback-classic 1.4 and perhaps other implementations of sfl4j-api v2 no longer supports Java 1.8. Yes, the version is long-lived old...

Hi @Flyer4109, thanks for writing in. The reason why the "workflow execute" event handling is executed asynchronously in a different thread is mentioned in the code comment as below: >As...