[STG-2560] docs: replace deprecated advancedStealth with verified#2348
Closed
bbclanker wants to merge 1 commit into
Closed
[STG-2560] docs: replace deprecated advancedStealth with verified#2348bbclanker wants to merge 1 commit into
bbclanker wants to merge 1 commit into
Conversation
|
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Docs pass to replace the deprecated
advancedStealthbrowser setting withverifiedacross the Stagehand docs. The old name is still accepted (Stagehand core keeps it as a backwards-compat alias, and the standalone MCP server documents--advancedStealthas a deprecated alias in its own CLI--help), but user-facing examples and tables should show the current canonical name.Reported by Alex on Slack, pointing at
v3/configuration/browser→ "Advanced Browserbase Configuration Example".Changes
v3 docs
packages/docs/v3/configuration/browser.mdx— code sample now usesverified: falseinstead ofadvancedStealth: falsepackages/docs/v3/integrations/mcp/setup.mdx— Optional query params table + Local CLI flags table swapped toverified/--verifiedpackages/docs/v3/integrations/mcp/configuration.mdx— CLI flags table swapped, "Advanced Stealth" tab retitled to "Verified" with a deprecated-alias note, security best-practices bullet updatedv2 docs — same fixes for the v2 mirror
Not touched
packages/docs/sdk-api-reference-labels.js— this is a snake_case rewriter driven by the live OpenAPI wire field;advancedStealthis still part of the API spec, so the mapping is intentional.stagehand-{java,go,python,ruby}andsdk-node— regenerated from OpenAPI, not human-authored docs.packages/core/lib/v3/v3.tsandpackages/core/lib/v3/types/public/api.ts— deliberately keepadvancedStealthas a backwards-compat alias (see the@deprecatedcomment onisAdvancedStealthinv3.ts).Test plan
Docs-only diff — no code paths touched. Verified with
git diffthat only the six intended MDX files change and every remainingadvancedStealthmention is either an intentional deprecated-alias note or unchanged code that reflects the API's continued support of both names.Requested by: alexander@browserbase.com
Linear: https://linear.app/browserbase/issue/STG-2560/docs-replace-deprecated-advancedstealth-with-verified-across-stagehand
Slack thread: https://browserbase.slack.com/archives/D0AHY8DEQPM/p1783960618071569
Note
Alex asked for a draft PR. The internal
createOrUpdatePRtool doesn't currently support thedraftflag — opening as a regular PR. Please mark it as draft in the GitHub UI if that's still desired.