Skip to content

chore(deps): bump PostHog/posthog-sdk-test-harness/.github/workflows/test-sdk-action.yml from 1.27.0 to 1.29.0 - #987

Merged
turnipdabeets merged 1 commit into
mainfrom
dependabot/github_actions/PostHog/posthog-sdk-test-harness/dot-github/workflows/test-sdk-action.yml-1.29.0
Nov 17, 2026
Merged

turnipdabeets merged 1 commit into
mainfrom
dependabot/github_actions/PostHog/posthog-sdk-test-harness/dot-github/workflows/test-sdk-action.yml-1.29.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 17, 2026

Copy link
Copy Markdown
Contributor

Bumps PostHog/posthog-sdk-test-harness/.github/workflows/test-sdk-action.yml from 1.27.0 to 1.29.0.

Release notes

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

1.29.0

Minor changes

  • 168f46a The v2 Gherkin runner can run the /flags?v=4 read cases of the YAML feature_flags_v4 suite. The specs features remote-flags-v4-legacy-getter.feature (requires flags_response_v4) and remote-flags-v4-legacy-payload.feature (also requires feature_flag_payloads) show each mock response and expected result inline.

    • New steps: the mock serves this /flags response body: (sent byte for byte, with no default fields merged in), get feature flag payload is called with JSON arguments: (route /get_feature_flag_payload), strict the public flag getter should return exactly JSON <value>, payload comparisons as parsed JSON values, and "no value"/"no payload" checks that accept native undefined or JSON null. Every result check also requires that at least one /flags request received the served body, all of them with v=4, so a read that never reached the mock cannot pass. The body serves up to 10 requests.
    • bin/update-flags-v4-features.py --specs <checkout> generates the two features from the feature flag rules v2 contract with posthog_test_harness.flags_v4; --check fails on drift. The release workflow runs the check on the pinned specs.
    • Adds 150 read scenarios; the migrated scope now contains 308 cases and the acceptance scope 339. SDKs without flags_response_v4 select none of the new cases. — Thanks @​andehen!

Patch changes

  • 168f46a The feature_flags_v4 suite and the Gherkin /flags?v=4 payload feature read a reader case's legacy_payload expectation from contract 9.0.0. readers.v1_failed, a failed record that still carries a metadata.payload, now runs in legacy_payload_reads_reader_fixture and in remote-flags-v4-legacy-payload.feature, and expects no payload. The payload feature has 75 scenarios. — Thanks @​andehen!

1.28.0

