test automated pre-release

.changeset/ten-snakes-teach.md

@@ -0,0 +1,6 @@
+---
+"@appwrite.io/pink-icons": patch
+"@appwrite.io/pink": patch
+---
+
+patch

.github/workflows/release.yml

@@ -1,9 +1,6 @@
 name: Release
 
-on:
-  push:
-    branches:
-      - main
+on: push
 
 concurrency: ${{ github.workflow }}-${{ github.ref }}
 

VERSIONING.md

@@ -0,0 +1,23 @@
+# Versioning
+
+Versioning consists in 3 steps. Specifying a bump (which can be `patch`, `minor` or `major`), updating package versions, and releasing.
+
+## Bumping
+
+To specify a new bump in the package versions, you can use the `bump-x` script, where `x` is the bump type.
+
+This will automatically generate a [changeset](https://github.com/changesets/changesets). A changeset is a file that contains the bump intent, and a list of all commits that will be included in the release.
+
+## Updating package versions
+
+To apply the bump intents, and change the package versions accordingly, you can use the `version` script. This will automatically update all the `CHANGELOG.md` files, and the `package.json` files.
+
+## Releasing
+
+If everything looks good, you can release the new version using the `release` script. This will automatically create a new git tag, and publish the packages to npm. Don't forget to commit!
+
+## Pre-releasing
+
+Sometimes, you will want to release a pre-release version. Firstly, be sure to be in a branch that is not `main`. Then, you can use the `pre` script, which will enter the current branch into pre-release mode. While in pre-release mode, all other actions are the same, but the version will be suffixed with `-next.X`.
+
+Before merging this pre-release branch into `main`, be sure to exit the pre-release mode using the `pre` script again.

package.json

@@ -14,6 +14,12 @@
     "test": "turbo run test",
     "format": "turbo run format",
     "clean": "turbo run clean && rm -rf node_modules",
+    "pre": "",
+    "bump": "changeset",
+    "bump-patch": "",
+    "bump-minor": "",
+    "bump-major": "",
+    "version": "changeset version",
     "release": "npm run build && changeset publish"
   },
   "devDependencies": {