Skip to content

:hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error tracking, logs, and more – capture all the context agents need to diagnose problems, uncover opportunities, and ship fixes. Steer it all from Slack, web, desktop, or the MCP.

chore(ci): allow manual cli release runs (#130697)

Manoel Aranda Neto6c629ab32a15
diff --git a/.github/workflows/release-cli.yml b/.github/workflows/release-cli.yml
index 0d06bd0e2b31..c3984a79079b 100644
--- a/.github/workflows/release-cli.yml
+++ b/.github/workflows/release-cli.yml
@@ -5,6 +5,7 @@ on:
branches: [master]
paths:
- 'cli/.sampo/changesets/*.md'
+ workflow_dispatch:
permissions:
contents: read
@@ -24,7 +25,7 @@ concurrency:
jobs:
check-changesets:
name: Check for CLI changesets
- if: github.repository == 'PostHog/posthog'
+ if: github.repository == 'PostHog/posthog' && github.ref == 'refs/heads/master'
runs-on: ubuntu-24.04
timeout-minutes: 5
outputs:
diff --git a/cli/RELEASING.md b/cli/RELEASING.md
index ad7791fb25d4..982a77fb1531 100644
--- a/cli/RELEASING.md
+++ b/cli/RELEASING.md
@@ -93,6 +93,16 @@ A release that fails to upload therefore breaks npm installs for that version, w
The upload step shipped one release ahead of this setting for that reason.
If you need to cut a release by hand, merge a CLI changeset to `master` and let `Release CLI` run from there.
+If changesets are already pending, you can start a new run manually, for example after fixing a failed release preparation.
+Open [Release CLI in GitHub Actions](https://github.com/PostHog/posthog/actions/workflows/release-cli.yml), select **Run workflow**, choose `master`, and select **Run workflow** again.
+You can also use the GitHub CLI:
+
+```bash
+gh workflow run release-cli.yml --repo PostHog/posthog --ref master
+```
+
+Manual runs use the workflow on `master` and still require approval in the `Release SDK` environment.
+They do not bypass changesets or release checks, and runs on other branches are skipped.
Do not push `posthog-cli/vX.Y.Z` tags manually; cargo-dist tag-push releases are disabled.
If cargo-dist fails after `Release CLI` commits the release bump, rerun the failed jobs from the same workflow run.
Any failed job in `Release CLI` posts to the approval thread and to the [#alerts-posthog-js channel in Slack](https://posthog.slack.com/archives/C07HTMN9X47).