feat: Release and version strategy (#358)

Author: charlesvien

.github/workflows/release.yml

@@ -52,24 +52,50 @@ jobs:
           node-version: 22
           cache: "pnpm"
 
-      - name: Bump minor version
+      - name: Compute version from git tags
         id: version
         run: |
-          CURRENT_VERSION=$(jq -r .version apps/array/package.json)
-          MAJOR=$(echo "$CURRENT_VERSION" | cut -d. -f1)
-          MINOR=$(echo "$CURRENT_VERSION" | cut -d. -f2)
-          NEW_VERSION="${MAJOR}.$((MINOR + 1)).0"
-          echo "Bumping version from $CURRENT_VERSION to $NEW_VERSION"
+          # Find the latest minor version tag (vX.Y format - exactly 2 parts)
+          # These are manually created to mark new minor releases
+          # Release tags (vX.Y.Z) are ignored for base version calculation
+          LATEST_TAG=$(git tag --list 'v[0-9]*.[0-9]*' --sort=-v:refname | grep -E '^v[0-9]+\.[0-9]+$' | head -1)
+
+          # Fall back to vX.Y.0 format if no vX.Y tags exist (backward compat)
+          if [ -z "$LATEST_TAG" ]; then
+            LATEST_TAG=$(git tag --list 'v[0-9]*.[0-9]*.0' --sort=-v:refname | head -1)
+          fi
+
+          if [ -z "$LATEST_TAG" ]; then
+            echo "No version tag found. Create one with: git tag v0.15 && git push origin v0.15"
+            exit 1
+          fi
+
+          # Extract major.minor from tag
+          VERSION_PART=${LATEST_TAG#v}
+          MAJOR=$(echo "$VERSION_PART" | cut -d. -f1)
+          MINOR=$(echo "$VERSION_PART" | cut -d. -f2)
+
+          # Count commits since the base tag
+          PATCH=$(git rev-list "$LATEST_TAG"..HEAD --count)
 
-          jq --arg v "$NEW_VERSION" '.version = $v' apps/array/package.json > tmp.json && mv tmp.json apps/array/package.json
+          if [ "$PATCH" -eq 0 ]; then
+            echo "No commits since $LATEST_TAG. Nothing to release."
+            exit 1
+          fi
 
-          git config user.name "posthog-bot"
-          git config user.email "[email protected]"
-          git add apps/array/package.json
-          git commit -m "chore: bump version to $NEW_VERSION [skip ci]"
-          git push
+          NEW_VERSION="${MAJOR}.${MINOR}.${PATCH}"
+          echo "Version: $NEW_VERSION (from base tag $LATEST_TAG + $PATCH commits)"
 
           echo "version=$NEW_VERSION" >> "$GITHUB_OUTPUT"
+          echo "base_tag=$LATEST_TAG" >> "$GITHUB_OUTPUT"
+
+      - name: Set version in package.json
+        env:
+          APP_VERSION: ${{ steps.version.outputs.version }}
+        run: |
+          # Update package.json for the build (not committed)
+          jq --arg v "$APP_VERSION" '.version = $v' apps/array/package.json > tmp.json && mv tmp.json apps/array/package.json
+          echo "Set apps/array/package.json version to $APP_VERSION"
 
       - name: Install dependencies
         run: pnpm install --frozen-lockfile

UPDATES.md

@@ -0,0 +1,66 @@
+# Releasing Updates
+
+Array uses semantic versioning with git tags. Patch versions are automatically computed from commit counts.
+
+The version in `apps/array/package.json` is set to `0.0.0-dev` - this is intentional. CI injects the real version at build time from git tags.
+
+## Version Format: `major.minor.patch`
+
+- **major.minor**: Controlled by git tags (e.g., `v0.15`, `v1.0`)
+- **patch**: Auto-calculated as number of commits since the minor tag
+
+## How It Works
+
+1. A base tag like `v0.15` marks the start of a minor version
+2. Each push to `main` triggers a release with version `0.15.N` where N = commits since `v0.15`
+3. No manual `package.json` updates needed for patch releases
+
+## Releasing a Patch (Automatic)
+
+Just push to `main`. The workflow computes the version automatically:
+
+```
+v0.15 tag exists
+Push commit #1 → releases 0.15.1
+Push commit #2 → releases 0.15.2
+Push commit #3 → releases 0.15.3
+```
+
+## Releasing a Minor Version
+
+Create a new base tag when you want to bump the minor version:
+
+```bash
+git tag v0.16
+git push origin v0.16
+```
+
+The next push to `main` will release `0.16.1`.
+
+## Releasing a Major Version
+
+Same process, just increment the major:
+
+```bash
+git tag v1.0
+git push origin v1.0
+```
+
+## Checking Current Version
+
+See what version would be released:
+
+```bash
+# Find the current base tag
+git tag --list 'v[0-9]*.[0-9]*' --sort=-v:refname | grep -E '^v[0-9]+\.[0-9]+$' | head -1
+
+# Count commits since base tag (this is the patch number)
+git rev-list v0.15..HEAD --count
+```
+
+## Tag Naming Convention
+
+- **Base tags** (manual): `vX.Y` - e.g., `v0.15`, `v1.0`
+- **Release tags** (auto): `vX.Y.Z` - e.g., `v0.15.3`, created by CI
+
+Only base tags (`vX.Y`) are used for version calculation. Release tags (`vX.Y.Z`) are created for GitHub releases but ignored when computing the next version.

apps/array/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@posthog/array",
-  "version": "0.16.0",
+  "version": "0.0.0-dev",
   "description": "Array - PostHog desktop task manager",
   "main": ".vite/build/index.js",
   "versionHash": "dynamic",