chore: add sampo changeset for before_send module-level setup fix (#472) (#489)

Author: marandaneto

.sampo/changesets/before-send-module-setup.md

@@ -0,0 +1,5 @@
+---
+pypi/posthog: patch
+---
+
+fix: pass the module-level `posthog.before_send` callback into the lazily initialized default client

CODEOWNERS

@@ -1 +1 @@
-@PostHog/team-feature-flags
+@PostHog/team-client-libraries

README.md

@@ -69,14 +69,3 @@ posthoganalytics = { path = "../posthog-python-local" }
 ```
 
 This'll let you build and test SDK changes fully locally, incorporating them into your local posthog app stack. It mainly takes care of the `posthog -> posthoganalytics` module renaming. You'll need to re-run `make prep_local` each time you make a change, and re-run `uv sync --active` in the posthog app project.
-
-## Releasing
-
-This repository uses [Sampo](https://github.com/bruits/sampo) for versioning, changelogs, and publishing to crates.io.
-
-1. When making changes, include a changeset: `sampo add`
-2. Create a PR with your changes and the changeset file
-3. Add the `release` label and merge to `main`
-4. Approve the release in Slack when prompted — this triggers version bump, crates.io publish, git tag, and GitHub Release
-
-You can also trigger a release manually via the workflow's `workflow_dispatch` trigger (still requires pending changesets).

RELEASING.md

@@ -0,0 +1,10 @@
+# Releasing
+
+This repository uses [Sampo](https://github.com/bruits/sampo) for versioning, changelogs, and publishing to crates.io.
+
+1. When making changes, include a changeset: `sampo add`
+2. Create a PR with your changes and the changeset file
+3. Add the `release` label and merge to `main`
+4. Approve the release in Slack when prompted — this triggers version bump, crates.io publish, git tag, and GitHub Release
+
+You can also trigger a release manually via the workflow's `workflow_dispatch` trigger (still requires pending changesets).