Skip to content

chore(deps): bump the github-actions group with 3 updates - #326

Merged
turnipdabeets merged 1 commit into
mainfrom
dependabot/github_actions/github-actions-1455d200d9
Nov 17, 2026
Merged

turnipdabeets merged 1 commit into
mainfrom
dependabot/github_actions/github-actions-1455d200d9

Conversation

@dependabot

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

Copy link
Copy Markdown
Contributor

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

Updates github/codeql-action/init from 4.39.2 to 4.39.3

Release notes

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

v4.39.3

  • Fixed diff-informed alert filtering incorrectly removing alerts in changed files whose paths contain spaces, special characters, or non-ASCII characters. #4283
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.3 - 04 Nov 2026

  • Fixed diff-informed alert filtering incorrectly removing alerts in changed files whose paths contain spaces, special characters, or non-ASCII characters. #4283

4.39.2 - 03 Nov 2026

  • Update default CodeQL bundle version to 2.27.4. #4284
  • Upcoming breaking change: CodeQL version 2.22.3 and earlier were discontinued on 16 October 2026 alongside GitHub Enterprise Server 3.18, and will be unsupported by the next minor release of the CodeQL Action. Added a deprecation warning for customers using these versions of CodeQL. #4266
  • Starting with macOS 27 and Xcode 27, traced analyses are unsupported. See this blog post for more information. The CodeQL Action will now try to identify if a workflow is about to perform a traced analysis on version 27 or above of macOS or Xcode. If so, the CodeQL Action will emit a corresponding warning that will also be visible on the Tool Status Page. This check will be rolled out following this release of the CodeQL Action. #4221
  • The undocumented TRAP cache cleanup feature that could be enabled using the CODEQL_ACTION_CLEANUP_TRAP_CACHES environment variable has been removed, as announced in the release notes for CodeQL Action 4.35.2. The analyze Action now warns if this environment variable is set. If you used TRAP cache cleanup to limit Actions cache usage, we recommend disabling TRAP caching by passing the trap-caching: false input to the init Action. #4243

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

... (truncated)

Commits
  • 33d7b85 Merge pull request #4299 from github/update-v4.39.3-064910ba2
  • 24393f8 Update changelog for v4.39.3
  • 064910b Merge pull request #4297 from github/mbg/update-glob
  • f532ac5 Update glob to 14.0.3
  • 8cd4dfa Merge pull request #4280 from github/mbg/ci/validate-yaml
  • cea289b Return different exit code when a language is not recognised
  • 7287bb3 Remove exclude entry that's no longer needed
  • 8eb7cdf Use normal .editorconfig pattern
  • 160e547 Merge remote-tracking branch 'origin/main' into mbg/ci/validate-yaml
  • 913e1bb Merge pull request #4283 from github/sam-robson/decode-diff-informed-sarif-uris
  • Additional commits viewable in compare view

Updates github/codeql-action/analyze from 4.39.2 to 4.39.3

Release notes

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

v4.39.3

  • Fixed diff-informed alert filtering incorrectly removing alerts in changed files whose paths contain spaces, special characters, or non-ASCII characters. #4283
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.3 - 04 Nov 2026

  • Fixed diff-informed alert filtering incorrectly removing alerts in changed files whose paths contain spaces, special characters, or non-ASCII characters. #4283

4.39.2 - 03 Nov 2026

  • Update default CodeQL bundle version to 2.27.4. #4284
  • Upcoming breaking change: CodeQL version 2.22.3 and earlier were discontinued on 16 October 2026 alongside GitHub Enterprise Server 3.18, and will be unsupported by the next minor release of the CodeQL Action. Added a deprecation warning for customers using these versions of CodeQL. #4266
  • Starting with macOS 27 and Xcode 27, traced analyses are unsupported. See this blog post for more information. The CodeQL Action will now try to identify if a workflow is about to perform a traced analysis on version 27 or above of macOS or Xcode. If so, the CodeQL Action will emit a corresponding warning that will also be visible on the Tool Status Page. This check will be rolled out following this release of the CodeQL Action. #4221
  • The undocumented TRAP cache cleanup feature that could be enabled using the CODEQL_ACTION_CLEANUP_TRAP_CACHES environment variable has been removed, as announced in the release notes for CodeQL Action 4.35.2. The analyze Action now warns if this environment variable is set. If you used TRAP cache cleanup to limit Actions cache usage, we recommend disabling TRAP caching by passing the trap-caching: false input to the init Action. #4243

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

... (truncated)

Commits
  • 33d7b85 Merge pull request #4299 from github/update-v4.39.3-064910ba2
  • 24393f8 Update changelog for v4.39.3
  • 064910b Merge pull request #4297 from github/mbg/update-glob
  • f532ac5 Update glob to 14.0.3
  • 8cd4dfa Merge pull request #4280 from github/mbg/ci/validate-yaml
  • cea289b Return different exit code when a language is not recognised
  • 7287bb3 Remove exclude entry that's no longer needed
  • 8eb7cdf Use normal .editorconfig pattern
  • 160e547 Merge remote-tracking branch 'origin/main' into mbg/ci/validate-yaml
  • 913e1bb Merge pull request #4283 from github/sam-robson/decode-diff-informed-sarif-uris
  • Additional commits viewable in compare view

Updates PostHog/posthog-sdk-test-harness/.github/workflows/test-sdk-action.yml from 1.27.0 to 1.30.0

Release notes

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

1.30.0

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

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.32.0 — 2026-11-17

Minor changes

  • 683c40e Keep legacy bounded-retry and queued-batching coverage by default while adding positive unbounded-retry recovery and synchronous-delivery profiles. Supply compatible legacy and rich-v2 feature flag fixtures, also readable by v4 old-server compatibility readers.

    Require complete event identity across every recovery attempt and successful final delivery, and reject contradictory bounded/unbounded retry capabilities before acceptance. Poll for recovery with a bounded monotonic deadline and check synchronous delivery after every capture call. Existing first-two-request assertions remain compatible. — Thanks @​marandaneto!

Patch changes

  • 683c40e Respect declared native GeoIP defaults and failed-evaluation no-result mappings in Gherkin remote flag checks. — Thanks @​marandaneto!

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

... (truncated)

Commits
  • 6414114 chore: Release v1.30.0 [skip ci]
  • d85e5a1 fix(release): check the /flags?v=4 features before the version commit, and re...
  • d97715d chore: Release v1.30.0 [skip ci]
  • fb5fbfa feat(flags): rename $feature_flag_variant to $feature_flag_variant_key (contr...
  • 097d69e chore(deps): bump the github-actions group across 1 directory with 2 updates ...
  • 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...
  • 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

Bumps the github-actions group with 3 updates: [github/codeql-action/init](https://github.com/github/codeql-action), [github/codeql-action/analyze](https://github.com/github/codeql-action) and [PostHog/posthog-sdk-test-harness/.github/workflows/test-sdk-action.yml](https://github.com/posthog/posthog-sdk-test-harness).


Updates `github/codeql-action/init` from 4.39.2 to 4.39.3
- [Release notes](https://github.com/github/codeql-action/releases)
- [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md)
- [Commits](github/codeql-action@1fc58d0...33d7b85)

Updates `github/codeql-action/analyze` from 4.39.2 to 4.39.3
- [Release notes](https://github.com/github/codeql-action/releases)
- [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md)
- [Commits](github/codeql-action@1fc58d0...33d7b85)

Updates `PostHog/posthog-sdk-test-harness/.github/workflows/test-sdk-action.yml` from 1.27.0 to 1.30.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...6414114)

---
updated-dependencies:
- dependency-name: github/codeql-action/init
  dependency-version: 4.39.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: github-actions
- dependency-name: github/codeql-action/analyze
  dependency-version: 4.39.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: github-actions
- dependency-name: PostHog/posthog-sdk-test-harness/.github/workflows/test-sdk-action.yml
  dependency-version: 1.30.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: github-actions
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot requested a review from a team as a code owner November 17, 2026 15:55
@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-php-fork_curl Compliance Report

Date: 2026-11-17T15:57:38.474433+00:00
Duration: 116175ms

⚠️ Some Tests Failed

46/47 tests passed, 1 failed


Capture Tests

⚠️ 29/30 tests passed, 1 failed

View Details
Test Status Duration
Format Validation.Event Has Required Fields ✅ 41ms
Format Validation.Event Has Uuid ✅ 532ms
Format Validation.Event Has Lib Properties ✅ 535ms
Format Validation.Distinct Id Is String ✅ 534ms
Format Validation.Token Is Present ✅ 535ms
Format Validation.Custom Properties Preserved ✅ 535ms
Format Validation.Event Has Timestamp ✅ 534ms
Format Validation.Non Utc Event Timestamp Is Converted To Utc ✅ 535ms
Retry Behavior.Retries On 503 ✅ 5861ms
Retry Behavior.Does Not Retry On 400 ✅ 2537ms
Retry Behavior.Does Not Retry On 401 ✅ 2536ms
Retry Behavior.Respects Retry After Header ❌ 6348ms
Retry Behavior.Implements Backoff ✅ 16284ms
Retry Behavior.Retries On 500 ✅ 5656ms
Retry Behavior.Retries On 502 ✅ 5649ms
Retry Behavior.Retries On 504 ✅ 5653ms
Retry Behavior.Max Retries Respected ✅ 16273ms
Deduplication.Generates Unique Uuids ✅ 50ms
Deduplication.Preserves Uuid On Retry ✅ 5651ms
Deduplication.Preserves Uuid And Timestamp On Retry ✅ 10870ms
Deduplication.Preserves Uuid And Timestamp On Batch Retry ✅ 5653ms
Deduplication.No Duplicate Events In Batch ✅ 540ms
Deduplication.Different Events Have Different Uuids ✅ 536ms
Compression.Sends Gzip When Enabled ✅ 535ms
Batch Format.Uses Proper Batch Structure ✅ 533ms
Batch Format.Flush With No Events Sends Nothing ✅ 521ms
Batch Format.Multiple Events Batched Together ✅ 522ms
Error Handling.Does Not Retry On 403 ✅ 2535ms
Error Handling.Does Not Retry On 413 ✅ 2539ms
Error Handling.Retries On 408 ✅ 5651ms

Failures

retry_behavior.respects_retry_after_header

Retry delay too short: 810ms < 2500ms

Feature_Flags Tests

✅ 17/17 tests passed

View Details
Test Status Duration
Request Payload.Request With Person Properties Device Id ✅ 526ms
Request Payload.Flags Request Uses V2 Query Param ✅ 524ms
Request Payload.Flags Request Hits Flags Path Not Decide ✅ 525ms
Request Payload.Flags Request Omits Authorization Header ✅ 525ms
Request Payload.Token In Flags Body Matches Init ✅ 525ms
Request Payload.Groups Round Trip ✅ 525ms
Request Payload.Groups Default To Empty Object ✅ 525ms
Request Payload.Disable Geoip False Propagates As Geoip Disable False ✅ 524ms
Request Payload.Disable Geoip Omitted Defaults To False ✅ 525ms
Request Payload.Flag Keys To Evaluate Contains Only Requested Key ✅ 525ms
Request Lifecycle.No Flags Request On Init Alone ✅ 519ms
Request Lifecycle.No Flags Request On Normal Capture ✅ 518ms
Request Lifecycle.Two Flag Calls Produce Two Remote Requests ✅ 530ms
Request Lifecycle.Mock Response Value Is Returned To Caller ✅ 527ms
Retry Behavior.Retries Flags On 502 ✅ 628ms
Retry Behavior.Retries Flags On 504 ✅ 627ms
Side Effect Events.Get Feature Flag Captures Feature Flag Called Event ✅ 536ms

@github-actions

Copy link
Copy Markdown
Contributor

posthog-php-lib_curl Compliance Report

Date: 2026-11-17T15:58:12.930093+00:00
Duration: 116390ms

⚠️ Some Tests Failed

46/47 tests passed, 1 failed


Capture Tests

⚠️ 29/30 tests passed, 1 failed

View Details
Test Status Duration
Format Validation.Event Has Required Fields ✅ 24ms
Format Validation.Event Has Uuid ✅ 520ms
Format Validation.Event Has Lib Properties ✅ 521ms
Format Validation.Distinct Id Is String ✅ 521ms
Format Validation.Token Is Present ✅ 521ms
Format Validation.Custom Properties Preserved ✅ 520ms
Format Validation.Event Has Timestamp ✅ 521ms
Format Validation.Non Utc Event Timestamp Is Converted To Utc ✅ 521ms
Retry Behavior.Retries On 503 ✅ 5831ms
Retry Behavior.Does Not Retry On 400 ✅ 2523ms
Retry Behavior.Does Not Retry On 401 ✅ 2523ms
Retry Behavior.Respects Retry After Header ❌ 6331ms
Retry Behavior.Implements Backoff ✅ 16245ms
Retry Behavior.Retries On 500 ✅ 5631ms
Retry Behavior.Retries On 502 ✅ 5628ms
Retry Behavior.Retries On 504 ✅ 5629ms
Retry Behavior.Max Retries Respected ✅ 17047ms
Deduplication.Generates Unique Uuids ✅ 226ms
Deduplication.Preserves Uuid On Retry ✅ 5629ms
Deduplication.Preserves Uuid And Timestamp On Retry ✅ 10838ms
Deduplication.Preserves Uuid And Timestamp On Batch Retry ✅ 5631ms
Deduplication.No Duplicate Events In Batch ✅ 526ms
Deduplication.Different Events Have Different Uuids ✅ 522ms
Compression.Sends Gzip When Enabled ✅ 522ms
Batch Format.Uses Proper Batch Structure ✅ 521ms
Batch Format.Flush With No Events Sends Nothing ✅ 517ms
Batch Format.Multiple Events Batched Together ✅ 511ms
Error Handling.Does Not Retry On 403 ✅ 2522ms
Error Handling.Does Not Retry On 413 ✅ 2524ms
Error Handling.Retries On 408 ✅ 5629ms

Failures

retry_behavior.respects_retry_after_header

Retry delay too short: 804ms < 2500ms

Feature_Flags Tests

✅ 17/17 tests passed

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

@github-actions

Copy link
Copy Markdown
Contributor

posthog-php-socket Compliance Report

Date: 2026-11-17T15:58:13.528208+00:00
Duration: 115576ms

⚠️ Some Tests Failed

46/47 tests passed, 1 failed


Capture Tests

⚠️ 29/30 tests passed, 1 failed

View Details
Test Status Duration
Format Validation.Event Has Required Fields ✅ 27ms
Format Validation.Event Has Uuid ✅ 523ms
Format Validation.Event Has Lib Properties ✅ 524ms
Format Validation.Distinct Id Is String ✅ 525ms
Format Validation.Token Is Present ✅ 525ms
Format Validation.Custom Properties Preserved ✅ 525ms
Format Validation.Event Has Timestamp ✅ 523ms
Format Validation.Non Utc Event Timestamp Is Converted To Utc ✅ 525ms
Retry Behavior.Retries On 503 ✅ 5831ms
Retry Behavior.Does Not Retry On 400 ✅ 2527ms
Retry Behavior.Does Not Retry On 401 ✅ 2528ms
Retry Behavior.Respects Retry After Header ❌ 6330ms
Retry Behavior.Implements Backoff ✅ 16248ms
Retry Behavior.Retries On 500 ✅ 5633ms
Retry Behavior.Retries On 502 ✅ 5630ms
Retry Behavior.Retries On 504 ✅ 5633ms
Retry Behavior.Max Retries Respected ✅ 16250ms
Deduplication.Generates Unique Uuids ✅ 532ms
Deduplication.Preserves Uuid On Retry ✅ 5632ms
Deduplication.Preserves Uuid And Timestamp On Retry ✅ 10834ms
Deduplication.Preserves Uuid And Timestamp On Batch Retry ✅ 5139ms
Deduplication.No Duplicate Events In Batch ✅ 531ms
Deduplication.Different Events Have Different Uuids ✅ 526ms
Compression.Sends Gzip When Enabled ✅ 524ms
Batch Format.Uses Proper Batch Structure ✅ 524ms
Batch Format.Flush With No Events Sends Nothing ✅ 520ms
Batch Format.Multiple Events Batched Together ✅ 513ms
Error Handling.Does Not Retry On 403 ✅ 2527ms
Error Handling.Does Not Retry On 413 ✅ 2526ms
Error Handling.Retries On 408 ✅ 5632ms

Failures

retry_behavior.respects_retry_after_header

Retry delay too short: 803ms < 2500ms

Feature_Flags Tests

✅ 17/17 tests passed

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

@turnipdabeets
turnipdabeets merged commit 6ace1f9 into main Nov 17, 2026
27 checks passed
@turnipdabeets
turnipdabeets deleted the dependabot/github_actions/github-actions-1455d200d9 branch November 17, 2026 18:22
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