From 5181c56959387572bba133d6caf7348f52290ae4 Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Tue, 13 Jan 2026 10:30:57 +0000
Subject: [PATCH] fix: remove incorrect push to master in beta
 update-version.js

The update-version.js script was pushing to 'origin master' instead of
the current release branch. This caused the PR creation to fail because
there were no commits between master and the release branch (since the
commit was pushed to master, not the release branch).

The push is now removed from update-version.js because gh pr create
will handle pushing the release branch when creating the PR.

Co-authored-by: louislam <1336778+louislam@users.noreply.github.com>
---
 extra/beta/update-version.js | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/extra/beta/update-version.js b/extra/beta/update-version.js
index 240d44608..5465763df 100644
--- a/extra/beta/update-version.js
+++ b/extra/beta/update-version.js
@@ -58,8 +58,8 @@ function commit(version) {
         throw new Error("commit error");
     }
 
-    res = childProcess.spawnSync("git", ["push", "origin", "master"]);
-    console.log(res.stdout.toString().trim());
+    // Note: Push is handled by gh pr create in the release script
+    // No need to push here as we're on a release branch, not master
 }
 
 /**