Minor changes

  • a1a5658 Add the feature_flags_v4 suite, which runs the feature flag rules v2 reader fixtures and value corpus through an SDK by serving mock /flags?v=4 responses built from the contract package.

    • Requires flags_response_v4. Every case in fixtures/wire/readers.json and every successful case of corpus/v2_value_evaluation.json runs as its own test, named <test>[<case id>]: get_feature_flag returns the legacy rendering of the record value, false for a failed or unreadable record, no value for a missing flag, and variant ?? enabled for an older server's record. Each test also requires a successful adapter result and a /flags?v=4 request that read the case's response.
    • With feature_flag_payloads, the payload accessor returns a config version 2 number or object value as the payload, keeps a config version 1 record's metadata.payload, and returns no payload otherwise. A failed record that still carries a payload is not checked, because the contract leaves it open. Payloads compare as parsed JSON values, so key order and number spelling may differ.
    • New optional adapter route POST /get_feature_flag_payload; see ADAPTER_GUIDE.md.
    • Contract tests can set cases: readers, cases: values or cases: reader_payloads to run once per fixture case with {case} substituted.
    • Mock responses can set raw_body to send a body as is, without the endpoint's default fields, so a v4 envelope carries no featureFlags.

    Adapters without flags_response_v4 run no new tests, and no existing test changes. — Thanks @​andehen!

  • e481a63 The v2 Gherkin runner reads @excludes:<capability> tags. It does not select a case when the adapter profile declares any capability that the case excludes. An excluded case that is selected explicitly is not_applicable with rule sdk-capability-excluded-v1. This lets flags_response_v4 replace the ?v=2 query check on /flags with a ?v=4 check in the Gherkin suite, as excludes already does in the YAML suite. — Thanks @​andehen!

  • 425e9cd Accept a config version 2 $feature_flag_called that drops a broken rule pair, following PostHog/sdk-specs#162 (contract package 9.0.0).

    • $feature_flag_rule_id and $feature_flag_rule_type are sent together or not at all, and only with a rule type the reason code allows. An SDK that reads a record with a missing rule ID, a missing rule type or a disallowed rule type sends neither field, and keeps the config version and reason code.
    • schemas/feature_flag_called_context.schema.json now accepts a config version 2 call with no rule, variant or experiment attribution for targeting_match, rollout_miss, experiment_paused and holdout, as it already did for a malformed experiment_split. A half pair and a disallowed rule type, such as targeting_match with experiment, are still rejected, and complete pairs are unchanged.
    • A config version 2 call whose $feature_flag_reason_code is missing or is not a registered reason code is now accepted with no rule, variant or experiment attribution. It keeps config version 2 and the raw code, if any. Registered codes still go through their own branches, so their behaviour is unchanged.
    • bin/update-feature-flag-rules-v2-presence-schemas.py generates these branches: one per reason that names a rule in rules/response_presence.json, and one for a missing or unregistered reason code. Every other branch now requires its reason code, so the branches do not overlap. The malformed-split branch is now generated the same way, with the same shape.
    • The meta-tests check a call without attribution for each of those reasons, for the local flag_disabled, and for a missing or unregistered reason code, the complete call for every matrix row, each half pair and disallowed rule type, and each attribution field added to a call without attribution.
    • A failed record reads as disabled, so the legacy payload accessor yields no payload for it, even when the record carries metadata.payload. Reader cases gain an optional legacy_payload expectation, the decoded JSON value the accessor returns or null for none. readers.v1_at_v4 declares its decoded payload, and readers.v1_failed, a failed config version 1 record that still carries a payload, pins it as null. A meta-test checks every declared legacy_payload and requires one on any failed reader case that carries a payload.
    • The set of accepted calls grows, so this is a major contract version. Consumers that vendor the called-context schema need to copy this release. — Thanks @​andehen!
Changelog

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

posthog-sdk-test-harness

1.31.1 — 2026-11-12

Patch changes

  • a169ec9 Accept null or omitted legacy flag results for explicitly failed records while keeping healthy values and malformed-record checks strict. — Thanks @​marandaneto!

1.31.0 — 2026-11-10

Minor changes

  • 461d176 Expand v2 exception acceptance assertions for normalized inputs, preserved stacks and nested exception metadata. — Thanks @​dustinbyrne!

1.30.0 — 2026-11-10

Minor changes

  • d85e5a1 Rename $feature_flag_variant to $feature_flag_variant_key in the feature flag rules v2 event schemas, following PostHog/sdk-specs#203 (contract package 10.0.0).

    • schemas/experiment_exposure_properties.schema.json requires exactly $feature_flag, $feature_flag_response, $feature_flag_variant_key, $feature_flag_rule_id and locally_evaluated. schemas/feature_flag_called_context.schema.json uses $feature_flag_variant_key in every config version 2 branch. Both closed schemas reject the old name.
    • For config version 2 the variant key and the value are separate: a split can assign the variant control with the value false. $feature_flag_variant read like the value, which $feature_flag_response carries. The new name matches the source field metadata.variant_key and $feature_flag_rule_id. The value, the presence rules and $feature_flag_response do not change.
    • bin/update-feature-flag-rules-v2-presence-schemas.py now names every event property after its metadata field, with no exception for the variant key.
    • The meta-tests check that both schemas reject $feature_flag_variant.
    • A renamed field is a major contract version. Consumers that vendor either event schema need to copy this release. No released SDK sends the old name. — Thanks @​andehen!

1.29.0 — 2026-11-09

