Skip to content

chore(cli): prepare browse 0.9.7 from v3 - #2705

Open
shrey150 wants to merge 2 commits into
agent/fix-functions-parity-v3from
agent/release-browse-0.9.7-v3
Open

chore(cli): prepare browse 0.9.7 from v3#2705
shrey150 wants to merge 2 commits into
agent/fix-functions-parity-v3from
agent/release-browse-0.9.7-v3

Conversation

@shrey150

@shrey150 shrey150 commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

Summary

  • version Browse from 0.9.6 to 0.9.7 and consume the Functions parity changeset
  • add a v3-cli-only trusted-publishing job for Browse
  • keep the existing monorepo release job restricted to main
  • lint, test, pack, inspect, install-smoke, publish with npm provenance, and tag the exact Browse artifact

This is stacked on #2704 and supersedes #2703, whose v4-spike-cli base contains unrelated CLI migration work.

Why this release path

v3-cli starts at the last pre-v4 main commit, and its packages/cli tree is identical to the published browse@0.9.6 tag. This lets 0.9.7 contain the tactical Functions fix without also shipping unreleased v4-branch CLI changes.

The workflow publishes only packages/cli; it does not run the monorepo-wide Changesets publish path. npm authentication remains the repository's existing OIDC/trusted-publishing flow with provenance.

E2E Test Matrix

Command / flow Observed output Confidence / sufficiency
actionlint .github/workflows/release.yml Passed with no findings Validates workflow syntax and expressions
pnpm --filter browse lint Formatting, ESLint, and TypeScript checks passed for browse@0.9.7 Proves the exact release tree is statically valid
pnpm --filter browse test under the CI-standard umask 25 files and 369/369 tests passed Proves the exact versioned release tree is green
pnpm --dir packages/cli pack --pack-destination <temp> Produced browse-0.9.7.tgz with 142 entries Exercises the exact v3-compatible pack command used by CI
Inspect packed package/package.json Name/version are browse@0.9.7; workspace dependency resolves to @browserbasehq/stagehand@3.7.1 Proves no v4 Stagehand dependency leaks into the artifact
Install tarball into a clean temp prefix browse/0.9.7; browse functions --help exposes functions publish Proves the packed artifact installs and its CLI entry point runs
npm view browse@0.9.7 Version is not published Confirms merging this PR will create, not overwrite, the release

Merge and publish order

  1. Merge fix(cli): align Functions with SDK on v3 CLI #2704 into v3-cli.
  2. Retarget this PR from agent/fix-functions-parity-v3 to v3-cli.
  3. Merge this PR. The push to v3-cli triggers the Browse-only job and publishes browse@0.9.7.

@changeset-bot

changeset-bot Bot commented Aug 13, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 7365a20

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@shrey150
shrey150 marked this pull request as ready for review August 13, 2026 15:57
@shrey150
shrey150 force-pushed the agent/release-browse-0.9.7-v3 branch from f2fff94 to d77518d Compare August 13, 2026 16:07

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review completed against the latest diff

Reply with feedback, questions, or to request a fix.

Re-trigger cubic

Comment thread .github/workflows/release.yml
Comment thread .github/workflows/release.yml
Comment thread .github/workflows/release.yml
@shrey150
shrey150 force-pushed the agent/release-browse-0.9.7-v3 branch from 501cba1 to 7365a20 Compare August 13, 2026 16:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant