{"id":"org_RVcfDRcn2piydCEP2lqfD","slug":"posthog","name":"PostHog","domain":"posthog.com","description":null,"category":null,"tags":[],"sourceCount":5,"releaseCount":661,"releasesLast30Days":245,"avgReleasesPerWeek":34.9,"lastFetchedAt":"2026-04-19T03:02:16.697Z","trackingSince":"2020-11-23T15:38:15.000Z","aliases":[],"accounts":[{"platform":"github","handle":"PostHog"}],"products":[],"sources":[{"id":"src_aFPJh8KG1_D_eibUSxbNu","slug":"posthog","name":"PostHog","type":"github","url":"https://github.com/PostHog/posthog","isPrimary":false,"isHidden":false,"fetchPriority":"normal","releaseCount":151,"latestVersion":"agent-skills-v0.49.0","latestDate":"2026-04-16T14:52:30.000Z","latestAddedAt":"2026-04-16T16:01:51.052Z","productSlug":null,"productName":null},{"id":"src_ayguL4KiCWWacyZ6A3waO","slug":"posthog-changelog","name":"PostHog Changelog","type":"agent","url":"https://posthog.com/changelog","isPrimary":false,"isHidden":false,"fetchPriority":"normal","releaseCount":10,"latestVersion":"March 2026 - Week IV","latestDate":"2026-03-22T00:00:00.000Z","latestAddedAt":"2026-03-30T22:09:51.545Z","productSlug":null,"productName":null},{"id":"src_gwaS6LcxpdXMxZdYQqzsw","slug":"posthog-js","name":"PostHog JS","type":"github","url":"https://github.com/PostHog/posthog-js","isPrimary":false,"isHidden":false,"fetchPriority":"normal","releaseCount":314,"latestVersion":"@posthog/nuxt@1.6.16","latestDate":"2026-04-18T01:13:52.000Z","latestAddedAt":"2026-04-18T05:01:27.177Z","productSlug":null,"productName":null},{"id":"src_f9HO02Q_05sz_r5GJ6GeG","slug":"posthog-node","name":"PostHog Node","type":"github","url":"https://github.com/PostHog/posthog-node","isPrimary":false,"isHidden":false,"fetchPriority":"normal","releaseCount":9,"latestVersion":"v1.3.0","latestDate":"2021-11-24T15:39:02.000Z","latestAddedAt":"2026-04-09T17:58:54.500Z","productSlug":null,"productName":null},{"id":"src_FPX9VKXmAUWIOOyKwibVI","slug":"posthog-python","name":"PostHog Python","type":"github","url":"https://github.com/PostHog/posthog-python","isPrimary":false,"isHidden":false,"fetchPriority":"normal","releaseCount":177,"latestVersion":"v7.12.0","latestDate":"2026-04-16T08:39:21.000Z","latestAddedAt":"2026-04-16T11:01:07.641Z","productSlug":null,"productName":null}],"overview":null,"knowledgePage":null,"playbook":{"scope":"playbook","content":"# PostHog — Playbook\n\n> Agent reference for fetching and maintaining **PostHog** (`posthog`) changelog sources.\n\n**5** active sources · domain: posthog.com\n\n## Sources\n\n| Name | ID | Type | URL | Last Fetched |\n|------|-----|------|-----|--------------|\n| PostHog Changelog | `src_ayguL4KiCWWacyZ6A3waO` | agent | https://posthog.com/changelog | Apr 18 |\n| PostHog | `src_aFPJh8KG1_D_eibUSxbNu` | github | https://github.com/PostHog/posthog | Apr 18 |\n| PostHog JS | `src_gwaS6LcxpdXMxZdYQqzsw` | github | https://github.com/PostHog/posthog-js | Apr 18 |\n| PostHog Python | `src_FPX9VKXmAUWIOOyKwibVI` | github | https://github.com/PostHog/posthog-python | Apr 18 |\n| PostHog Node | `src_f9HO02Q_05sz_r5GJ6GeG` | github | https://github.com/PostHog/posthog-node | Apr 18 |\n\n## Parse Instructions\n\n> To update, use `edit_source` with metadata — do not edit the playbook header.\n\n**PostHog Changelog** (`posthog-changelog`): PostHog runs a weekly kanban-style changelog. Individual feature updates ship throughout the week, then get bucketed under a weekly header like \"March 2026 - Week IV\" each Friday. Produce EXACTLY one release per weekly bucket — NEVER one release per individual item.  The page-data.json contains the full historical roadmap (700+ items). Group items by ISO week of their `date` field (Friday-anchored). Use a title like \"Month YYYY - Week N\" where N is the ordinal week within the month containing that Friday (Week I=first Friday, II=second, III=third, IV=fourth).  CRITICAL: Only extract the FIVE most recent weekly buckets — the older weeks are already stored. Skip anything dated before March 2026.  Publish date should be the Friday of that week. Summarize the bucket items into 1-3 concise sentences in the content body — list the headline features, do not quote full descriptions. Skip rollup items already labelled with weekly headers.\n\n## Agent Notes\n\n### Extraction patterns\n\n- **posthog** (GitHub): Core platform repo. Releases use standard GitHub releases with semver tags. Changelogs are detailed with breaking changes, new features, and bug fixes clearly separated. High release volume — use `--max` to avoid pulling the entire history.\n- **posthog-changelog** (scrape, render-required): Product changelog at posthog.com/changelog. Presented as a **weekly kanban-style board** — PostHog ships individual feature items throughout the week, then buckets them under a weekly header like \"March 2026 - Week IV\" each Friday. **Ingest one release per weekly bucket** (using the bucket header as the release title), not one per individual item. No dedicated changelog RSS exists: `/changelog/rss` 404s, and `/rss.xml` is the blog-only feed — do NOT configure either as the feed URL. The page is Gatsby/React-rendered, so static HTML fetch sees no items — `renderRequired: true` is mandatory. If headless rendering ever fails, raw per-item data is available at `https://posthog.com/page-data/changelog/page-data.json` (`result.data.allRoadmap.nodes` — each node has `date`, `title`, `description`, `topic`, `teams`, `githubUrls`, `githubPRMetadata`, `media`); items would need to be grouped by ISO week before ingesting. Entries are product announcements aimed at end users; may overlap with features announced via the core repo.\n- **posthog-js** (GitHub): Browser SDK. Frequent patch releases with concise changelogs. Releases are automated and follow conventional commit style.\n- **posthog-node** (GitHub): Node.js SDK. Less frequent than posthog-js. Standard GitHub release format.\n- **posthog-python** (GitHub): Python SDK. Similar cadence and format to posthog-node.\n\n### Known quirks\n\n- The core `posthog` repo has extremely high release volume due to continuous deployment — expect hundreds of releases. Always use `--max` when fetching.\n- `posthog-changelog` entries are editorial/marketing in tone and may not map 1:1 to versioned releases. They describe feature launches, not code versions. The weekly `#month-year-week-N` anchors are a display grouping produced client-side — they are NOT part of the raw data model.\n- Feed auto-discovery was previously fooled into setting `feedUrl = https://posthog.com/changelog/rss` (Vercel serves a cached HTML 404 there that occasionally returned 304 on conditional fetches, masking the problem as \"no change\"). If feed discovery ever re-runs on this source, verify the result by actually parsing the body — don't trust HEAD alone.\n- SDK repos (posthog-js, posthog-node, posthog-python) sometimes publish pre-release or canary tags that can be noisy. These are valid GitHub releases but may not represent stable versions.\n- No products are defined — all sources sit directly under the PostHog org. If the org grows, SDKs could be grouped under a \"PostHog SDKs\" product.\n\n### Source coverage\n\n- **Core platform**: Covered via GitHub releases (posthog) and the product changelog (posthog-changelog). Between these two sources, platform changes are well-represented from both developer and user perspectives.\n- **Client SDKs**: posthog-js covers the browser; posthog-node and posthog-python cover server-side. Other SDKs exist (React Native, Go, Ruby, PHP, Flutter, iOS, Android) but are not yet tracked as sources.\n- **Infrastructure/self-host**: Not currently covered. PostHog's Helm charts and self-hosted deployment updates are in separate repos.\n","updatedAt":"2026-04-18T23:23:44.042Z"}}