[dependabot]

Bumps the github-actions group with 4 updates: github/codeql-action/init, github/codeql-action/analyze, ruby/setup-ruby and PostHog/posthog-sdk-test-harness/.github/workflows/test-sdk-action.yml.

Updates github/codeql-action/init from 4.38.3 to 4.39.1

Release notes

Sourced from github/codeql-action/init's releases.

v4.39.1

• Update default CodeQL bundle version to 2.27.3. #4256

v4.39.0

• Breaking change: Bump the minimum required CodeQL bundle version to 2.20.7. #4205
• The codeql-action/analyze step now validates that a correct argument for the checkout_path input has been provided. The checkout_path input must be set to the path where the repository that is being analyzed is checked out at on the runner, if that path is something other than the workspace root. If the path does not point to a repository checkout or is different from the path that was used by codeql-action/init, then the CodeQL Action now produces a warning. #4148
• Resolved an issue with third-party caching implementations that prevented caches from being restored correctly. #4206
• The codeql-action/start-proxy step that is used in Code Scanning Default Setup now finds CodeQL releases using the same logic as codeql-action/init. This primarily benefits customers who are using GitHub instances other than github.com where the codeql-action/start-proxy step may previously have been unable to locate recent releases and ended up using outdated versions of the private registry authentication proxy as a result. #4198

Changelog

Sourced from github/codeql-action/init's changelog.

CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

[UNRELEASED]

No user facing changes.

4.39.1 - 21 Oct 2026

• Update default CodeQL bundle version to 2.27.3. #4256

4.39.0 - 15 Oct 2026

• Breaking change: Bump the minimum required CodeQL bundle version to 2.20.7. #4205
• The codeql-action/analyze step now validates that a correct argument for the checkout_path input has been provided. The checkout_path input must be set to the path where the repository that is being analyzed is checked out at on the runner, if that path is something other than the workspace root. If the path does not point to a repository checkout or is different from the path that was used by codeql-action/init, then the CodeQL Action now produces a warning. #4148
• Resolved an issue with third-party caching implementations that prevented caches from being restored correctly. #4206
• The codeql-action/start-proxy step that is used in Code Scanning Default Setup now finds CodeQL releases using the same logic as codeql-action/init. This primarily benefits customers who are using GitHub instances other than github.com where the codeql-action/start-proxy step may previously have been unable to locate recent releases and ended up using outdated versions of the private registry authentication proxy as a result. #4198

4.38.3 - 08 Oct 2026

• Upcoming breaking change: CodeQL version 2.21.2 and earlier were discontinued on 24 September 2026 alongside GitHub Enterprise Server 3.17, and will be unsupported by the next minor release of the CodeQL Action. Added a deprecation warning for customers using these versions of CodeQL. #4188
• Update default CodeQL bundle version to 2.27.2. #4203
• Fixed a bug where the decision of whether to use a per-language bundle did not account for custom configurations that reference queries outside of compiled CodeQL packs. This issue was caught during internal testing and did not affect any customer repositories. We will resume the roll out of per-language bundles in the coming weeks. #4184

4.38.2 - 24 Sept 2026

• Update default CodeQL bundle version to 2.27.1. #4160

4.38.1 - 18 Sept 2026

• The CodeQL Action now has experimental support for CodeQL releases for which per-language bundles are available. Per-language bundles support analysis for a single language and are therefore smaller than the combined bundles that allow analysis for all supported languages. As a result, per-language bundles take up less space on disk and are faster to download. We expect to roll this change out to everyone in the coming weeks. #4146

4.38.0 - 09 Sept 2026

• On GitHub-hosted runners, the CodeQL Action now deletes unused CodeQL bundles from the toolcache before downloading a different bundle, which frees up disk space for the analysis. We expect to roll this change out to everyone in September. #4124
• The CodeQL Action now supports CodeQL releases that are compatible with Linux Arm64 and downloads the native linux-arm64 CodeQL bundle when available. #4072
• Update default CodeQL bundle version to 2.27.0. #4129

4.37.9 - 26 Aug 2026

• Update default CodeQL bundle version to 2.26.4. #4106

4.37.8 - 21 Aug 2026

No user facing changes.

4.37.7 - 13 Aug 2026

• Update default CodeQL bundle version to 2.26.3. #4085

