This project uses release-please to automate releases for both JavaScript and Python packages in our monorepo.
- Conventional Commits: All commits must follow the Conventional Commits specification
- Automatic PRs: Release Please creates release PRs when it detects releasable changes
- Automated Publishing: When release PRs are merged, packages are automatically published
type(scope): description
[optional body]
[optional footer]
feat:- New feature (minor version bump)fix:- Bug fix (patch version bump)feat!:orfix!:- Breaking change (major version bump)chore:,docs:,refactor:- Non-breaking changes that will be included in releases
- Package:
@langwatch/scenario - Release Type:
node - Tag Pattern:
javascript/v{version}
- Package:
langwatch-scenario - Release Type:
python - Tag Pattern:
python/v{version}
- Make Changes: Create PRs with conventional commit messages
- Merge to Main: Release Please will create release PRs automatically
- Review Release PR: Check the generated changelog and version bumps
- Merge Release PR: This triggers the automated publishing workflows
To force a release or fix issues:
- Add
release-please:force-runlabel to any merged PR - Or run the release-please GitHub Action manually
.release-please-config.json- Main configuration.release-please-manifest.json- Current version tracking.github/workflows/release-please.yml- GitHub Action workflow
- No release PR created: Ensure commits follow conventional format
- Wrong version bump: Check commit message types
- Failed publish: Check secrets (NPM_TOKEN, PYPI_API_TOKEN) are set