docs(changelog): update changelog & fix release - #2678
Merged
Conversation
Match the 3.0.0 entry's pattern: the major-bump entries now carry the one-line summary from the cutover PR (#2671) and link to the docs migration guide.
|
The consolidated root changelog seeded on v4-spike jumped from 4.0.0 straight to 3.0.0, dropping 16 releases of 3.x history. Splice the entries back in from packages/core/CHANGELOG.md on the v3 branch.
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
1 issue found across 1 file (changes from recent commits).
Confidence score: 5/5
- In
CHANGELOG.md, the 3.1.0 caching note’s passive phrasing can obscure who enables caching by default and who can opt out, which may cause mild reader confusion in public release communication—rewrite it in active voice naming Stagehand and users explicitly.
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="CHANGELOG.md">
<violation number="1" location="CHANGELOG.md:289">
P3: The 3.1.0 caching note uses passive voice for default and opt-out behavior. Name Stagehand and users as actors.
(Based on your team's feedback about active voice in public documentation.)</violation>
</file>
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
|
|
||
| When running `env: "BROWSERBASE"`, Stagehand automatically caches `act()`, `extract()`, and `observe()` results server-side — repeated calls with the same inputs return instantly without consuming LLM tokens. | ||
|
|
||
| Caching is enabled by default and can be disabled via `serverCache: false` on the Stagehand instance or per individual call. Check out the [browserbase blog](https://www.browserbase.com/blog/stagehand-caching) for more details. |
Contributor
There was a problem hiding this comment.
P3: The 3.1.0 caching note uses passive voice for default and opt-out behavior. Name Stagehand and users as actors.
(Based on your team's feedback about active voice in public documentation.)
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At CHANGELOG.md, line 289:
<comment>The 3.1.0 caching note uses passive voice for default and opt-out behavior. Name Stagehand and users as actors.
(Based on your team's feedback about active voice in public documentation.) </comment>
<file context>
@@ -19,6 +19,513 @@ describe the TypeScript SDK.
+
+ When running `env: "BROWSERBASE"`, Stagehand automatically caches `act()`, `extract()`, and `observe()` results server-side — repeated calls with the same inputs return instantly without consuming LLM tokens.
+
+ Caching is enabled by default and can be disabled via `serverCache: false` on the Stagehand instance or per individual call. Check out the [browserbase blog](https://www.browserbase.com/blog/stagehand-caching) for more details.
+
+- [#1642](https://github.com/browserbase/stagehand/pull/1642) [`3673369`](https://github.com/browserbase/stagehand/commit/36733691f90c15386cf2a7b47d04ef429b7195ae) Thanks [@seanmcguire12](https://github.com/seanmcguire12)! - fix issue where scripts added via context.addInitScripts() were not being injected into new pages that were opened via popups (eg, clicking a link that opens a new page) and/or calling context.newPage(url)
</file context>
Suggested change
| Caching is enabled by default and can be disabled via `serverCache: false` on the Stagehand instance or per individual call. Check out the [browserbase blog](https://www.browserbase.com/blog/stagehand-caching) for more details. | |
| Stagehand enables caching by default; users can disable it with `serverCache: false` on the Stagehand instance or per individual call. Check out the [browserbase blog](https://www.browserbase.com/blog/stagehand-caching) for more details. |
devEngines.packageManager with onFail: 'download' makes every npm command in the repo hard-fail (npm cannot download itself into being pnpm). changeset publish shells out to 'npm info' to check published versions before publishing (the publish itself uses pnpm), so the Release workflow died on EBADDEVENGINES. onFail: 'warn' keeps the pnpm nudge for contributors without blocking npm-based tooling.
miguelg719
changed the title
seanmcguire12
changed the title
seanmcguire12
approved these changes
Aug 10, 2026
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.
Three fixes, all wanted before the 4.0.0 release run (merging this PR to main is itself the release trigger):
packages/core/CHANGELOG.mdon thev3branch (that history's maintenance home going forward).EBADDEVENGINES:devEngines.packageManagerwithonFail: "download"makes every npm command in the repo hard-fail (npm can't download itself into being pnpm), andchangeset publishpreflights withnpm info(the publish itself usespnpm publish, socatalog:deps resolve fine — verified in @changesets/cli 2.31'sgetPublishTool).onFail: "warn"keeps the pnpm nudge without blocking npm tooling; verifiednpm infonow succeeds in-repo.consolidate-changelogs.ts --checkpasses.