Skip to content

docs(emails): say capture_engagement keeps open and click tracking - #5629

Draft
Silthus wants to merge 3 commits into
mainfrom
docs/capture-engagement-keeps-tracking
Draft

docs(emails): say capture_engagement keeps open and click tracking#5629
Silthus wants to merge 3 commits into
mainfrom
docs/capture-engagement-keeps-tracking

Conversation

@Silthus

@Silthus Silthus commented Nov 9, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Problem

  • Developers and agents read captureEngagement: false on a code send as "no open or click tracking", which is wrong.
  • The option only keeps the email's engagement events off the recipient's person. PostHog still adds its open pixel, because code sends are transactional. It never rewrites a code send's links, so it counts no clicks.

Changes

Release info Sub-libraries affected

Libraries affected

  • posthog-node

Checklist

  • All commits are signed
  • Tests for new code: none, comment only
  • Accounted for backwards compatibility of any changes (no breaking changes!)

If releasing new changes

  • No changeset. The comment ships with the next posthog-node release.

🤖 Agent context

Autonomy: Human-driven (agent-assisted)

  • Claude Code, Claude Opus 5.5 (claude-opus-5-5), in a T3 Code thread that came out of a code-send trial.
  • One draft PR per repo carries the same wording: the API help text in PostHog/posthog, the 8 SDKs, posthog.com and the context-mill migrate-email skill.
  • A separate field that turns the pixel and link rewriting off is in progress and not merged, so this PR doesn't mention it.

🤖 Generated with Claude Code

@Silthus @claude
docs(emails): say capture_engagement keeps open and click tracking
a1975bf 
Turning engagement capture off only keeps the email's engagement events off
the recipient's person. The email still carries PostHog's open pixel and
tracked links, so the docs no longer read as "no open or click tracking".

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Silthus Silthus self-assigned this Nov 9, 2026
@github-actions

github-actions Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

📝 No Changeset Found

This PR doesn't include a changeset. A changeset is required to release a new version.

How to add a changeset

Run this command and follow the prompts:

pnpm changeset

Remember: Never use major version bumps for posthog-js as it's autoloaded by clients.

@github-actions

github-actions Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor
⚠️ `posthog-node` is modified but this PR has no changeset

This is informational — the PR is not blocked. Click the triangle above to collapse, or push a fix and this comment will auto-delete.

Modified in this PR but no changeset added:

  • posthog-node

If this change should ship, run pnpm changeset and select a bump level.
If it isn't user-facing (refactor with no behavior change, internal tooling, generated files), no action needed.

@github-actions

github-actions Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

Coherence

📄 0 spec file errors · ⛔ 0 broken rules · 🚪 1 unchecked input · 🐛 0 bugs that came back

What is Coherence?

Coherence compares the code with its spec files (*.spec.md). A spec file lists the rules for one part of the code.

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 (1)

  • public api in packages/web/Web.spec.md. The input comes from: host-app.
What this means and how to fix it

Input 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 ## entrances section of its spec file. Add one line under it:

  • If all of the input goes through one function that a rule in the spec protects, add guard: <function>.
  • If a rule in the spec already checks input from the same source, add the place's name to the entrances: line of that rule.
  • If the input needs no check, add control: none - <reason>.

To get the line to add, run npx --no -- coherence scaffold control "<name>".

@github-actions

github-actions Bot commented Nov 9, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Node SDK acceptance v2

Commit: cace3fa
Workflow run and artifacts

Capture v0

✅ 83 passed / ❌ 4 non-passing / ⚠️ 954 not selected

Drill-down: run artifacts → node-v2-v0 → acceptance/report.json.diagnostics.json (match case_id below).

❌ server_snapshot_payload_false — failed_assertion

Expected native data result

Code: snapshot_result

Failed step: acceptance/public/evaluate-flags.feature:868

the public snapshot outcomes should have these semantics:
❌ server_snapshot_payload_zero — failed_assertion

Expected native data result

Code: snapshot_result

Failed step: acceptance/public/evaluate-flags.feature:868

the public snapshot outcomes should have these semantics:
❌ server_snapshot_payload_null — failed_assertion

Expected native data result

Code: snapshot_result

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_assertion

Flags field differs

Code: flag_request_field

Failed step: migration/yaml-parity-v1/remote-flags-v1.feature:134

the first flags request field "geoip_disable" should equal JSON false

Operation: /flags/

Field: geoip_disable

Expected:

false