... (truncated)

Commits

• 9b32540 Merge pull request #4257 from github/update-v4.39.1-c5a2f4b0f
• b5e1ed9 Trigger workflows
• 20f5ec3 Update changelog for v4.39.1
• c5a2f4b Merge pull request #4245 from github/henrymercer/graduate-overlay-trap-caching
• 61a5a80 Merge pull request #4256 from github/update-bundle/codeql-bundle-v2.27.3
• 3dd33f8 Merge pull request #4249 from github/mbg/upload-improvements-for-4223
• b96e339 Change comment for getConfig call in upload-sarif
• 7fa4518 Use shouldSkipSarifUpload in analyze-action.ts
• a69c7cb Document that setting the env vars to false takes precedence
• 74ddcd9 Fix typo in comment
• Additional commits viewable in compare view

Updates github/codeql-action/analyze from 4.38.3 to 4.39.1

Release notes

Sourced from github/codeql-action/analyze's releases.

v4.39.1

• Update default CodeQL bundle version to 2.27.3. #4256

v4.39.0

• Breaking change: Bump the minimum required CodeQL bundle version to 2.20.7. #4205
• The codeql-action/analyze step now validates that a correct argument for the checkout_path input has been provided. The checkout_path input must be set to the path where the repository that is being analyzed is checked out at on the runner, if that path is something other than the workspace root. If the path does not point to a repository checkout or is different from the path that was used by codeql-action/init, then the CodeQL Action now produces a warning. #4148
• Resolved an issue with third-party caching implementations that prevented caches from being restored correctly. #4206
• The codeql-action/start-proxy step that is used in Code Scanning Default Setup now finds CodeQL releases using the same logic as codeql-action/init. This primarily benefits customers who are using GitHub instances other than github.com where the codeql-action/start-proxy step may previously have been unable to locate recent releases and ended up using outdated versions of the private registry authentication proxy as a result. #4198

Changelog

Sourced from github/codeql-action/analyze's changelog.

CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

[UNRELEASED]

No user facing changes.

4.39.1 - 21 Oct 2026

• Update default CodeQL bundle version to 2.27.3. #4256

4.39.0 - 15 Oct 2026

• Breaking change: Bump the minimum required CodeQL bundle version to 2.20.7. #4205
• The codeql-action/analyze step now validates that a correct argument for the checkout_path input has been provided. The checkout_path input must be set to the path where the repository that is being analyzed is checked out at on the runner, if that path is something other than the workspace root. If the path does not point to a repository checkout or is different from the path that was used by codeql-action/init, then the CodeQL Action now produces a warning. #4148
• Resolved an issue with third-party caching implementations that prevented caches from being restored correctly. #4206
• The codeql-action/start-proxy step that is used in Code Scanning Default Setup now finds CodeQL releases using the same logic as codeql-action/init. This primarily benefits customers who are using GitHub instances other than github.com where the codeql-action/start-proxy step may previously have been unable to locate recent releases and ended up using outdated versions of the private registry authentication proxy as a result. #4198

4.38.3 - 08 Oct 2026

• Upcoming breaking change: CodeQL version 2.21.2 and earlier were discontinued on 24 September 2026 alongside GitHub Enterprise Server 3.17, and will be unsupported by the next minor release of the CodeQL Action. Added a deprecation warning for customers using these versions of CodeQL. #4188
• Update default CodeQL bundle version to 2.27.2. #4203
• Fixed a bug where the decision of whether to use a per-language bundle did not account for custom configurations that reference queries outside of compiled CodeQL packs. This issue was caught during internal testing and did not affect any customer repositories. We will resume the roll out of per-language bundles in the coming weeks. #4184

4.38.2 - 24 Sept 2026

• Update default CodeQL bundle version to 2.27.1. #4160

4.38.1 - 18 Sept 2026

• The CodeQL Action now has experimental support for CodeQL releases for which per-language bundles are available. Per-language bundles support analysis for a single language and are therefore smaller than the combined bundles that allow analysis for all supported languages. As a result, per-language bundles take up less space on disk and are faster to download. We expect to roll this change out to everyone in the coming weeks. #4146

4.38.0 - 09 Sept 2026

