[infra] Add automated release PR creation script

package.json

@@ -59,6 +59,7 @@
     "release:publish": "pnpm publish --recursive --tag latest",
     "release:publish:dry-run": "pnpm publish --recursive --tag latest --registry=\"http://localhost:4873/\"",
     "release:tag": "node scripts/releaseTag.mjs",
+    "release:prepare": "node scripts/createReleasePR.mjs",
     "validate": "concurrently \"pnpm prettier && pnpm eslint\" \"pnpm proptypes\" \"pnpm docs:typescript:formatted\" \"pnpm docs:api\"",
     "clean:node_modules": "rimraf --glob \"**/node_modules\"",
     "clean": "pnpm -r exec rm -rf build tsconfig.build.tsbuildinfo"
@@ -67,6 +68,8 @@
     "@actions/core": "^1.11.1",
     "@actions/github": "^6.0.1",
     "@argos-ci/core": "^3.2.0",
+    "execa": "^9.6.0",
+    "inquirer": "^9.2.15",
     "@babel/cli": "^7.27.2",
     "@babel/core": "catalog:",
     "@babel/plugin-transform-class-properties": "^7.27.1",

scripts/README.md

@@ -14,6 +14,23 @@
 
 ### Prepare the release of the packages
 
+> [!INFO]
+> You can now use the new automated release preparation script by running `pnpm release:prepare`. This script automates steps 1-5 below by:
+>
+> - Asking for the major version to update (v7.x, v6.x, etc.)
+> - Determining the new version based on the selected major version:
+>   - For non-latest major versions: patch/minor/custom
+>   - For latest major version: patch/minor/major/custom and prerelease options:
+>     - Start alpha prerelease (if no prerelease exists)
+>     - Increase alpha version or start beta (if alpha exists)
+>     - Increase beta version or go to major (if beta exists)
+> - Creating a new branch from upstream/master (for latest major) or upstream/vX.x (for older versions)
+> - Updating the root package.json and all product package versions
+> - Generating and formatting the changelog
+> - Creating a PR with all changes and a complete checklist
+>
+> This script is fully interactive and will guide you through the release process.
+
 The following steps must be proposed as a pull request.
 
 1. Compare the last tag with the branch upon which you want to release (`next` for the alpha / beta releases and `master` for the current stable version).