⚠️ No Changeset found

Latest commit: 180a1c8

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.

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

Greptile Summary

This PR consolidates server binary building and GitHub Release publishing into the main release.yml workflow, eliminating the dependency on a separate tag-triggered workflow. The change fixes an issue where tag pushes from CI weren't triggering the old stagehand-server-release.yml workflow.

Key Changes

• Moves server_build_binaries and server_publish_release jobs from the deleted stagehand-server-release.yml into release.yml
• Adds output variables (server_published, server_version, server_tag) to the release job
• Adds detection logic to identify if @browserbasehq/stagehand-server was published via Changesets
• Creates git tags and triggers build/publish jobs conditionally based on server publication
• Adds clarifying comments to Windows binary builds explaining SDK package selection
• Improves checksum creation to handle edge cases with empty binary lists

Architecture Improvement

The new flow is more robust: it creates tags automatically from the detected version (not relying on external tag pushes) and orchestrates the entire build→publish pipeline within a single workflow triggered by main branch pushes.

Confidence Score: 4/5

• This PR is safe to merge with high confidence - it correctly moves existing functionality into a more robust architecture without introducing new risks.
• The consolidation addresses a real workflow trigger problem (tag-based trigger failing). The detection logic properly checks if the server package was in the published list. The binary build steps are identically copied from the old workflow with added clarifying comments. Checksum creation was improved to handle edge cases. The job dependencies and conditionals (needs and if) are correctly structured to prevent unnecessary builds. One minor observation: the old workflow had explicit tag→package.json version verification in the release step, which the new workflow skips (though it's less critical since tags are created from package.json, not received externally). The approach trades explicit verification for implicit safety through tag creation rather than tag receiving.
• No files require special attention - changes are straightforward workflow consolidation with proper guardrails.

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant GH as GitHub Push (main)
    participant Release as release job
    participant Detect as Detect server publish
    participant Tag as Tag creation
    participant Build as server_build_binaries job
    participant Publish as server_publish_release job

    GH->>Release: Push to main triggers
    Release->>Release: Run changesets/action
    Release->>Detect: Extract version from package.json
    Detect->>Detect: Check if server in publishedPackages
    Detect-->>Release: Output server_version, server_tag, server_published
    Release->>Tag: If server_published == 'true'
    Tag->>Tag: Create and push git tag
    Release-->>Build: Pass outputs to dependent job
    Build->>Build: Run if server_published == 'true'
    Build->>Build: Build binaries for all platforms
    Build-->>Publish: Upload artifacts
    Publish->>Publish: Run if server_published == 'true'
    Publish->>Publish: Download artifacts
    Publish->>Publish: Create release with assets