langchain/.github/workflows/langchain_experimental_release.yml

---
name: libs/experimental Release

on:
  push:
    branches:
      - master
    paths:
      - 'libs/experimental/pyproject.toml'
  workflow_dispatch:  # Allows to trigger the workflow manually in GitHub UI

jobs:
  release:
    uses:
      ./.github/workflows/_release.yml
    with:
      working-directory: libs/experimental
    secrets: inherit
add experimental release action (#8096) 2023-07-21 20:38:35 +00:00			`---`
scheduled tests GHA (#8879) Adding scheduled daily GHA that runs marked integration tests. To start just marking some tests in test_openai 2023-08-08 21:55:25 +00:00			`name: libs/experimental Release`
add experimental release action (#8096) 2023-07-21 20:38:35 +00:00
			`on:`
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			`push:`
add experimental release action (#8096) 2023-07-21 20:38:35 +00:00			`branches:`
			`- master`
			`paths:`
			`- 'libs/experimental/pyproject.toml'`
bump releases rc0 (#8097) 2023-07-21 20:54:57 +00:00			`workflow_dispatch: # Allows to trigger the workflow manually in GitHub UI`
add experimental release action (#8096) 2023-07-21 20:38:35 +00:00
			`jobs:`
			`release:`
			`uses:`
			`./.github/workflows/_release.yml`
			`with:`
			`working-directory: libs/experimental`
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`