Skip to content

chore(main): release python 0.7.32#658

Open
rogeriochaves wants to merge 1 commit into
mainfrom
release-please--branches--main--components--python
Open

chore(main): release python 0.7.32#658
rogeriochaves wants to merge 1 commit into
mainfrom
release-please--branches--main--components--python

Conversation

@rogeriochaves

@rogeriochaves rogeriochaves commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.7.32 (2026-07-02)

Features

Bug Fixes


This PR was generated with Release Please. See documentation.

@github-actions github-actions Bot added the low-risk-change PR qualifies as low-risk per policy and can be merged without manual review label Jun 11, 2026
github-actions[bot]
github-actions Bot previously approved these changes Jun 11, 2026

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved by automation: PR qualifies as low-risk-change under the documented policy.

@rogeriochaves rogeriochaves force-pushed the release-please--branches--main--components--python branch from ba77ba6 to 3c786e0 Compare June 11, 2026 10:48
@github-actions github-actions Bot added low-risk-change PR qualifies as low-risk per policy and can be merged without manual review and removed low-risk-change PR qualifies as low-risk per policy and can be merged without manual review labels Jun 11, 2026
github-actions[bot]
github-actions Bot previously approved these changes Jun 11, 2026

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved by automation: PR qualifies as low-risk-change under the documented policy.

@rogeriochaves rogeriochaves force-pushed the release-please--branches--main--components--python branch from 3c786e0 to 389985a Compare June 12, 2026 15:23
@github-actions github-actions Bot added low-risk-change PR qualifies as low-risk per policy and can be merged without manual review and removed low-risk-change PR qualifies as low-risk per policy and can be merged without manual review labels Jun 12, 2026
github-actions[bot]
github-actions Bot previously approved these changes Jun 12, 2026

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved by automation: PR qualifies as low-risk-change under the documented policy.

@rogeriochaves rogeriochaves force-pushed the release-please--branches--main--components--python branch from 389985a to a9cf15c Compare June 16, 2026 10:28
@coderabbitai

coderabbitai Bot commented Jun 16, 2026

Copy link
Copy Markdown

Review Change Stack

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review

Walkthrough

Bumps the langwatch-scenario Python package version from 0.7.31 to 0.7.32 in pyproject.toml and .release-please-manifest.json, and adds a corresponding v0.7.32 changelog section documenting new features and bug fixes.

Changes

Python v0.7.32 Release Bump