• On GitHub-hosted runners, the CodeQL Action now deletes unused CodeQL bundles from the toolcache before downloading a different bundle, which frees up disk space for the analysis. We expect to roll this change out to everyone in September. #4124
• The CodeQL Action now supports CodeQL releases that are compatible with Linux Arm64 and downloads the native linux-arm64 CodeQL bundle when available. #4072
• Update default CodeQL bundle version to 2.27.0. #4129

4.37.9 - 26 Aug 2026

• Update default CodeQL bundle version to 2.26.4. #4106

4.37.8 - 21 Aug 2026

No user facing changes.

4.37.7 - 13 Aug 2026

• Update default CodeQL bundle version to 2.26.3. #4085

... (truncated)

Commits

• 9b32540 Merge pull request #4257 from github/update-v4.39.1-c5a2f4b0f
• b5e1ed9 Trigger workflows
• 20f5ec3 Update changelog for v4.39.1
• c5a2f4b Merge pull request #4245 from github/henrymercer/graduate-overlay-trap-caching
• 61a5a80 Merge pull request #4256 from github/update-bundle/codeql-bundle-v2.27.3
• 3dd33f8 Merge pull request #4249 from github/mbg/upload-improvements-for-4223
• b96e339 Change comment for getConfig call in upload-sarif
• 7fa4518 Use shouldSkipSarifUpload in analyze-action.ts
• a69c7cb Document that setting the env vars to false takes precedence
• 74ddcd9 Fix typo in comment
• Additional commits viewable in compare view

Updates ruby/setup-ruby from 1.329.0 to 1.332.0

Release notes

Sourced from ruby/setup-ruby's releases.

v1.332.0

What's Changed

• Update CRuby releases on Windows (CVE-2026-111943) by @​ruby-builder-bot in ruby/setup-ruby#952

Full Changelog: ruby/setup-ruby@v1.331.0...v1.332.0

v1.331.0

What's Changed

• Use ruby's Gem::Version instead of npm's semver to parse rubygems version by @​ntkme in ruby/setup-ruby#946

Full Changelog: ruby/setup-ruby@v1.330.0...v1.331.0

v1.330.0

What's Changed

• Suggest the latest patch release when a version is unavailable by @​CyberNativeAI in ruby/setup-ruby#949

New Contributors

• @​CyberNativeAI made their first contribution in ruby/setup-ruby#949

Full Changelog: ruby/setup-ruby@v1.329.0...v1.330.0

Commits

• b1da480 Update CRuby releases on Windows
• 824c0e2 Use ruby's Gem::Version instead of npm's semver to parse rubygems version
• a89e929 Tweak wording in the README, update link and simplify
• fbbff8d Suggest the latest patch release when a version is unavailable
• See full diff in compare view

Updates PostHog/posthog-sdk-test-harness/.github/workflows/test-sdk-action.yml from 1.15.0 to 1.20.0

Release notes

Sourced from PostHog/posthog-sdk-test-harness/.github/workflows/test-sdk-action.yml's releases.

1.20.0

Minor changes

• 34fd648 Add the feature flag rules v2 experiment rule evaluation corpus and drop the experiment and holdout references from v2 experiment rules (contract package 6.0.0). An experiment links to its rule from the Experiment row, so the rule carries no experiment reference, and every variant assignment by an experiment rule reports experiment_split, whether or not an experiment links to the rule. A holdout belongs to its rule: it holds only a seed and an exclusion percentage, and a holdout result is identified by its rule ID and the holdout reason.

  • Config schema: experiment_id is no longer a rule field and id is no longer a holdout field, so a rule or holdout that carries one is rejected. config.invalid.null_experiment_id is removed; config.valid.experiment_rule_local_holdout, config.invalid.experiment_rule_with_experiment_id and config.invalid.holdout_with_id are added; the other experiment rule fixtures drop experiment_id and holdout.id and keep their expectations.
  • Corpus: corpus/v2_experiment_evaluation.json (81 cases in the ordering, assignment, values, white_box and parser families) and its companion schema.
  • Wire: no config version 2 record carries experiment_id, and no record or event carries a holdout ID. The producer schema forbids experiment_id on v2 records, no longer requires it on a split, and has no holdout_id; the presence rows for experiment rules forbid experiment_id; the event schemas have no $feature_flag_holdout_id, and $experiment_exposure has no $feature_flag_experiment_id. Version 1 records keep experiment_id. The wire templates drop both fields from v2 records and id from the definitions holdout. Removed cases: responses.split_wrong_type_experiment_id, responses.experiment_split_contradicted_has_experiment, responses.rollout_miss_percentage_rollout_wrong_rule_type, responses.rollout_miss_experiment_wrong_rule_type, responses.holdout_missing_holdout_id, responses.v1_forbidden_holdout_id and readers.partial_split_missing_experiment_id. Added cases: responses.experiment_split_flag_without_experiment, responses.holdout_missing_rule_id (the committed presence-layer required failure) and readers.split_extra_experiment_id. responses.json now has 26 valid and 44 invalid cases.
  • Registry: experiment_id leaves fields, and experiment_id and holdout_id leave openfeature_mapping.flag_metadata_keys. — Thanks @​andehen!

