New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
create github action to auto publish new pypi package when version changes #26
Comments
* Adopts [Poetry](https://python-poetry.org/) as a dependency manager * Introduces dependency version requirements * Deprecates Python 3.7 support **TODO** - [x] Update developer guide - [x] Add back `playwright`, `manifest-ml`, and `jupyter` to dependency group **Not Doing => Fast Follow** - Investigate single source for version, perhaps relying on GitHub tags and [tackling this issue](#26)
I'm happy to take this issue on next. @hwchase17, what's your desired release workflow? Do you want the version to be manually specified? One proposal would be a separate workflow from merging that would involve pushing a git tag, triggering a release workflow that creates a GitHub release and pushes the artifact to PyPI. |
@shoelsch sorry im just seeing this now! this would be great what about something like https://www.seanh.cc/2022/05/21/publishing-python-packages-from-github-actions/? happy to discuss this more as well, im not 100% sure |
* Adopts [Poetry](https://python-poetry.org/) as a dependency manager * Introduces dependency version requirements * Deprecates Python 3.7 support **TODO** - [x] Update developer guide - [x] Add back `playwright`, `manifest-ml`, and `jupyter` to dependency group **Not Doing => Fast Follow** - Investigate single source for version, perhaps relying on GitHub tags and [tackling this issue](langchain-ai/langchain#26)
* Adopts [Poetry](https://python-poetry.org/) as a dependency manager * Introduces dependency version requirements * Deprecates Python 3.7 support **TODO** - [x] Update developer guide - [x] Add back `playwright`, `manifest-ml`, and `jupyter` to dependency group **Not Doing => Fast Follow** - Investigate single source for version, perhaps relying on GitHub tags and [tackling this issue](langchain-ai/langchain#26)
Hi, @hwchase17! I'm helping the LangChain team manage their backlog and wanted to let you know that we are marking this issue as stale. From what I understand, the issue is about creating a GitHub action for automatically publishing a new PyPI package when the version changes. @shoelsch has offered to work on it and proposed a workflow involving pushing a git tag and triggering a release workflow. You expressed interest in this proposal and suggested looking into a blog post for more information. Before we close this issue, we wanted to check if it is still relevant to the latest version of the LangChain repo. If you could let us know, the LangChain team will take a look. Otherwise, if we don't hear back from you within 7 days, the issue will be automatically closed. Thanks! |
fix collab links
No description provided.
The text was updated successfully, but these errors were encountered: