Skip to content

Conversation

@tkattkat
Copy link
Collaborator

why

bump version to 3.0.5

what changed

our package.json is out of sync with latest release version

test plan

@changeset-bot
Copy link

changeset-bot bot commented Nov 25, 2025

⚠️ No Changeset found

Latest commit: c4a5a2d

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

@tkattkat tkattkat merged commit c3e522c into main Nov 25, 2025
6 of 8 checks passed
@greptile-apps
Copy link
Contributor

greptile-apps bot commented Nov 25, 2025

Greptile Overview

Greptile Summary

Bumps version from 3.0.4 to 3.0.5 in preparation for next release containing Fara 7B support.

  • Manual version bump bypasses changeset automation workflow
  • CHANGELOG.md not updated (should include Fara 7B entry)
  • Pending changeset file .changeset/free-dancers-rescue.md not removed
  • packages/evals/package.json not updated (typically bumped alongside core)

Recommendation: Use pnpm changeset version instead of manual edit to properly update all version-related files and maintain consistency with the established changesets workflow used in previous releases (e.g., PR #1276).

Confidence Score: 2/5

  • This PR has significant process issues that could cause release inconsistencies
  • Manual version bump bypasses established changeset workflow, leaving CHANGELOG.md outdated and changeset files unremoved, which will cause issues when the proper Version Packages automation runs
  • Review .changeset/free-dancers-rescue.md and packages/core/CHANGELOG.md - these should be updated as part of version bump process

Important Files Changed

File Analysis

Filename Score Overview
packages/core/package.json 2/5 Manual version bump from 3.0.4 to 3.0.5, bypassing changeset workflow which should auto-update CHANGELOG and remove pending changesets

Sequence Diagram

sequenceDiagram
    participant Dev as Developer
    participant PR as This PR
    participant CS as Changesets
    participant NPM as NPM Registry
    
    Note over Dev,CS: Current Approach (Manual)
    Dev->>PR: Manually edit package.json to 3.0.5
    PR->>NPM: Merge & publish
    Note over CS: ❌ CHANGELOG.md not updated
    Note over CS: ❌ .changeset/free-dancers-rescue.md still exists
    Note over CS: ❌ evals package.json not bumped
    
    Note over Dev,CS: Recommended Approach (Changesets)
    Dev->>CS: Run `pnpm changeset version`
    CS->>PR: Update package.json to 3.0.5
    CS->>PR: Update CHANGELOG.md with Fara 7B entry
    CS->>PR: Remove .changeset/free-dancers-rescue.md
    CS->>PR: Bump evals package.json to 1.1.5
    PR->>NPM: Merge & publish
    Note over NPM: ✅ All files consistent
Loading

Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

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

1 file reviewed, 1 comment

Edit Code Review Agent Settings | Greptile

{
"name": "@browserbasehq/stagehand",
"version": "3.0.4",
"version": "3.0.5",
Copy link
Contributor

Choose a reason for hiding this comment

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

logic: manual version bump bypasses changeset workflow - should run pnpm changeset version to also update CHANGELOG.md and remove .changeset/free-dancers-rescue.md

Prompt To Fix With AI
This is a comment left during a code review.
Path: packages/core/package.json
Line: 3:3

Comment:
**logic:** manual version bump bypasses changeset workflow - should run `pnpm changeset version` to also update CHANGELOG.md and remove `.changeset/free-dancers-rescue.md`

How can I resolve this? If you propose a fix, please make it concise.

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.

3 participants