fix: update browser-use-sdk from 2.0.15 to 3.4.1#4605
fix: update browser-use-sdk from 2.0.15 to 3.4.1#4605octo-patch wants to merge 1 commit intobrowser-use:mainfrom
Conversation
) The strict pin on browser-use-sdk==2.0.15 prevented users from installing the package alongside other packages requiring newer SDK versions. No 2.x patch releases exist after 2.0.15 (the SDK went directly to 3.x), so relaxing the pin means upgrading to 3.x. SDK 3.x introduced breaking API changes that required code updates: - Rename skills.list_skills() -> skills.list() - Rename skills.execute_skill() -> skills.execute() - SkillResponse.id changed from str to UUID (fixed with str() coercion) - SkillsGenerationStatus changed from Literal to Enum (fixed .value access) - Import paths updated from deprecated browser_use_sdk.types.* to top-level browser_use_sdk exports
|
|
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| - | - | Generic High Entropy Secret | 3f9520c | examples/glazyr_benchmark.py | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
Fixes #4588
Problem
browser-use-sdkwas pinned to==2.0.15, but no 2.x patch versions exist after 2.0.15 — the SDK went directly from 2.0.15 to 3.0.3. This pin prevented users from installing browser-use alongside other packages that require newer SDK versions.Solution
Updated the pin to
browser-use-sdk==3.4.1(latest) and fixed the breaking API changes introduced in SDK 3.x:skills.list_skills()skills.list()skills.execute_skill(skill_id=...)skills.execute(skill_id, ...)SkillResponse.idtypestrUUIDSkillsGenerationStatustypeLiteral["finished", ...]Enumbrowser_use_sdk.types.*browser_use_sdk(top-level)The old
browser_use_sdk.types.*import paths still work via backward-compat stubs in 3.x, but they are deprecated and scheduled for removal, so this PR also migrates to the recommended top-level imports.Testing
SkillListResponse.items,SkillResponse.parameters,ExecuteSkillResponse.success/error/latency_msfields are structurally identicaltypes.*stubs in 3.4.1 re-export fromgenerated.v2.modelsconfirming backward compatibility at the import levelSummary by cubic
Upgrade
browser-use-sdkto3.4.1and update our skills code to the 3.x APIs to unblock installs with newer SDK versions. Fixes #4588.browser_use_sdkimports.skills.list(...)(waslist_skills) andskills.execute(skill_id, ...)(wasexecute_skill).SkillResponse.id(UUID) tostrfor comparisons and serialization.status.value == "finished"to handle the new Enum.Written for commit 0bed616. Summary will update on new commits.