Limited support for AffectedModuleDetector #335
Description
TL;DR
- Ongoing support for AffectedModuleDetector will be very limited
- I’ll try to merge critical fixes when possible
- No new features planned
- No timeline for support or non-critical changes
⚠️ Project Support Update: AffectedModuleDetector
Due to current resource constraints, I will no longer be able to provide a high level of ongoing support for AffectedModuleDetector.
I will try to periodically plan time to merge critical fixes when Google makes relevant updates in the AndroidX repository. That said, there is no plan to develop or accept new features, and there is no committed timeline for reviewing, merging, or supporting additional changes.
I want to be very clear that this project has benefited greatly from the community. I’m genuinely thankful for all the contributions, discussions, and features that developers have put into Affected Module Detector over time. The support and effort from the community have been meaningful and appreciated.
I understand that this is unfortunate for teams that rely on this tool, and I regret the impact this change may have. While I can’t offer the level of support I previously did, I hope the existing functionality continues to be useful, and I appreciate everyone’s understanding.
If any individual or organization is interested in taking over ownership or long-term maintenance of AffectedModuleDetector, please feel free to reach out via this issue so we can discuss next steps.
Thank you again to everyone who has contributed and supported this project.