1.19.0

Minor changes

• 65b0eb7 Include migrated YAML-parity cases in the SDK acceptance suite while preserving their capability-based selection. — Thanks @​dustinbyrne!

1.18.0

Minor changes

• a6e61f6 Generate the per-field feature flag rules v2 response negatives from the presence matrix instead of committing them. For every row of rules/response_presence.json, the meta-tests build a missing-field case for has_experiment and each required field, a forbidden-field case for each forbidden field, and a wrong condition index case from the row's template, and check each against the same validation layer, keyword and instance path the committed cases declared. A mutation that another matrix row accepts is not a negative. 76 of the 77 committed cases that the generator reproduces exactly (responses.<row>_missing_<field>, responses.<row>_forbidden_<field> and responses.<row>_wrong_condition_index) are removed from fixtures/wire/responses.json; responses.holdout_missing_holdout_id stays so that the committed set keeps a presence-layer required failure. The hand-made invalid cases, all valid cases and all templates stay. responses.json now has 25 valid and 49 invalid cases, so consumers that pin its case counts must update them when they re-vendor. The removal ships in contract package 5.0.0. — Thanks @​andehen!

1.17.0

Minor changes

• a599572 Remove the feature flag rules v2 wire fixture sets that no consumer runs: fixtures/wire/calls.json, call_transport.json, exposures.json, exposure_transport.json, definitions_feed.json, errors.json and warnings.json, together with their manifest.json entries and the meta-tests that only checked them. The definitions.json, responses.json and readers.json fixture sets are unchanged. All schemas stay byte-identical and published as specifications, including the $feature_flag_called context, experiment exposure, management warning, management error and definitions feed schemas; the meta-tests still check each one as a valid JSON Schema 2020-12 document. Fixture sets are added together with the first consumer that runs them. The removal ships in contract package 4.0.0. — Thanks @​andehen!

1.16.0

Minor changes

• 429c266 Use one version for the feature flag rules v2 contract (contract package 3.0.0). manifest.json now holds only contract (name, version, config_version) and artifacts entries with path and kind, plus fixture_id, expected and expected_failure on config fixtures. SHA256SUMS and its checksum script are removed, as are the per-component versions: case_ids, per-artifact version, schema and component in the manifest, fixture_version in the wire fixture files, registry_version in the literal registry and version in the presence matrix. Consumers re-vendoring the contract must stop reading these, take case IDs from the corpus and fixture files, and pin the harness release or commit instead of the checksum index. Schema bytes, schema $ids and all fixture and corpus expectations are unchanged. — Thanks @​andehen!

Changelog

Sourced from PostHog/posthog-sdk-test-harness/.github/workflows/test-sdk-action.yml's changelog.

posthog-sdk-test-harness

1.25.0 — 2026-10-28

Minor changes

• 7c94bda Add capability-gated capture v1 tests that need new adapter features.

  • reported_drops: /state lists the drops the SDK reported. Tests: a drop result and a dropped duplicate copy are reported with capture's details. Local drops (such as an over-ceiling AI event) are not asserted, because each SDK keeps its own surface for them.
  • generated_payloads: /capture_ai pads properties to an exact byte size. Tests: an AI event under the 8 MiB ceiling is sent and one at 9 MiB is not; three 3 MiB AI events go out in at least two requests under 5 MiB each, in order.
  • log_capture: /state lists the SDK's log lines. Test: an over-ceiling AI event is reported as dropped or named in a log line, and no log line includes its content.
  • property_layers: /init takes super_properties and a declarative before_send. Tests: caller properties beat registered ones, and before_send runs last.
  • fail_open: /init accepts an empty or personal (phx_) API key. Tests: such a client sends nothing. — Thanks @​eli-r-ph!

