You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
private-key: ${{ secrets.GH_APP_POSTHOG_PHP_RELEASER_PRIVATE_KEY }} # Secrets available only inside the 'Release' environment, requires approval from a maintainer
Copy file name to clipboardExpand all lines: README.md
+1-23Lines changed: 1 addition & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,26 +33,4 @@ Specifically, the [PHP integration](https://posthog.com/docs/integrations/php-in
33
33
34
34
## Releasing
35
35
36
-
Releases are semi-automated via GitHub Actions. When a PR with the `release` and a version bump label is merged to `master`, the release workflow is triggered.
37
-
38
-
You'll need an approval from a PostHog engineer. If you're an employee, you can see the request in the [#approvals-client-libraries](https://app.slack.com/client/TSS5W8YQZ/C0A3UEVDDNF) channel.
39
-
40
-
### Release Process
41
-
42
-
1.**Create your PR** with the changes you want to release
43
-
2.**Add the `release` label** to the PR
44
-
3.**Add a version bump label** that should be either `bump-patch`, `bump-minor` or `bump-major`
45
-
4.**Merge the PR** to `master`
46
-
47
-
Once merged, the following happens automatically:
48
-
49
-
1. A Slack notification is sent to the client libraries channel requesting approval
50
-
2. A maintainer approves the release in the GitHub `Release` environment
51
-
3. The version is bumped in `lib/PostHog.php` and `composer.json` based on the version label (`patch`, `minor`, or `major`, extracted from the label)
52
-
4. The `CHANGELOG.md` is updated with a link to the full changelog
53
-
5. Changes are committed and pushed to `master`
54
-
6. A git tag is created (e.g., `v1.8.0`)
55
-
7. A GitHub release is created with the changelog content
Releases are semi-automated via GitHub Actions. When a PR with the `release` and a version bump label is merged to `master`, the release workflow is triggered.
4
+
5
+
You'll need an approval from a PostHog engineer. If you're an employee, you can see the request in the [#approvals-client-libraries](https://app.slack.com/client/TSS5W8YQZ/C0A3UEVDDNF) channel.
6
+
7
+
## Release Process
8
+
9
+
1.**Create your PR** with the changes you want to release
10
+
2.**Add the `release` label** to the PR
11
+
3.**Add a version bump label** that should be either `bump-patch`, `bump-minor` or `bump-major`
12
+
4.**Merge the PR** to `master`
13
+
14
+
Once merged, the following happens automatically:
15
+
16
+
1. A Slack notification is sent to the client libraries channel requesting approval
17
+
2. A maintainer approves the release in the GitHub `Release` environment
18
+
3. The version is bumped in `lib/PostHog.php` and `composer.json` based on the version label (`patch`, `minor`, or `major`, extracted from the label)
19
+
4. The `CHANGELOG.md` is updated with a link to the full changelog
20
+
5. Changes are committed and pushed to `master`
21
+
6. A git tag is created (e.g., `v1.8.0`)
22
+
7. A GitHub release is created with the changelog content
0 commit comments