Layer / File(s) Summary
Version field updates
python/pyproject.toml, .release-please-manifest.json
Version field updated to 0.7.32 in pyproject.toml and the release-please manifest.
v0.7.32 changelog release documentation
python/CHANGELOG.md
CHANGELOG.md updated with v0.7.32 release section including voice-related features (#660, #666, #673) and multiple bug fixes (#488, #655, #664, voice/TypeScript turn-commit/next-turn re-engagement, active-response guard, and hosted ElevenLabs timeout documentation).

🐇 A hop, a skip, a version bump so neat,
From thirty-one to thirty-two — how sweet!
Features and fixes, all logged with care,
The changelog entry placed right there.
A tiny patch, but oh so complete! 🎉

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title 'chore(main): release python 0.7.32' is directly related to the changeset, which updates version numbers across manifest, changelog, and pyproject files from 0.7.31 to 0.7.32.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Description check ✅ Passed The description matches this release PR and summarizes the version bump and changelog updates.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch release-please--branches--main--components--python

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@github-actions github-actions Bot added low-risk-change PR qualifies as low-risk per policy and can be merged without manual review and removed low-risk-change PR qualifies as low-risk per policy and can be merged without manual review labels Jun 16, 2026
github-actions[bot]
github-actions Bot previously approved these changes Jun 16, 2026

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved by automation: PR qualifies as low-risk-change under the documented policy.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@python/pyproject.toml`:
- Line 7: The `__version__` constant in `python/scenario/__init__.py` is out of
sync with the package version in `pyproject.toml`. Update the `__version__`
variable from its current value of "0.1.0" to "0.7.32" to match the package
version specified in `pyproject.toml`. This ensures consistency across the
codebase and prevents confusion for any external code or future functionality
that may reference this constant.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 5c00412f-8880-4db5-b09e-e3f8360ef9df

📥 Commits

Reviewing files that changed from the base of the PR and between 4b99682 and a9cf15c.

📒 Files selected for processing (3)
  • .release-please-manifest.json
  • python/CHANGELOG.md
  • python/pyproject.toml

Comment thread python/pyproject.toml
[project]
name = "langwatch-scenario"
version = "0.7.31"
version = "0.7.32"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Find all __version__ declarations in Python files
rg -n '__version__\s*=' --type=py

Repository: langwatch/scenario

Length of output: 116


🏁 Script executed:

# Check all version-related references in Python files
rg -in 'VERSION|version\s*=' --type=py -A 1 | head -100

Repository: langwatch/scenario

Length of output: 13571


🏁 Script executed:

# Check if scenario.__version__ is imported or referenced anywhere
rg -n 'from.*scenario.*import.*__version__|scenario\.__version__' --type=py

Repository: langwatch/scenario

Length of output: 44


🏁 Script executed:

# Check pyproject.toml for any version-related configurations
cat python/pyproject.toml | head -50

Repository: langwatch/scenario

Length of output: 1926


🏁 Script executed:

# Look for any version synchronization scripts or documentation
find . -type f \( -name "*version*" -o -name "*VERSION*" \) | grep -v __pycache__ | grep -v .git

Repository: langwatch/scenario

Length of output: 8331


Update python/scenario/__init__.py to set __version__ = "0.7.32" to match the package version.

The module's __version__ constant is outdated at "0.1.0" while the package version in pyproject.toml is "0.7.32". Though nothing in the codebase currently checks this constant, updating it maintains consistency and prevents confusion for external code or future functionality that may reference it.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@python/pyproject.toml` at line 7, The `__version__` constant in
`python/scenario/__init__.py` is out of sync with the package version in
`pyproject.toml`. Update the `__version__` variable from its current value of
"0.1.0" to "0.7.32" to match the package version specified in `pyproject.toml`.
This ensures consistency across the codebase and prevents confusion for any
external code or future functionality that may reference this constant.

@rogeriochaves rogeriochaves force-pushed the release-please--branches--main--components--python branch 3 times, most recently from b7b7937 to 0f6a424 Compare June 17, 2026 10:58
@github-actions github-actions Bot added low-risk-change PR qualifies as low-risk per policy and can be merged without manual review and removed low-risk-change PR qualifies as low-risk per policy and can be merged without manual review labels Jun 17, 2026
github-actions[bot]
github-actions Bot previously approved these changes Jun 17, 2026

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved by automation: PR qualifies as low-risk-change under the documented policy.

@rogeriochaves rogeriochaves force-pushed the release-please--branches--main--components--python branch from 0f6a424 to 223bd44 Compare June 17, 2026 16:14
@github-actions github-actions Bot removed the low-risk-change PR qualifies as low-risk per policy and can be merged without manual review label Jun 17, 2026
@rogeriochaves rogeriochaves force-pushed the release-please--branches--main--components--python branch from ea458a6 to 828b8bb Compare June 24, 2026 20:48
@github-actions github-actions Bot added low-risk-change PR qualifies as low-risk per policy and can be merged without manual review and removed low-risk-change PR qualifies as low-risk per policy and can be merged without manual review labels Jun 24, 2026
github-actions[bot]
github-actions Bot previously approved these changes Jun 24, 2026

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved by automation: PR qualifies as low-risk-change under the documented policy.

@rogeriochaves rogeriochaves force-pushed the release-please--branches--main--components--python branch from 828b8bb to 92a5895 Compare June 25, 2026 09:23
@github-actions github-actions Bot added low-risk-change PR qualifies as low-risk per policy and can be merged without manual review and removed low-risk-change PR qualifies as low-risk per policy and can be merged without manual review labels Jun 25, 2026
github-actions[bot]
github-actions Bot previously approved these changes Jun 25, 2026

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved by automation: PR qualifies as low-risk-change under the documented policy.

@rogeriochaves rogeriochaves force-pushed the release-please--branches--main--components--python branch from 92a5895 to fca400d Compare June 26, 2026 08:06
@github-actions github-actions Bot added low-risk-change PR qualifies as low-risk per policy and can be merged without manual review and removed low-risk-change PR qualifies as low-risk per policy and can be merged without manual review labels Jun 26, 2026
github-actions[bot]
github-actions Bot previously approved these changes Jun 26, 2026

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved by automation: PR qualifies as low-risk-change under the documented policy.

@rogeriochaves rogeriochaves force-pushed the release-please--branches--main--components--python branch from fca400d to f98d6fe Compare July 1, 2026 13:10
@github-actions github-actions Bot added low-risk-change PR qualifies as low-risk per policy and can be merged without manual review and removed low-risk-change PR qualifies as low-risk per policy and can be merged without manual review labels Jul 1, 2026
github-actions[bot]
github-actions Bot previously approved these changes Jul 1, 2026

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved by automation: PR qualifies as low-risk-change under the documented policy.

@rogeriochaves rogeriochaves force-pushed the release-please--branches--main--components--python branch from f98d6fe to 6c3284e Compare July 2, 2026 11:30
@github-actions github-actions Bot added low-risk-change PR qualifies as low-risk per policy and can be merged without manual review and removed low-risk-change PR qualifies as low-risk per policy and can be merged without manual review labels Jul 2, 2026
@github-actions

github-actions Bot commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

Automated low-risk assessment

This PR was evaluated against the repository's Low-Risk Pull Requests procedure.

  • Scope: Bump python package version to 0.7.32 and update CHANGELOG.md and .release-please-manifest.json.
  • Exclusions confirmed: no changes to auth, security settings, database schema, business-critical logic, or external integrations.
  • Classification: low-risk-change under the documented policy.

The PR only updates release metadata and documentation: it bumps the Python package version (pyproject.toml and .release-please-manifest.json) and adds the 0.7.32 changelog entries. It does not touch authentication/authorization, secrets, database schemas, business‑critical logic, or third‑party integrations, so it meets the low-risk criteria.

An approving review has been submitted by automation. The PR may merge once required CI checks pass.

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved by automation: PR qualifies as low-risk-change under the documented policy.

@langwatch-agent langwatch-agent added the hound-checked Triaged by the pr-hound agent at the current head SHA label Jul 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

autorelease: pending hound-checked Triaged by the pr-hound agent at the current head SHA low-risk-change PR qualifies as low-risk per policy and can be merged without manual review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants