Change lerna release config to allow version update in release branch…

…es (#3878)

* fix: config lerna to allow release versioning in release branches

* fix: commit changelog in a separate commit for clarity

* fix: typo

* fix: typo 2

lerna.json

@@ -3,5 +3,13 @@
     "docs",
     "packages/*"
   ],
-  "version": "54.2.0"
+  "version": "54.2.0",
+  "command": {
+    "version": {
+      "allowBranch": [
+        "develop",
+        "release/*"
+      ]
+    }
+  }
 }

scripts/create-release-branch.js

@@ -78,14 +78,17 @@ const groupedMessages = changeLogGeneratorUtils.getMessagesGroupedByPackage(pars
 const changeLog = changeLogGeneratorUtils.getChangeLogText(releaseBranchName, groupedMessages);
 changeLogGeneratorUtils.writeChangeLog(changeLog);
 
+const commitCommand = `git commit -a -m "chore: generated CHANGELOG for ${releaseBranchName}"`;
+shell.exec(commitCommand);
+
 // git clean but keeping node_modules around
 shell.exec('git clean -xfd -e node_modules');
 
 // lerna version
 // increment the version number in all packages without publishing to npmjs
 // only run on branch named develop and do not create git tags
 shell.exec(
-  `lerna version ${nextVersion} --force-publish --allow-branch develop --no-git-tag-version --exact --yes`
+  `lerna version ${nextVersion} --force-publish --no-git-tag-version --exact --yes`
 );
 
 // Using --no-git-tag-version prevents creating git tags but also prevents commiting