2023-07-21 16:20:24 +00:00
|
|
|
---
|
|
|
|
|
name: libs/langchain Release
|
|
|
|
|
|
|
|
|
|
on:
|
2023-07-21 20:54:57 +00:00
|
|
|
workflow_dispatch: # Allows to trigger the workflow manually in GitHub UI
|
2023-07-21 16:20:24 +00:00
|
|
|
|
|
|
|
|
jobs:
|
|
|
|
|
release:
|
|
|
|
|
uses:
|
|
|
|
|
./.github/workflows/_release.yml
|
|
|
|
|
with:
|
|
|
|
|
working-directory: libs/langchain
|
2023-08-21 16:57:40 +00:00
|
|
|
secrets: inherit
|
2023-10-04 14:27:08 +00:00
|
|
|
|
|
|
|
|
# N.B.: It's possible that PyPI doesn't make the new release visible / available
|
|
|
|
|
# immediately after publishing. If that happens, the docker build might not
|
|
|
|
|
# create a new docker image for the new release, since it won't see it.
|
|
|
|
|
#
|
|
|
|
|
# If this ends up being a problem, add a check to the end of the `_release.yml`
|
|
|
|
|
# workflow that prevents the workflow from finishing until the new release
|
|
|
|
|
# is visible and installable on PyPI.
|
|
|
|
|
release-docker:
|
|
|
|
|
needs:
|
|
|
|
|
- release
|
|
|
|
|
uses:
|
|
|
|
|
./.github/workflows/langchain_release_docker.yml
|
2023-10-05 18:23:27 +00:00
|
|
|
secrets: inherit
|
