Skip to content

Conversation

@vdekrijger
Copy link
Contributor

Adds support for the Releaser (posthog-php) integration as documented over here: https://posthog.com/handbook/engineering/sdks/releases.

@vdekrijger vdekrijger requested a review from a team January 8, 2026 16:34
permissions:
contents: write
actions: write
id-token: write
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, you don't need id-token for PHP. Might need to mention on the documentation that this is only needed when using OIDC deployment - which I don't think makes sense for PHP

run: |
current_version="${{ steps.bump-version.outputs.current_version }}"
new_version="${{ steps.bump-version.outputs.new_version }}"
echo -e "## $new_version\n\n* [Full Changelog](https://github.com/PostHog/posthog-php/compare/v${current_version}...v${new_version})\n\n$(cat CHANGELOG.md)" > CHANGELOG.md
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks like it is currently called History.md

do we need to add a CHANGELOG.md with the History.md contents
point a link to CHANGELOG.md in the History.md

??

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

also nit that it'd be good to have the day's date there for the future traveller

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good idea! Added it to the generation flow and will backport it to the posthog-go SDK as well 🙌

Copy link
Member

@pauldambra pauldambra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i've been removed from these changes but this is easy to change if needed so 🚢 🚢 🚢 🚢 🚢

(NB i think there needs to be some CHANGELOG creation)

Copy link
Member

@rafaeelaudibert rafaeelaudibert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's interesting how this is just pushing a tag rather than publishing somewhere, but lgtm! Left a minor nit but don't have to fix it here

README.md Outdated

1. **Create your PR** with the changes you want to release
2. **Add the `release` label** to the PR
3. **Add a version bump label** that should be either `patch`, `minor` or `major`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is wrong, your action is expecting bump-patch, bump-minor or bump-major. Can you make them match?

@vdekrijger
Copy link
Contributor Author

Addressed both of your comments!

I copied this file from the posthog-go repository, but looks like I missed a few things when fixing the releaser logic!

Should now be fixed!

  • Renamed History.md to CHANGELOG.md (no longer referenced in the code due to the removal of the legacy release flow)
  • Removed the legacy release flow (might as well if we don't need it anymore)
  • Updated the readme to explicitely call out the labels (bump-*), will fix this in the posthog-go repo afterwards as well!
  • Removed id-token: write

Copy link
Member

@rafaeelaudibert rafaeelaudibert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Check the SDK Doctor code on posthog/posthog to make sure we didn't depend on History.md. IIRC we're using releases so it should be fine, but double-check it please!

@vdekrijger
Copy link
Contributor Author

Ah good shout! TIL that there is a connection between the 2!

Here we go! PostHog/posthog#44560

@vdekrijger vdekrijger merged commit 2ec3ecc into master Jan 9, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants