From f2e880923f08a8c7818938e85558098ba7854908 Mon Sep 17 00:00:00 2001
From: yawbtng <154343001+yawbtng@users.noreply.github.com>
Date: Wed, 3 Jun 2026 20:06:11 -0700
Subject: [PATCH] chore: sync registry manifest versions to 3.0.0

server.json (2.2.0) and gemini-extension.json (2.4.1) had drifted from the
published package version (3.0.0 in package.json/CHANGELOG/tag). publish-mcp.yml
ships server.json verbatim to the MCP registry, so the registry advertised a
stale version. Bump both manifests to 3.0.0 to match.
---
 gemini-extension.json | 2 +-
 server.json           | 6 +++---
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/gemini-extension.json b/gemini-extension.json
index 5013e62..075dec6 100644
--- a/gemini-extension.json
+++ b/gemini-extension.json
@@ -1,6 +1,6 @@
 {
   "name": "mcp-server-browserbase",
-  "version": "2.4.1",
+  "version": "3.0.0",
   "mcpServers": {
     "mcp-server-browserbase": {
       "command": "npx",
diff --git a/server.json b/server.json
index a292e34..f0c2c5a 100644
--- a/server.json
+++ b/server.json
@@ -7,13 +7,13 @@
     "url": "https://github.com/browserbase/mcp-server-browserbase",
     "source": "github"
   },
-  "version": "2.2.0",
+  "version": "3.0.0",
   "packages": [
     {
       "registry_type": "npm",
       "registry_base_url": "https://registry.npmjs.org",
       "identifier": "@browserbasehq/mcp",
-      "version": "2.2.0",
+      "version": "3.0.0",
       "transport": {
         "type": "stdio"
       },
@@ -44,7 +44,7 @@
     {
       "registry_type": "oci",
       "identifier": "browserbasehq/mcp-server-browserbase",
-      "version": "2.2.0",
+      "version": "3.0.0",
       "runtime_hint": "docker",
       "environment_variables": [
         {