I started with my first project and came across a bug and there was a workaround which worked, but decided to open source contribute and then came across the announcement which says langchain-community is sunset immediately with no new contributions accepted. For anyone hitting bugs post-sunset:
Is the only option to fork and fix locally?
Will bug fix PRs be rejected?
Should we create standalone packages for bug fixes?
Anyone else facing this? What’s your approach?
I would suggest either using a fork and applying fixes there, or creating a standalone package specifically for bug fixes.
In my current project, we had a few dependencies on langchain-community, but since it has been deprecated, I decided to maintain my own fork so that I can apply future fixes and updates as needed.
Thanks for the response. Regarding standalone packages, I looked through the existing integrations and didn’t find a dedicated package for FAISS. It is yet to be created.
So, until then, any encountered issues may require developers to research and maintain local forks for fixes. Won’t this lead to duplicate effort even when the same issue has already been encountered and resolved by others.
Unfortunately, at the moment, local forks are the way. However, if you can share your fork with the community, it will be great as well, so that others can maintain the same fork as well.
Ok Thanks 
@Aashishkumar-07 If you are happy, can you mark the last answer as the solution so this thread is marked as solved.