Actual value:

true

Harness exit: 1; report validation exit: 1.

Capture v1

✅ 148 passed / ❌ 4 non-passing / ⚠️ 889 not selected

Drill-down: run artifacts → node-v2-v1 → acceptance/report.json.diagnostics.json (match case_id below).

❌ server_snapshot_payload_false — failed_assertion

Expected native data result

Code: snapshot_result

Failed step: acceptance/public/evaluate-flags.feature:868

the public snapshot outcomes should have these semantics:
❌ server_snapshot_payload_zero — failed_assertion

Expected native data result

Code: snapshot_result

Failed step: acceptance/public/evaluate-flags.feature:868

the public snapshot outcomes should have these semantics:
❌ server_snapshot_payload_null — failed_assertion

Expected native data result

Code: snapshot_result

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_assertion

Flags field differs

Code: flag_request_field

Failed step: migration/yaml-parity-v1/remote-flags-v1.feature:134

the first flags request field "geoip_disable" should equal JSON false

Operation: /flags/

Field: geoip_disable

Expected:

false

Actual value:

true

Harness exit: 1; report validation exit: 1.

@github-actions

github-actions Bot commented Nov 9, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

SDK performance: posthog-node

Benchmarks 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
Test Measurement Before PR With PR Change Assessment
Capture and deliver events (32-byte payload, burst)
Shard: capture		 Allocations per operation — — — unavailable; base:​ unsupported; head:​ unsupported; base:​ V8 samples do not expose total allocation count; sample count is not object count.​; head:​ V8 samples do not expose total allocation count; sample count is not object count.​
Capture and deliver events (4,096-byte payload, burst)
Shard: capture		 Allocations per operation — — — unavailable; base:​ unsupported; head:​ unsupported; base:​ V8 samples do not expose total allocation count; sample count is not object count.​; head:​ V8 samples do not expose total allocation count; sample count is not object count.​
Capture and deliver events (32-byte payload, steady)
Shard: capture		 Allocations per operation — — — unavailable; base:​ unsupported; head:​ unsupported; base:​ V8 samples do not expose total allocation count; sample count is not object count.​; head:​ V8 samples do not expose total allocation count; sample count is not object count.​
Capture and deliver events (4,096-byte payload, steady)
Shard: capture		 Allocations per operation — — — unavailable; base:​ unsupported; head:​ unsupported; base:​ V8 samples do not expose total allocation count; sample count is not object count.​; head:​ V8 samples do not expose total allocation count; sample count is not object count.​
Queue an event (32-byte payload)
Shard: capture		 Allocations per operation — — — unavailable; base:​ unsupported; head:​ unsupported; base:​ V8 samples do not expose total allocation count; sample count is not object count.​; head:​ V8 samples do not expose total allocation count; sample count is not object count.​
Queue an event (4,096-byte payload)
Shard: capture		 Allocations per operation — — — unavailable; base:​ unsupported; head:​ unsupported; base:​ V8 samples do not expose total allocation count; sample count is not object count.​; head:​ V8 samples do not expose total allocation count; sample count is not object count.​
Evaluate all 10 flags
Shard: flags-scaling		 Allocations per operation — — — unavailable; base:​ unsupported; head:​ unsupported; base:​ V8 samples do not expose total allocation count; sample count is not object count.​; head:​ V8 samples do not expose total allocation count; sample count is not object count.​
Evaluate all 100 flags
Shard: flags-scaling		 Allocations per operation — — — unavailable; base:​ unsupported; head:​ unsupported; base:​ V8 samples do not expose total allocation count; sample count is not object count.​; head:​ V8 samples do not expose total allocation count; sample count is not object count.​
Evaluate all 1,000 flags
Shard: flags-scaling		 Allocations per operation — — — unavailable; base:​ unsupported; head:​ unsupported; base:​ V8 samples do not expose total allocation count; sample count is not object count.​; head:​ V8 samples do not expose total allocation count; sample count is not object count.​
Evaluate one boolean flag
Shard: flags-single		 Allocations per operation — — — unavailable; base:​ unsupported; head:​ unsupported; base:​ V8 samples do not expose total allocation count; sample count is not object count.​; head:​ V8 samples do not expose total allocation count; sample count is not object count.​
Evaluate a cohort-filtered flag
Shard: flags-single		 Allocations per operation — — — unavailable; base:​ unsupported; head:​ unsupported; base:​ V8 samples do not expose total allocation count; sample count is not object count.​; head:​ V8 samples do not expose total allocation count; sample count is not object count.​
Evaluate a flag (early match)
Shard: flags-single		 Allocations per operation — — — unavailable; base:​ unsupported; head:​ unsupported; base:​ V8 samples do not expose total allocation count; sample count is not object count.​; head:​ V8 samples do not expose total allocation count; sample count is not object count.​
Evaluate a flag (late match)
Shard: flags-single		 Allocations per operation — — — unavailable; base:​ unsupported; head:​ unsupported; base:​ V8 samples do not expose total allocation count; sample count is not object count.​; head:​ V8 samples do not expose total allocation count; sample count is not object count.​
Evaluate a flag (no match)
Shard: flags-single		 Allocations per operation — — — unavailable; base:​ unsupported; head:​ unsupported; base:​ V8 samples do not expose total allocation count; sample count is not object count.​; head:​ V8 samples do not expose total allocation count; sample count is not object count.​
Evaluate a property-filtered flag
Shard: flags-single		 Allocations per operation — — — unavailable; base:​ unsupported; head:​ unsupported; base:​ V8 samples do not expose total allocation count; sample count is not object count.​; head:​ V8 samples do not expose total allocation count; sample count is not object count.​
Evaluate a regex-filtered flag
Shard: flags-single		 Allocations per operation — — — unavailable; base:​ unsupported; head:​ unsupported; base:​ V8 samples do not expose total allocation count; sample count is not object count.​; head:​ V8 samples do not expose total allocation count; sample count is not object count.​
Evaluate a rollout flag
Shard: flags-single		 Allocations per operation — — — unavailable; base:​ unsupported; head:​ unsupported; base:​ V8 samples do not expose total allocation count; sample count is not object count.​; head:​ V8 samples do not expose total allocation count; sample count is not object count.​
Evaluate a multivariate flag
Shard: flags-single		 Allocations per operation — — — unavailable; base:​ unsupported; head:​ unsupported; base:​ V8 samples do not expose total allocation count; sample count is not object count.​; head:​ V8 samples do not expose total allocation count; sample count is not object count.​
Capture and deliver events (32-byte payload, burst)
Shard: capture		 Allocated memory per operation (estimated) 10.31 KiB/op 10.02 KiB/op 2.8% less memory Not flagged
Capture and deliver events (32-byte payload, burst)
Shard: capture		 Time per operation 23.05 µs/op 23.21 µs/op 0.7% more time Not flagged
Capture and deliver events (32-byte payload, burst)
Shard: capture		 Idle process memory (RSS) 102.58 MiB 102.63 MiB <0.1% more memory Not flagged
Capture and deliver events (32-byte payload, burst)
Shard: capture		 Observed peak process memory (RSS) 105.83 MiB 106.38 MiB 0.5% more memory Not flagged
Capture and deliver events (32-byte payload, burst)
Shard: capture		 Managed heap after settling 9.97 MiB 9.97 MiB <0.1% less memory Not flagged
Capture and deliver events (32-byte payload, burst)
Shard: capture		 Process memory after settling (RSS) 105.52 MiB 106.09 MiB 0.5% more memory Not flagged
Capture and deliver events (32-byte payload, burst)
Shard: capture		 Process CPU time per operation 38.96 µs/op 38.51 µs/op 1.1% less time Not flagged
Capture and deliver events (32-byte payload, burst)
Shard: capture		 Lifetime peak process memory (RSS) 106.09 MiB 106.58 MiB 0.5% more memory Not flagged
Capture and deliver events (4,096-byte payload, burst)
Shard: capture		 Allocated memory per operation (estimated) 17.94 KiB/op 17.62 KiB/op 1.8% less memory Not flagged
Capture and deliver events (4,096-byte payload, burst)
Shard: capture		 Time per operation 36.87 µs/op 36.82 µs/op 0.1% less time Not flagged
Capture and deliver events (4,096-byte payload, burst)
Shard: capture		 Idle process memory (RSS) 103.08 MiB 103.06 MiB <0.1% less memory Not flagged
Capture and deliver events (4,096-byte payload, burst)
Shard: capture		 Observed peak process memory (RSS) 113.59 MiB 113.5 MiB <0.1% less memory Not flagged
Capture and deliver events (4,096-byte payload, burst)
Shard: capture		 Managed heap after settling 9.98 MiB 9.98 MiB <0.1% less memory Not flagged
Capture and deliver events (4,096-byte payload, burst)
Shard: capture		 Process memory after settling (RSS) 109.55 MiB 109.47 MiB <0.1% less memory Not flagged
Capture and deliver events (4,096-byte payload, burst)
Shard: capture		 Process CPU time per operation 53.78 µs/op 52.93 µs/op 1.6% less time Not flagged
Capture and deliver events (4,096-byte payload, burst)
Shard: capture		 Lifetime peak process memory (RSS) 116.35 MiB 116.35 MiB <0.1% more memory Not flagged
Capture and deliver events (32-byte payload, steady)
Shard: capture		 Allocated memory per operation (estimated) 9.96 KiB/op 10.45 KiB/op 4.9% more memory Not flagged
Capture and deliver events (32-byte payload, steady)
Shard: capture		 Time per operation 22.68 µs/op 22.36 µs/op 1.5% less time Not flagged
Capture and deliver events (32-byte payload, steady)
Shard: capture		 Idle process memory (RSS) 102.49 MiB 102.37 MiB 0.1% less memory Not flagged
Capture and deliver events (32-byte payload, steady)
Shard: capture		 Observed peak process memory (RSS) 106.59 MiB 106.52 MiB <0.1% less memory Not flagged
Capture and deliver events (32-byte payload, steady)
Shard: capture		 Managed heap after settling 10.05 MiB 10.05 MiB <0.1% less memory Not flagged
Capture and deliver events (32-byte payload, steady)
Shard: capture		 Process memory after settling (RSS) 106.59 MiB 106.59 MiB <0.1% less memory Not flagged
Capture and deliver events (32-byte payload, steady)
Shard: capture		 Process CPU time per operation 38.67 µs/op 38.44 µs/op 0.6% less time Not flagged
Capture and deliver events (32-byte payload, steady)
Shard: capture		 Lifetime peak process memory (RSS) 106.74 MiB 106.61 MiB 0.1% less memory Not flagged
Capture and deliver events (4,096-byte payload, steady)
Shard: capture		 Allocated memory per operation (estimated) 17.6 KiB/op 17.83 KiB/op 1.3% more memory Not flagged
Capture and deliver events (4,096-byte payload, steady)
Shard: capture		 Time per operation 35.65 µs/op 34.04 µs/op 4.5% less time Not flagged
Capture and deliver events (4,096-byte payload, steady)
Shard: capture		 Idle process memory (RSS) 102.78 MiB 102.81 MiB <0.1% more memory Not flagged
Capture and deliver events (4,096-byte payload, steady)
Shard: capture		 Observed peak process memory (RSS) 109.07 MiB 109.62 MiB 0.5% more memory Not flagged
Capture and deliver events (4,096-byte payload, steady)
Shard: capture		 Managed heap after settling 10.06 MiB 10.06 MiB <0.1% less memory Not flagged
Capture and deliver events (4,096-byte payload, steady)
Shard: capture		 Process memory after settling (RSS) 107.87 MiB 108.45 MiB 0.5% more memory Not flagged
Capture and deliver events (4,096-byte payload, steady)
Shard: capture		 Process CPU time per operation 52.56 µs/op 50.51 µs/op 3.9% less time Not flagged
Capture and deliver events (4,096-byte payload, steady)
Shard: capture		 Lifetime peak process memory (RSS) 109.12 MiB 109.62 MiB 0.5% more memory Not flagged
Queue an event (32-byte payload)
Shard: capture		 Allocated memory per operation (estimated) 8.91 KiB/op 8.26 KiB/op 7.3% less memory Not flagged
Queue an event (32-byte payload)
Shard: capture		 Time per operation 16.95 µs/op 16.28 µs/op 4% less time Not flagged
Queue an event (32-byte payload)
Shard: capture		 Process CPU time per operation 32.54 µs/op 31.3 µs/op 3.8% less time Not flagged
Queue an event (4,096-byte payload)
Shard: capture		 Allocated memory per operation (estimated) 8.72 KiB/op 8.65 KiB/op 0.8% less memory Not flagged
Queue an event (4,096-byte payload)
Shard: capture		 Time per operation 15.32 µs/op 15.17 µs/op 1% less time Not flagged
Queue an event (4,096-byte payload)
Shard: capture		 Process CPU time per operation 29.06 µs/op 29.45 µs/op 1.3% more time Not flagged
Evaluate all 10 flags
Shard: flags-scaling		 Allocated memory per operation (estimated) 132.95 KiB/op 132.45 KiB/op 0.4% less memory Not flagged
Evaluate all 10 flags
Shard: flags-scaling		 Time per operation 143.34 µs/op 144.28 µs/op 0.7% more time Not flagged
Evaluate all 10 flags
Shard: flags-scaling		 Process CPU time per operation 252.85 µs/op 255.7 µs/op 1.1% more time Not flagged
Evaluate all 100 flags
Shard: flags-scaling		 Allocated memory per operation (estimated) 1.23 MiB/op 1.23 MiB/op 0.2% more memory Not flagged
Evaluate all 100 flags
Shard: flags-scaling		 Time per operation 1.27 ms/op 1.26 ms/op 1% less time Not flagged
Evaluate all 100 flags
Shard: flags-scaling		 Process CPU time per operation 2.19 ms/op 2.18 ms/op 0.5% less time Not flagged
Evaluate all 1,000 flags
Shard: flags-scaling		 Allocated memory per operation (estimated) 12.14 MiB/op 12.12 MiB/op 0.2% less memory Not flagged
Evaluate all 1,000 flags
Shard: flags-scaling		 Time per operation 14.61 ms/op 14.81 ms/op 1.4% more time Not flagged
Evaluate all 1,000 flags
Shard: flags-scaling		 Process CPU time per operation 22.92 ms/op 23.29 ms/op 1.6% more time Not flagged
Evaluate 1,000 flags under concurrent load
Shard: flags-memory		 Idle process memory (RSS) 273.68 MiB 272.07 MiB 0.6% less memory Not flagged
Evaluate 1,000 flags under concurrent load
Shard: flags-memory		 Observed peak process memory (RSS) 273.68 MiB 272.14 MiB 0.6% less memory Not flagged
Evaluate 1,000 flags under concurrent load
Shard: flags-memory		 Managed heap after settling 9.63 MiB 9.62 MiB <0.1% less memory Not flagged
Evaluate 1,000 flags under concurrent load
Shard: flags-memory		 Process memory after settling (RSS) 272.9 MiB 271.53 MiB 0.5% less memory Not flagged
Evaluate 1,000 flags under concurrent load
Shard: flags-memory		 Lifetime peak process memory (RSS) 274.96 MiB 273.17 MiB 0.6% less memory Not flagged
Refresh 1,000 flag definitions
Shard: flags-memory		 Idle process memory (RSS) 227.5 MiB 227.41 MiB <0.1% less memory Not flagged
Refresh 1,000 flag definitions
Shard: flags-memory		 Observed peak process memory (RSS) 239.85 MiB 239.46 MiB 0.2% less memory Not flagged
Refresh 1,000 flag definitions
Shard: flags-memory		 Managed heap after settling 11.64 MiB 11.63 MiB <0.1% less memory Not flagged
Refresh 1,000 flag definitions
Shard: flags-memory		 Process memory after settling (RSS) 235.61 MiB 235.22 MiB 0.2% less memory Not flagged
Refresh 1,000 flag definitions
Shard: flags-memory		 Lifetime peak process memory (RSS) 242.34 MiB 241.76 MiB 0.2% less memory Not flagged
Evaluate one boolean flag
Shard: flags-single		 Allocated memory per operation (estimated) 17.11 KiB/op 17.05 KiB/op 0.4% less memory Not flagged
Evaluate one boolean flag
Shard: flags-single		 Time per operation 88.11 µs/op 85.99 µs/op 2.4% less time Not flagged
Evaluate one boolean flag
Shard: flags-single		 Process CPU time per operation 97.22 µs/op 94.6 µs/op 2.7% less time Not flagged
Evaluate a cohort-filtered flag
Shard: flags-single		 Allocated memory per operation (estimated) 14.09 KiB/op 14.15 KiB/op 0.4% more memory Not flagged
Evaluate a cohort-filtered flag
Shard: flags-single		 Time per operation 47.73 µs/op 49.28 µs/op 3.3% more time Not flagged
Evaluate a cohort-filtered flag
Shard: flags-single		 Process CPU time per operation 56.55 µs/op 58.44 µs/op 3.3% more time Not flagged
Evaluate a flag (early match)
Shard: flags-single		 Allocated memory per operation (estimated) 17.45 KiB/op 17.59 KiB/op 0.8% more memory Not flagged
Evaluate a flag (early match)
Shard: flags-single		 Time per operation 50.23 µs/op 49.93 µs/op 0.6% less time Not flagged
Evaluate a flag (early match)
Shard: flags-single		 Process CPU time per operation 58.61 µs/op 58.66 µs/op <0.1% more time Not flagged
Evaluate a flag (late match)
Shard: flags-single		 Allocated memory per operation (estimated) 22.33 KiB/op 22.33 KiB/op <0.1% more memory Not flagged
Evaluate a flag (late match)
Shard: flags-single		 Time per operation 48.74 µs/op 50.65 µs/op 3.9% more time Not flagged
Evaluate a flag (late match)
Shard: flags-single		 Process CPU time per operation 56.76 µs/op 59 µs/op 3.9% more time Not flagged
Evaluate a flag (no match)
Shard: flags-single		 Allocated memory per operation (estimated) 17.06 KiB/op 17.06 KiB/op <0.1% more memory Not flagged
Evaluate a flag (no match)
Shard: flags-single		 Time per operation 5.66 µs/op 5.69 µs/op 0.5% more time Not flagged
Evaluate a flag (no match)
Shard: flags-single		 Process CPU time per operation 10.21 µs/op 10.32 µs/op 1.1% more time Not flagged
Evaluate a property-filtered flag
Shard: flags-single		 Allocated memory per operation (estimated) 12.68 KiB/op 12.66 KiB/op 0.2% less memory Not flagged
Evaluate a property-filtered flag
Shard: flags-single		 Time per operation 47.66 µs/op 49.86 µs/op 4.6% more time Not flagged
Evaluate a property-filtered flag
Shard: flags-single		 Process CPU time per operation 55.58 µs/op 57.85 µs/op 4.1% more time Not flagged
Evaluate a regex-filtered flag
Shard: flags-single		 Allocated memory per operation (estimated) 18.24 KiB/op 18.39 KiB/op 0.8% more memory Not flagged
Evaluate a regex-filtered flag
Shard: flags-single		 Time per operation 98.49 µs/op 95.67 µs/op 2.9% less time Not flagged
Evaluate a regex-filtered flag
Shard: flags-single		 Process CPU time per operation 110.3 µs/op 106.72 µs/op 3.2% less time Not flagged
Evaluate a rollout flag
Shard: flags-single		 Allocated memory per operation (estimated) 14.27 KiB/op 14.22 KiB/op 0.4% less memory Not flagged
Evaluate a rollout flag
Shard: flags-single		 Time per operation 66.98 µs/op 69.03 µs/op 3.1% more time Not flagged
Evaluate a rollout flag
Shard: flags-single		 Process CPU time per operation 74.32 µs/op 77.46 µs/op 4.2% more time Not flagged
Evaluate a multivariate flag
Shard: flags-single		 Allocated memory per operation (estimated) 17.55 KiB/op 17.5 KiB/op 0.3% less memory Not flagged
Evaluate a multivariate flag
Shard: flags-single		 Time per operation 89.34 µs/op 85.88 µs/op 3.9% less time Not flagged
Evaluate a multivariate flag
Shard: flags-single		 Process CPU time per operation 98.86 µs/op 94.07 µs/op 4.8% less time Not flagged

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 c9c47d39e97818868b81f5acc8f71b01cbefe634 → cace3fa4248cf67be024724b99514614aba28e0c.

Full report and diagnostics

102 metric rows; 102 rows shown in all results. Omitted or shortened data remain in comparison.json, including per-runner environments, resource limits, measurement methods, samples and checkpoints.

Silthus and others added 2 commits November 9, 2026 12:07
@Silthus @claude
docs: say a code send never rewrites its links
12f56ab 
Code sends are sensitive, so PostHog leaves their links alone and only the
open pixel counts anything. The earlier wording said PostHog rewrites links
to count clicks, which is false for a code send.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Silthus @claude
docs(node): refresh the latest public API reference for captureEngage…
cace3fa 
…ment

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
posthog[bot]
posthog Bot reviewed Nov 9, 2026
View reviewed changes

@posthog posthog Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

PostHog Review · Standard · reviewed 12f56ab: no findings.

posthog[bot]
posthog Bot reviewed Nov 9, 2026
View reviewed changes

@posthog posthog Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

PostHog Review · Standard · reviewed cace3fa: no findings.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@posthog posthog[bot] posthog[bot] left review comments

At least 1 approving review is required to merge this pull request.

Assignees

@Silthus Silthus

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@Silthus