chore: auto publish alpha versions

.github/workflows/label-alpha-bump.yml

@@ -0,0 +1,47 @@
+name: Autobump
+
+on:
+  check_suite:
+    types:
+      completed
+
+jobs:
+    label-alpha-bump:
+        name: Bump version based on PR label
+        runs-on: ubuntu-20.04
+        if: |
+            github.event.check_suite.conclusion == 'success'
+            && contains(github.event.pull_request.labels.*.name, 'bump alpha')
+        steps:
+            - name: Check out repository
+              uses: actions/checkout@v4
+              with:
+                  ref: ${{ github.event.pull_request.base.ref }}
+                  token: ${{ secrets.POSTHOG_BOT_GITHUB_TOKEN }}
+                  fetch-depth: 0
+
+            - uses: pnpm/action-setup@v4
+              with:
+                version: 8.x.x
+
+            - name: Determine new version
+              id: versions
+              if: steps.bump-type.outputs.bump-type != 'null'
+              run: |
+                  OLD_VERSION=$(jq ".version" package.json -r)
+                  NEW_VERSION=$(npx semver $OLD_VERSION -i pre-release --preid alpha)
+                  echo "old-version=$OLD_VERSION" >> "$GITHUB_OUTPUT"
+                  echo "new-version=$NEW_VERSION" >> "$GITHUB_OUTPUT"
+
+            - name: Update version in package.json
+              if: steps.bump-type.outputs.bump-type != 'null'
+              run: |
+                  mv package.json package.old.json
+                  jq --indent 4 '.version = "${{ steps.versions.outputs.new-version }}"' package.old.json > package.json
+                  rm package.old.json
+
+            - name: Publish the alpha in the npm registry
+              run: npm publish --access public --dry-run
+              env:
+                  NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+

README.md

@@ -79,6 +79,10 @@ If you forget to add the label, don't try to update the version locally as you w
 
 To release an alpha or beta version, you'll need to use the CLI locally:
 
+#### CLI
+
+Only one person is set as a collaborator on NPM, so they're the only person that can manually publish alphas
+
 1. Make sure you're a collaborator on `posthog-js` in npm ([check here](https://www.npmjs.com/package/posthog-js)).
 2. Make sure you're logged into the npm CLI (`npm login`).
 3. Check out your work-in-progress branch (do not release an alpha/beta from `main`).
@@ -91,3 +95,8 @@ To release an alpha or beta version, you'll need to use the CLI locally:
     ```
 
 5. Enjoy the new prerelease version. You can now use it locally, in a dummy app, or in the [main repo](https://github.com/posthog/PostHog).
+
+#### Automagically
+
+Use the release-alpha label on your PR to have an alpha version bumped and published automatically.
+Remember that these are public and folk might use them, so make sure they're not _too_ alpha 🙈