chore(beta): create initial beta releases for stacks classic and stacks svelte

.changeset/open-hands-peel.md → .changeset/itchy-spies-cover.md

@@ -2,4 +2,4 @@
 "@stackoverflow/stacks": major
 ---
 
-Initial v3 beta release
+enter prerelease mode for project shine

.changeset/pre.json

@@ -1,8 +1,9 @@
 {
-  "mode": "pre",
-  "tag": "beta",
-  "initialVersions": {
-    "@stackoverflow/stacks": "2.8.6"
-  },
-  "changesets": ["open-hands-peel"]
+    "mode": "pre",
+    "tag": "beta",
+    "initialVersions": {
+        "@stackoverflow/stacks": "2.8.6",
+        "@stackoverflow/stacks-svelte": "0.5.0"
+    },
+    "changesets": []
 }

.changeset/silent-camels-shake.md

@@ -0,0 +1,5 @@
+---
+"@stackoverflow/stacks-svelte": major
+---
+
+enter prerelease mode for project shine

README.md

@@ -190,6 +190,22 @@ _Despite using changesets to communicate the intent of creating releases in a mo
 
 Successful releases trigger automatically a new deployment to stackoverflow.design by merging the `develop` branch into the `production` branch.
 
+## Beta publishing
+We use Changesets in prerelease mode to manage publishing to the beta branch. For more information, please refer to the official [Changesets prerelease documentation](https://github.com/changesets/changesets/blob/main/docs/prereleases.md).
+
+To prepare a beta release, follow these steps:
+
+1. Create a pull request (PR) targeting the beta branch.
+
+2. Ensure your PR includes a changeset.
+
+3. Merging the PR will trigger the `release` job. This job creates or updates a chore(new-beta-release) PR.
+
+4. To cut a new beta release, merge the `chore(new-release) (beta)` PR and wait for the `Release (latest or beta)` job to complete.
+
+Consumers can install the beta package by targeting the beta tag:
+`npm install @stackoverflow/stacks@beta` or `npm install @stackoverflow/stacks-svelte@beta`
+
 ## Bugs and feature requests
 Have a bug or feature request? First search existing or closed issues to make sure the issue hasn’t been noted yet. If not, review our [issue guidelines](/CONTRIBUTING.md#open-an-issue) for submitting [a bug report](/CONTRIBUTING.md#reporting-bugs) or [feature request](/CONTRIBUTING.md#feature-requests).