langchain

a7eba8b0 - Release on push to `master` instead of on closed PRs targeting it. (#9544)

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.