• 7190eab Bind the capture AI v1 Gherkin steps that need no adapter protocol change.

  • the first received event property "<key>" should be absent.
  • capture_ai is called with distinct id "<id>" and event "<name>", and the same for capture.
  • the mock delays every request to "<path>" until released and the delayed AI request is released and succeeds: the v2 mock holds every request to one path until the case releases it, while other paths keep flowing.
  • the analytics batch endpoint should have received "<name>" and the AI form.
  • the mock serves these ordered AI responses:. Both ordered response tables now accept the two-column status | body form, and a body that keys results by * gives every event in the request that result. — Thanks @​eli-r-ph!

1.24.0 — 2026-10-28

Minor changes

• b7eb7a9 Bring the capture_v1 and capture_ai_v1 suites in line with capture v1 as it ships today.

  • New retry tests: SDKs retry 404, 429 and 502 like 408 and the other 5xx statuses.
  • implements_backoff measures the SDK's own waits (100, 200 and 400 ms, jitter down to 0.75x) on a 502 that carries no Retry-After.
  • The mock answers a repeated uuid the way capture does: it keeps the first copy's result and adds duplicates_dropped. A new test checks that only the first copy is resent when capture asks for a retry.
  • Partial-batch tests use capture's warning result instead of limited, which capture never sends. The mock still accepts limited for older feature files.
  • New tests: a caller uuid is sent in lowercase, capture_ai keeps a non-$ai_ event on the AI endpoint, and a failing AI lane does not delay analytics events.
  • Mock responses can target one path, and request-count, batch-count and final-success assertions can filter by path.
  • New adapter capabilities gate tests some SDKs cannot run: event_uuid_override (caller uuids, now also forwarded on /capture), bounded_retries (max_retries_respected), disable_geoip and historical_migration. Adapters that support these must declare them to keep running those tests. — Thanks @​eli-r-ph!

1.23.0 — 2026-10-28

Minor changes

• 1a9528a Add the flags_response_v4 adapter capability. An SDK that declares it must send ?v=4 on remote /flags requests, which asks the server for the v4 flag record. An SDK that does not declare it is still held to ?v=2. Contract tests can now list excludes to skip a test when the adapter declares any of the named capabilities. — Thanks @​andehen!

1.22.0 — 2026-10-26

Minor changes

• 0bc2c7c Slim the feature flag rules v2 experiment rule evaluation corpus (contract package 7.0.0). The corpus drops about 38% of its bytes and loses no expectation: every removed field follows from the fields that remain.

  • corpus/v2_experiment_evaluation.json gains defaults with the flag and context every case shares. A case no longer carries flag, and its context holds only the fields that differ from the default context.
  • Cases no longer carry legacy; consumers derive it from expected.value with the typed value corpus table.
  • hash_evidence entries keep use, prefix, identifier, salt and hash01_binary64_hex. The SHA-1 intermediates move out to corpus/hash_sha1_60_v1.json, which already pins them, and the threshold or boundaries follow from the rule.

... (truncated)

Commits

