Description

This PR improves the error handling when automatically opening the browser fails. Several users have reported issues with the create-release-branch tool failing when their terminal application lacks sufficient privileges for System Events or when using non-standard browsers like Brave.

Instead of failing with an unclear osascript error, the tool now:

• Attempts to open the browser gracefully
• Falls back to displaying clear manual instructions if automatic opening fails
• Continues running the server regardless of browser open status

Testing Instructions

Prerequisites

• macOS system
• Terminal application (Terminal.app, iTerm2, VS Code integrated terminal, etc.)

Test Case 1: System Events Permission Disabled

1. First, test current behavior on main:

   git checkout main
   yarn build
   // use package locally (eg: from Core repo)
   yarn && yarn create-release-branch -i

   • Note that it fails with osascript error if permissions are not granted

2. Disable System Events permission:

   • Open System Settings > Privacy & Security > Automation
   • Find your terminal application
   • Disable "System Events" permission

3. Test the fix:

   git checkout fix/handle-macos-browser-open-permissions
   yarn build
   // use package locally (eg: from Core repo)
   yarn && yarn create-release-branch -i

   • Verify you see a clear message with the URL to open manually
   • Verify the server continues running
   • Verify you can copy/paste the URL and access the UI

Test Case 2: Non-standard Browser (Brave)

1. Set Brave as your default browser

2. Test current behavior on main:

   git checkout main
   yarn build
   // use package locally (eg: from Core repo)
   yarn && yarn create-release-branch -i

   • Note any errors or unexpected behavior

3. Test the fix:

   git checkout fix/handle-macos-browser-open-permissions
   yarn build
   // use package locally (eg: from Core repo)
   yarn && yarn create-release-branch -i

   • Verify you see either:
     a) Browser opens successfully in Brave, or
     b) Clear instructions to open the URL manually
   • Verify the server continues running
   • Verify you can access the UI by manually opening the URL