Minor changes

  • 168f46a The v2 Gherkin runner can run the /flags?v=4 read cases of the YAML feature_flags_v4 suite. The specs features remote-flags-v4-legacy-getter.feature (requires flags_response_v4) and remote-flags-v4-legacy-payload.feature (also requires feature_flag_payloads) show each mock response and expected result inline.

    • New steps: the mock serves this /flags response body: (sent byte for byte, with no default fields merged in), get feature flag payload is called with JSON arguments: (route /get_feature_flag_payload), strict the public flag getter should return exactly JSON <value>, payload comparisons as parsed JSON values, and "no value"/"no payload" checks that accept native undefined or JSON null. Every result check also requires that at least one /flags request received the served body, all of them with v=4, so a read that never reached the mock cannot pass. The body serves up to 10 requests.
    • bin/update-flags-v4-features.py --specs <checkout> generates the two features from the feature flag rules v2 contract with posthog_test_harness.flags_v4; --check fails on drift. The release workflow runs the check on the pinned specs.
    • Adds 150 read scenarios; the migrated scope now contains 308 cases and the acceptance scope 339. SDKs without flags_response_v4 select none of the new cases. — Thanks @​andehen!

Patch changes

  • 168f46a The feature_flags_v4 suite and the Gherkin /flags?v=4 payload feature read a reader case's legacy_payload expectation from contract 9.0.0. readers.v1_failed, a failed record that still carries a metadata.payload, now runs in legacy_payload_reads_reader_fixture and in remote-flags-v4-legacy-payload.feature, and expects no payload. The payload feature has 75 scenarios. — Thanks @​andehen!

1.28.0 — 2026-11-05

Minor changes

  • a1a5658 Add the feature_flags_v4 suite, which runs the feature flag rules v2 reader fixtures and value corpus through an SDK by serving mock /flags?v=4 responses built from the contract package.

    • Requires flags_response_v4. Every case in fixtures/wire/readers.json and every successful case of corpus/v2_value_evaluation.json runs as its own test, named <test>[<case id>]: get_feature_flag returns the legacy rendering of the record value, false for a failed or unreadable record, no value for a missing flag, and variant ?? enabled for an older server's record. Each test also requires a successful adapter result and a /flags?v=4 request that read the case's response.
    • With feature_flag_payloads, the payload accessor returns a config version 2 number or object value as the payload, keeps a config version 1 record's metadata.payload, and returns no payload otherwise. A failed record that still carries a payload is not checked, because the contract leaves it open. Payloads compare as parsed JSON values, so key order and number spelling may differ.
    • New optional adapter route POST /get_feature_flag_payload; see ADAPTER_GUIDE.md.
    • Contract tests can set cases: readers, cases: values or cases: reader_payloads to run once per fixture case with {case} substituted.

... (truncated)

