chore(main): release javascript 0.5.0

[rogeriochaves]

🤖 I have created a release beep boop

0.5.0 (2026-07-01)

⚠ BREAKING CHANGES

• voice: the EL adapter's SDK migration removes the public WebSocketLike test-seam type (superseded by the SDK's own WebSocketFactory). Niche, but note it for the version bump.

Bug Fixes

• security: raise vite 8.x floor to >=8.0.16 across scenario workspaces (#709) (42d877e)
• voice: real voice-in by default for hosted ElevenLabs ConvAI (#707) (267426b)

---

This PR was generated with Release Please. See documentation.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: df7fd0ea-802e-49e1-a6b8-17d02ee05d1e

📥 Commits

Reviewing files that changed from the base of the PR and between a512456 and ff274a1.

⛔ Files ignored due to path filters (1)

• javascript/package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (3)

• .release-please-manifest.json
• javascript/CHANGELOG.md
• javascript/package.json

✅ Files skipped from review due to trivial changes (2)

• javascript/CHANGELOG.md
• .release-please-manifest.json

---

Walkthrough

Bumps the javascript release manifest and package version from 0.4.15 to 0.5.0, and adds the corresponding changelog entry for v0.5.0. The changelog includes a breaking-change note for the EL adapter SDK migration plus bug-fix entries for the Vite minimum version and hosted ElevenLabs ConvAI default behavior.

Changes

JavaScript 0.5.0 release

Layer / File(s)	Summary
Release metadata and changelog .release-please-manifest.json, javascript/package.json, javascript/CHANGELOG.md	The javascript release version is updated to 0.5.0 in the manifest and package metadata, and the changelog adds the v0.5.0 entry with breaking-change and bug-fix notes.

Possibly related PRs

• langwatch/scenario#704: Updates the same JavaScript release/versioning surfaces and changelog flow in a closely related release bump.

Suggested labels: autorelease: tagged

Poem

A rabbit hops with version cheer,
0.5.0 is finally here.
🥕 The changelog glows, the numbers sing,
and release notes flutter on the wing.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly describes the main change: releasing the JavaScript package at version 0.5.0.
Description check	✅ Passed	The description matches the release update and summarizes the version bump, breaking change, and bug fixes.
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.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release-please--branches--main--components--javascript

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[github-actions]

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

[coderabbitai]

🧹 Nitpick comments (1)

javascript/package.json (1)

1-3: 📐 Maintainability & Code Quality | 🔵 Trivial

Lockfile synchronization appears incomplete or unnecessary for this package structure

The javascript/package-lock.json references version 0.4.16, but javascript/pnpm-lock.yaml does not contain any references to 0.4.16. Additionally, javascript/pnpm-workspace.yaml exists. If this package uses pnpm as the primary package manager, the package-lock.json might be irrelevant, but the pnpm-lock.yaml should reflect the current package version. Verify that pnpm-lock.yaml is generated correctly and updated during the release process.

javascript/pnpm-lock.yaml | javascript/package-lock.json | javascript/pnpm-workspace.yaml

- "name": "`@langwatch/scenario`",
- "version": "0.4.16",

🤖 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 `@javascript/package.json` around lines 1 - 3, The version sync between package
metadata and lockfiles looks inconsistent for the JavaScript package. Verify
whether this repo is using pnpm via pnpm-workspace.yaml and, if so, make sure
pnpm-lock.yaml is regenerated and committed so it reflects the current package
version from package.json. If package-lock.json is not used in this workspace,
remove it or ensure the release process only updates the pnpm lockfile, using
package.json, pnpm-lock.yaml, and pnpm-workspace.yaml as the reference points.

🤖 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.

Nitpick comments:
In `@javascript/package.json`:
- Around line 1-3: The version sync between package metadata and lockfiles looks
inconsistent for the JavaScript package. Verify whether this repo is using pnpm
via pnpm-workspace.yaml and, if so, make sure pnpm-lock.yaml is regenerated and
committed so it reflects the current package version from package.json. If
package-lock.json is not used in this workspace, remove it or ensure the release
process only updates the pnpm lockfile, using package.json, pnpm-lock.yaml, and
pnpm-workspace.yaml as the reference points.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 50304ca2-3ac4-40e6-a05b-912ec4acac7d

📥 Commits

Reviewing files that changed from the base of the PR and between 42d877e and a512456.

⛔ Files ignored due to path filters (1)

• javascript/package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (3)

• .release-please-manifest.json
• javascript/CHANGELOG.md
• javascript/package.json

[github-actions]

Automated low-risk assessment

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

• Scope: Bump javascript package version to 0.5.0; update javascript/CHANGELOG.md, package.json, package-lock.json, and .release-please-manifest.json with release metadata.
• 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 (version bump in javascript package.json and package-lock, CHANGELOG, and .release-please-manifest) and does not touch authentication/authorization, secrets, database schemas, business-critical logic, or external integrations. All changes are documentation/release-related and are easily reversible. Therefore 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]

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

[rogeriochaves]

🤖 Created releases:

• javascript/v0.5.0

🌻