• aa725c8 chore: Release v1.20.0 [skip ci]
• 34fd648 feat(flags): add the experiment rule evaluation corpus without experiment or ...
• 129fbb4 chore: Release v1.19.0 [skip ci]
• 65b0eb7 feat(v2): unify migrated and canonical SDK acceptance (#88)
• 3957869 chore: Release v1.18.0 [skip ci]
• a6e61f6 test(flags): generate rules v2 presence negatives from the matrix (#86)
• 47178f6 chore(deps): bump the github-actions group across 1 directory with 4 updates ...
• 8ca75c4 chore: Release v1.17.0 [skip ci]
• a599572 refactor(flags): drop rules v2 wire fixture sets that nothing runs (#85)
• 27ae744 chore: Release v1.16.0 [skip ci]
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[github-actions]

posthog-ruby-sync Compliance Report

Date: 2026-10-28T18:33:12.045570+00:00
Duration: 56446ms

⚠️ Some Tests Failed

39/47 tests passed, 8 failed

---

Capture Tests

⚠️ 23/30 tests passed, 7 failed

View Details

Test	Status	Duration
Format Validation.Event Has Required Fields	✅	10ms
Format Validation.Event Has Uuid	✅	6ms
Format Validation.Event Has Lib Properties	✅	6ms
Format Validation.Distinct Id Is String	✅	10ms
Format Validation.Token Is Present	✅	7ms
Format Validation.Custom Properties Preserved	✅	7ms
Format Validation.Event Has Timestamp	✅	8ms
Format Validation.Non Utc Event Timestamp Is Converted To Utc	✅	8ms
Retry Behavior.Retries On 503	✅	5335ms
Retry Behavior.Does Not Retry On 400	❌	7ms
Retry Behavior.Does Not Retry On 401	❌	5ms
Retry Behavior.Respects Retry After Header	✅	8016ms
Retry Behavior.Implements Backoff	❌	333ms
Retry Behavior.Retries On 500	✅	5147ms
Retry Behavior.Retries On 502	✅	5154ms
Retry Behavior.Retries On 504	✅	5148ms
Retry Behavior.Max Retries Respected	❌	693ms
Deduplication.Generates Unique Uuids	✅	21ms
Deduplication.Preserves Uuid On Retry	✅	5146ms
Deduplication.Preserves Uuid And Timestamp On Retry	✅	10374ms
Deduplication.Preserves Uuid And Timestamp On Batch Retry	✅	5152ms
Deduplication.No Duplicate Events In Batch	✅	19ms
Deduplication.Different Events Have Different Uuids	✅	9ms
Compression.Sends Gzip When Enabled	✅	6ms
Batch Format.Uses Proper Batch Structure	✅	7ms
Batch Format.Flush With No Events Sends Nothing	✅	3ms
Batch Format.Multiple Events Batched Together	❌	17ms
Error Handling.Does Not Retry On 403	❌	5ms
Error Handling.Does Not Retry On 413	❌	5ms
Error Handling.Retries On 408	✅	5138ms

Failures

retry_behavior.does_not_retry_on_400

500, message='Internal Server Error', url='http://sdk-adapter:8080/capture'

retry_behavior.does_not_retry_on_401

500, message='Internal Server Error', url='http://sdk-adapter:8080/capture'

retry_behavior.implements_backoff

500, message='Internal Server Error', url='http://sdk-adapter:8080/capture'

retry_behavior.max_retries_respected

500, message='Internal Server Error', url='http://sdk-adapter:8080/capture'

batch_format.multiple_events_batched_together

Expected 1 requests, got 5

error_handling.does_not_retry_on_403

500, message='Internal Server Error', url='http://sdk-adapter:8080/capture'

error_handling.does_not_retry_on_413

500, message='Internal Server Error', url='http://sdk-adapter:8080/capture'

Feature_Flags Tests

⚠️ 16/17 tests passed, 1 failed

View Details

Test	Status	Duration
Request Payload.Request With Person Properties Device Id	✅	10ms
Request Payload.Flags Request Uses V2 Query Param	✅	9ms
Request Payload.Flags Request Hits Flags Path Not Decide	✅	8ms
Request Payload.Flags Request Omits Authorization Header	✅	8ms
Request Payload.Token In Flags Body Matches Init	✅	7ms
Request Payload.Groups Round Trip	✅	6ms
Request Payload.Groups Default To Empty Object	✅	7ms
Request Payload.Disable Geoip False Propagates As Geoip Disable False	✅	6ms
Request Payload.Disable Geoip Omitted Defaults To False	❌	7ms
Request Payload.Flag Keys To Evaluate Contains Only Requested Key	✅	7ms
Request Lifecycle.No Flags Request On Init Alone	✅	2ms
Request Lifecycle.No Flags Request On Normal Capture	✅	6ms
Request Lifecycle.Two Flag Calls Produce Two Remote Requests	✅	10ms
Request Lifecycle.Mock Response Value Is Returned To Caller	✅	7ms
Retry Behavior.Retries Flags On 502	✅	110ms
Retry Behavior.Retries Flags On 504	✅	145ms
Side Effect Events.Get Feature Flag Captures Feature Flag Called Event	✅	8ms

Failures

request_payload.disable_geoip_omitted_defaults_to_false

Field 'geoip_disable' not found in /flags request body at path 'geoip_disable'. Available keys: ['distinct_id', 'groups', 'person_properties', 'group_properties', 'flag_keys_to_evaluate', 'token']

[github-actions]

posthog-ruby-async Compliance Report

Date: 2026-10-28T18:33:46.868378+00:00
Duration: 98287ms

⚠️ Some Tests Failed

46/47 tests passed, 1 failed

---

Capture Tests

✅ 30/30 tests passed

View Details

Test	Status	Duration
Format Validation.Event Has Required Fields	✅	10ms
Format Validation.Event Has Uuid	✅	106ms
Format Validation.Event Has Lib Properties	✅	111ms
Format Validation.Distinct Id Is String	✅	107ms
Format Validation.Token Is Present	✅	107ms
Format Validation.Custom Properties Preserved	✅	108ms
Format Validation.Event Has Timestamp	✅	107ms
Format Validation.Non Utc Event Timestamp Is Converted To Utc	✅	8ms
Retry Behavior.Retries On 503	✅	5412ms
Retry Behavior.Does Not Retry On 400	✅	2110ms
Retry Behavior.Does Not Retry On 401	✅	2109ms
Retry Behavior.Respects Retry After Header	✅	8019ms
Retry Behavior.Implements Backoff	✅	15514ms
Retry Behavior.Retries On 500	✅	5212ms
Retry Behavior.Retries On 502	✅	5212ms
Retry Behavior.Retries On 504	✅	5212ms
Retry Behavior.Max Retries Respected	✅	15619ms
Deduplication.Generates Unique Uuids	✅	112ms
Deduplication.Preserves Uuid On Retry	✅	5212ms
Deduplication.Preserves Uuid And Timestamp On Retry	✅	10417ms
Deduplication.Preserves Uuid And Timestamp On Batch Retry	✅	5214ms
Deduplication.No Duplicate Events In Batch	✅	112ms
Deduplication.Different Events Have Different Uuids	✅	108ms
Compression.Sends Gzip When Enabled	✅	106ms
Batch Format.Uses Proper Batch Structure	✅	107ms
Batch Format.Flush With No Events Sends Nothing	✅	4ms
Batch Format.Multiple Events Batched Together	✅	111ms
Error Handling.Does Not Retry On 403	✅	2107ms
Error Handling.Does Not Retry On 413	✅	2110ms
Error Handling.Retries On 408	✅	5213ms

Feature_Flags Tests

⚠️ 16/17 tests passed, 1 failed

View Details

Test	Status	Duration
Request Payload.Request With Person Properties Device Id	✅	111ms
Request Payload.Flags Request Uses V2 Query Param	✅	108ms
Request Payload.Flags Request Hits Flags Path Not Decide	✅	108ms
Request Payload.Flags Request Omits Authorization Header	✅	107ms
Request Payload.Token In Flags Body Matches Init	✅	107ms
Request Payload.Groups Round Trip	✅	107ms
Request Payload.Groups Default To Empty Object	✅	108ms
Request Payload.Disable Geoip False Propagates As Geoip Disable False	✅	107ms
Request Payload.Disable Geoip Omitted Defaults To False	❌	107ms
Request Payload.Flag Keys To Evaluate Contains Only Requested Key	✅	107ms
Request Lifecycle.No Flags Request On Init Alone	✅	5ms
Request Lifecycle.No Flags Request On Normal Capture	✅	105ms
Request Lifecycle.Two Flag Calls Produce Two Remote Requests	✅	111ms
Request Lifecycle.Mock Response Value Is Returned To Caller	✅	107ms
Retry Behavior.Retries Flags On 502	✅	210ms
Retry Behavior.Retries Flags On 504	✅	254ms
Side Effect Events.Get Feature Flag Captures Feature Flag Called Event	✅	110ms

Failures

request_payload.disable_geoip_omitted_defaults_to_false

Field 'geoip_disable' not found in /flags request body at path 'geoip_disable'. Available keys: ['distinct_id', 'groups', 'person_properties', 'group_properties', 'flag_keys_to_evaluate', 'token']