langchain/.github/workflows/langchain_release.yml

---
name: libs/langchain Release

on:
  workflow_dispatch:  # Allows to trigger the workflow manually in GitHub UI

jobs:
  release:
    uses:
      ./.github/workflows/_release.yml
    with:
      working-directory: libs/langchain
    secrets: inherit
(WIP) set up experimental (#7959) 2023-07-21 16:20:24 +00:00			`---`
			`name: libs/langchain Release`

			`on:`
bump releases rc0 (#8097) 2023-07-21 20:54:57 +00:00			`workflow_dispatch: # Allows to trigger the workflow manually in GitHub UI`
(WIP) set up experimental (#7959) 2023-07-21 16:20:24 +00:00
			`jobs:`
			`release:`
			`uses:`
			`./.github/workflows/_release.yml`
			`with:`
			`working-directory: libs/langchain`
Release on push to `master` instead of on closed PRs targeting it. (#9544) This is safer than the prior approach, since it's safe by default: the release workflows never get triggered for non-merged PRs, so there's no possibility of a buggy conditional accidentally letting a workflow proceed when it shouldn't have. The only loss is that publishing no longer requires a `release` label on the merged PR that bumps the version. We can add a separate CI step that enforces that part as a condition for merging into `master`, if desirable. 2023-08-21 16:57:40 +00:00			`secrets: inherit`