stagehand-python@4.4.0a0.dev1670: chore : migrate browse to oxlint ( 3377)
Browserbase Stagehand releases published stagehand-python@4.4.0a0.dev1670: chore : migrate browse to oxlint ( 3377). why the monorepo uses oxlint what changed ported the cli specific eslint rules into oxlint removed eslint dep & config/scripts Summary by cubic Migrates packages/cli linting from ESLint to oxlint so the CLI uses the same linter as the…
Why this signal matters
Browserbase Stagehand releases published stagehand-python@4.4.0a0.dev1670: chore : migrate browse to oxlint ( 3377). This automated release-watch entry was generated from the project's official GitHub release feed and is kept separate from human-reviewed editorial analysis. Release notes: why the monorepo uses oxlint what changed ported the cli specific eslint rules into oxlint removed eslint dep & config/scripts Summary by cubic Migrates packages/cli linting from ESLint to oxlint so the CLI uses the same linter as the monorepo. Ports the CLI's ESLint rules (ESLint recommended, typescript-eslint recommended, security, and no-restricted-syntax selectors) into custom oxlint rules and overrides under rules/oxlint/ , adding new stagehand/no-dynamic-code and stagehand/no-legacy-octal rules to cover nonliteral eval , dynamic Function construction, and legacy octal literals in CommonJS. Adds integration tests that verify the new suite rejects the same violations, accepts the same valid code, and honors the same ignore patterns as the old ESLint config. Replaces the eslint / eslint:fix scripts with oxlint / oxlint:fix , deletes eslint.config.mjs , and removes ESLint…
Actionable summary
Treat stagehand-python@4.4.0a0.dev1670: chore : migrate browse to oxlint ( 3377) as an official release signal. Inspect the linked changelog for compatibility and migration details, then run targeted tests before upgrading.
- Agent usefulness
- 77/100
- Confidence
- 96%
- Canonical data
- JSON + Markdown
What builders should check
- Review the official Browserbase Stagehand releases release notes before upgrading.
- Check compatibility, migration, and security notes against your current agent stack.
- Run focused regression tests before production rollout.