Repository navigation
Conversation
The Markdown references replace HogRef, so this removes the api-extractor pipeline, the HogRef scripts and tests, and the public API check. `pnpm generate-references` now runs the Markdown generator. The HogRef JSON files under references/ stay, so the pages that read them keep working until posthog.com moves off HogRef. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
📝 No Changeset FoundThis PR doesn't include a changeset. A changeset is required to release a new version. How to add a changesetRun this command and follow the prompts: pnpm changesetRemember: Never use |
Replay incident risk checkThis diff touches code involved in past incidents. This is a heads-up, not a verdict: read the matched sections of INCIDENTS.md and answer their review questions before merging. For a judgment on whether this diff has the same failure mode, run the |
Coherence📄 0 spec file errors · ⛔ 0 broken rules · 🚪 2 unchecked inputs · 🐛 0 bugs that came back What is Coherence?Coherence compares the code with its spec files ( This check read 44 parts of the code and 7 rules. Note These findings do not make this check fail. None of these findings are in files that this pull request changes. You do not need to fix them in this pull request. 🚪 Unchecked inputs (2)
What this means and how to fix itInput from outside this code comes in at these places. The spec does not say what checks that input. 10 more places were already like this when Coherence was added. This list does not show them. To close one of these, find the place by its name in the
To get the line to add, run |
|
Size Change: 0 B Total Size: 26.5 MB ℹ️ View Unchanged
|
Node SDK acceptance v2Commit: d249fb9 Capture v0✅ 83 passed / ❌ 4 non-passing / Drill-down: run artifacts → ❌ server_snapshot_payload_false — failed_assertionExpected native data result Code: Failed step: acceptance/public/evaluate-flags.feature:868 the public snapshot outcomes should have these semantics: ❌ server_snapshot_payload_zero — failed_assertionExpected native data result Code: Failed step: acceptance/public/evaluate-flags.feature:868 the public snapshot outcomes should have these semantics: ❌ server_snapshot_payload_null — failed_assertionExpected native data result Code: Failed step: acceptance/public/evaluate-flags.feature:868 the public snapshot outcomes should have these semantics: ❌ migration/yaml-parity-v1/remote-flags-v1.feature::Omitted GeoIP settings default to enabled in flag requests — failed_assertionFlags field differs Code: Failed step: migration/yaml-parity-v1/remote-flags-v1.feature:134 the first flags request field "geoip_disable" should equal JSON false Operation: Field: Expected: false Actual value: true Harness exit: 1; report validation exit: 1. Capture v1✅ 148 passed / ❌ 4 non-passing / Drill-down: run artifacts → ❌ server_snapshot_payload_false — failed_assertionExpected native data result Code: Failed step: acceptance/public/evaluate-flags.feature:868 the public snapshot outcomes should have these semantics: ❌ server_snapshot_payload_zero — failed_assertionExpected native data result Code: Failed step: acceptance/public/evaluate-flags.feature:868 the public snapshot outcomes should have these semantics: ❌ server_snapshot_payload_null — failed_assertionExpected native data result Code: Failed step: acceptance/public/evaluate-flags.feature:868 the public snapshot outcomes should have these semantics: ❌ migration/yaml-parity-v1/remote-flags-v1.feature::Omitted GeoIP settings default to enabled in flag requests — failed_assertionFlags field differs Code: Failed step: migration/yaml-parity-v1/remote-flags-v1.feature:134 the first flags request field "geoip_disable" should equal JSON false Operation: Field: Expected: false Actual value: true Harness exit: 1; report validation exit: 1. |
SDK performance: posthog-nodeBenchmarks completed. No changes flagged for review. Flags require at least a 5% change in the median and all six pairs agreeing on direction. This is a noise filter, not proof of a performance change or a CI gate. View all results
Values are medians of paired measurements. Not flagged does not mean unchanged. Unavailable means a measurement could not be provided, not zero. Estimated allocation measurements retain their instrumentation uncertainty. RSS measures the whole process, not just SDK allocations; observed peaks are sampled checkpoints. Paired ranges in the diagnostics describe variability, not confidence intervals. Each shard uses its own runner; compare Before PR against With PR within a row, not across shards. Compared 102 metric rows; 102 rows shown in all results. Omitted or shortened data remain in |
Keeps scripts/check-public-api.js, now for the Markdown pages only, so CI still fails on a stale reference page after HogRef goes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ocs/sdk-reference-remove-hogref
…ocs/sdk-reference-remove-hogref
Problem
The Markdown references in #5589 replace HogRef. Stacked on #5589.
Changes
scripts/docs, thegenerate-docsscripts, the api-extractor and tsdoc configs, and their workflow and release steps.pnpm generate-referencesnow runs the Markdown generator.check-public-api.jsstays and checks only the Markdown pages, soPosthog-js.spec.mdstays valid.*-references-*.jsonfiles stay until posthog.com moves off HogRef, so the HogRef pages keep working.Tested: After the removal, regenerating gives no diff and
pnpm check:public-apipasses.Checklist
🤖 Agent context
Autonomy: Human-driven (agent-assisted)
Claude Code (Opus 5.5) built and opened it, directed by Vincent. Not yet reviewed line by line.
Merge order
Parked: this stack ships with the posthog-node 6 release (#5407). It replaces #5565, #5566 and #5568.
🤖 Generated with Claude Code