From b9c579b03c1833aa63660af76a4bbca26f2d504e Mon Sep 17 00:00:00 2001
From: CarlaCostea <56835388+CarlaCostea@users.noreply.github.com>
Date: Tue, 28 Apr 2026 11:22:43 +0300
Subject: [PATCH] =?UTF-8?q?Revert=20"chore(release):=20add=20--major=20fla?=
 =?UTF-8?q?g=20to=20scripts/release,=20enable=20on=20master=E2=80=A6"?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 .github/workflows/ci.yml | 17 +----------------
 scripts/release          | 13 +++----------
 2 files changed, 4 insertions(+), 26 deletions(-)

diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index 1adbd6c43e..07666893ac 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -75,19 +75,4 @@ jobs:
           cache: yarn
       - run: yarn install
       - run: scripts/release --build
-      # ─────────────────────────────────────────────────────────────────────
-      # TEMPORARY: --major forces every publishable package to a new major
-      # version on the next publish. This is in place ONLY for the platform
-      # upgrade release (React 18, MUI v7, Node 24, test stack modernization).
-      #
-      # REVERT THIS IMMEDIATELY AFTER THE PLATFORM RELEASE PUBLISHES.
-      #
-      # How to revert: open a follow-up PR to master that removes the
-      # --major flag from the line below, restoring:
-      #   - run: scripts/release --release --loglevel verbose
-      #
-      # Leaving --major in place will bump every package to the next major
-      # on EVERY subsequent merge to master, which is almost certainly not
-      # what you want.
-      # ─────────────────────────────────────────────────────────────────────
-      - run: scripts/release --release --major --loglevel verbose
+      - run: scripts/release --release --loglevel verbose
diff --git a/scripts/release b/scripts/release
index 32235f0654..4eccef2453 100755
--- a/scripts/release
+++ b/scripts/release
@@ -27,9 +27,9 @@ const CWD = process.cwd();
  *   - `next`: Defaults to `false`.
  */
 const argv = minimist(process.argv.slice(2), {
-  boolean: ['dry-run', 'next', 'build', 'test', 'release', 'major'],
+  boolean: ['dry-run', 'next', 'build', 'test', 'release'],
   string: ['loglevel'],
-  default: { 'dry-run': false, next: false, build: false, test: false, release: false, major: false },
+  default: { 'dry-run': false, next: false, build: false, test: false, release: false },
 });
 
 /**
@@ -209,14 +209,7 @@ const test = () => {
  */
 const release = () => {
   log(chalk.magenta('--- STEP 5: VERSION PACKAGES ---'));
-  // --major forces a major bump on every publishable package, bypassing
-  // conventional-commits inference. Use this for coordinated platform
-  // upgrades (peerDep changes for React, MUI, etc.) where every package
-  // must move to a new major in lockstep.
-  const versionCmd = argv.major
-    ? 'npx lerna version major --force-publish=* --yes'
-    : 'npx lerna version --conventional-commits --yes';
-  runCmd(versionCmd);
+  runCmd('npx lerna version --conventional-commits --yes');
 
   log(chalk.magenta('--- STEP 6: PUBLISH PACKAGES ---'));
   let releaseCmd = 'npx lerna publish from-git --yes';