Commits
  • 69e5b88 chore: Release v1.29.0 [skip ci]
  • 168f46a feat(v2): run the /flags?v=4 read cases in the Gherkin runner (#103)
  • ffa6cc3 chore: Release v1.28.0 [skip ci]
  • a1a5658 feat(flags): run the v4 reader fixtures and value corpus through an SDK (#100)
  • e481a63 feat(v2): skip a Gherkin case when the adapter declares a capability it exclu...
  • 425e9cd feat(flags): accept a flag call that drops a broken rule pair (contract 9.0.0...
  • See full diff in compare view

Dependabot compatibility score

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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

…test-sdk-action.yml

Bumps [PostHog/posthog-sdk-test-harness/.github/workflows/test-sdk-action.yml](https://github.com/posthog/posthog-sdk-test-harness) from 1.27.0 to 1.29.0.
- [Release notes](https://github.com/posthog/posthog-sdk-test-harness/releases)
- [Changelog](https://github.com/PostHog/posthog-sdk-test-harness/blob/main/CHANGELOG.md)
- [Commits](PostHog/posthog-sdk-test-harness@75fb000...69e5b88)

---
updated-dependencies:
- dependency-name: PostHog/posthog-sdk-test-harness/.github/workflows/test-sdk-action.yml
  dependency-version: 1.29.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot requested a review from a team as a code owner November 17, 2026 06:13
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Nov 17, 2026
@github-actions

Copy link
Copy Markdown
Contributor

posthog-android Compliance Report

Date: 2026-11-17 06:20:21 UTC
Duration: 118463ms

✅ All Tests Passed!

46/46 tests passed


Capture Tests

✅ 29/29 tests passed

View Details
Test Status Duration
Format Validation.Event Has Required Fields ✅ 387ms
Format Validation.Event Has Uuid ✅ 31ms
Format Validation.Event Has Lib Properties ✅ 31ms
Format Validation.Distinct Id Is String ✅ 30ms
Format Validation.Token Is Present ✅ 26ms
Format Validation.Custom Properties Preserved ✅ 30ms
Format Validation.Event Has Timestamp ✅ 30ms
Retry Behavior.Retries On 503 ✅ 7030ms
Retry Behavior.Does Not Retry On 400 ✅ 4026ms
Retry Behavior.Does Not Retry On 401 ✅ 4022ms
Retry Behavior.Respects Retry After Header ✅ 7028ms
Retry Behavior.Implements Backoff ✅ 17022ms
Retry Behavior.Retries On 500 ✅ 7017ms
Retry Behavior.Retries On 502 ✅ 7017ms
Retry Behavior.Retries On 504 ✅ 7017ms
Retry Behavior.Max Retries Respected ✅ 17029ms
Deduplication.Generates Unique Uuids ✅ 37ms
Deduplication.Preserves Uuid On Retry ✅ 7012ms
Deduplication.Preserves Uuid And Timestamp On Retry ✅ 12031ms
Deduplication.Preserves Uuid And Timestamp On Batch Retry ✅ 7019ms
Deduplication.No Duplicate Events In Batch ✅ 36ms
Deduplication.Different Events Have Different Uuids ✅ 26ms
Compression.Sends Gzip When Enabled ✅ 19ms
Batch Format.Uses Proper Batch Structure ✅ 19ms
Batch Format.Flush With No Events Sends Nothing ✅ 12ms
Batch Format.Multiple Events Batched Together ✅ 37ms
Error Handling.Does Not Retry On 403 ✅ 4023ms
Error Handling.Does Not Retry On 413 ✅ 4021ms
Error Handling.Retries On 408 ✅ 5029ms

Feature_Flags Tests

✅ 17/17 tests passed

View Details
Test Status Duration
Request Payload.Request With Person Properties Device Id ✅ 36ms
Request Payload.Flags Request Uses V2 Query Param ✅ 27ms
Request Payload.Flags Request Hits Flags Path Not Decide ✅ 24ms
Request Payload.Flags Request Omits Authorization Header ✅ 28ms
Request Payload.Token In Flags Body Matches Init ✅ 23ms
Request Payload.Groups Round Trip ✅ 25ms
Request Payload.Groups Default To Empty Object ✅ 24ms
Request Payload.Disable Geoip False Propagates As Geoip Disable False ✅ 37ms
Request Payload.Disable Geoip Omitted Defaults To False ✅ 24ms
Request Payload.Flag Keys To Evaluate Contains Only Requested Key ✅ 26ms
Request Lifecycle.No Flags Request On Init Alone ✅ 10ms
Request Lifecycle.No Flags Request On Normal Capture ✅ 27ms
Request Lifecycle.Two Flag Calls Produce Two Remote Requests ✅ 40ms
Request Lifecycle.Mock Response Value Is Returned To Caller ✅ 25ms
Retry Behavior.Retries Flags On 502 ✅ 325ms
Retry Behavior.Retries Flags On 504 ✅ 323ms
Side Effect Events.Get Feature Flag Captures Feature Flag Called Event ✅ 26ms

@turnipdabeets
turnipdabeets merged commit 71f9b74 into main Nov 17, 2026
16 checks passed
@turnipdabeets
turnipdabeets deleted the dependabot/github_actions/PostHog/posthog-sdk-test-harness/dot-github/workflows/test-sdk-action.yml-1.29.0 branch November 17, 2026 16:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant