[dependabot]

Bumps the github-actions group with 5 updates:

Package	From	To
github/codeql-action/init	4.38.3	4.39.0
github/codeql-action/analyze	4.38.3	4.39.0
actions/create-github-app-token	3.2.0	3.3.0
pnpm/setup	3.0.0	3.1.1
PostHog/posthog-sdk-test-harness/.github/workflows/test-sdk-action.yml	1.14.0	1.15.0

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

Release notes

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

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

• 6f2ac81 Merge pull request #4239 from github/update-v4.39.0-d63383a73
• eb1c428 Trigger workflows
• 4443333 Update changelog for v4.39.0
• d63383a Merge pull request #4233 from github/mbg/start-proxy/report-version
• 8dec0b9 Rename path to result in tests
• 4eabea6 Merge remote-tracking branch 'origin/main' into mbg/start-proxy/report-version
• 57938b8 Merge pull request #4201 from github/mario-campos/automate-changenotes-assemble
• ee07b50 Merge pull request #4236 from github/mbg/add-missing-changenotes
• a897ed5 Add change note for #4206
• c8bd019 Add change note for #4198
• Additional commits viewable in compare view

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

Release notes

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

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

• 6f2ac81 Merge pull request #4239 from github/update-v4.39.0-d63383a73
• eb1c428 Trigger workflows
• 4443333 Update changelog for v4.39.0
• d63383a Merge pull request #4233 from github/mbg/start-proxy/report-version
• 8dec0b9 Rename path to result in tests
• 4eabea6 Merge remote-tracking branch 'origin/main' into mbg/start-proxy/report-version
• 57938b8 Merge pull request #4201 from github/mario-campos/automate-changenotes-assemble
• ee07b50 Merge pull request #4236 from github/mbg/add-missing-changenotes
• a897ed5 Add change note for #4206
• c8bd019 Add change note for #4198
• Additional commits viewable in compare view

Updates actions/create-github-app-token from 3.2.0 to 3.3.0

Release notes

Sourced from actions/create-github-app-token's releases.

v3.3.0

3.3.0 (2026-10-12)

Features

• update permission inputs (#399) (a47236f)

Bug Fixes

• deps: bump nested undici from 6.24.0 to 6.29.0 (#403) (12461a3)
• deps: bump the production-dependencies group across 1 directory with 3 updates (#395) (a69c19d)

Changelog

Sourced from actions/create-github-app-token's changelog.

Changelog

3.3.0 (2026-10-12)

Features

• update permission inputs (#399) (a47236f)

Bug Fixes

• deps: bump nested undici from 6.24.0 to 6.29.0 (#403) (12461a3)
• deps: bump the production-dependencies group across 1 directory with 3 updates (#395) (a69c19d)

3.2.0 (2026-05-12)

Features

• add support for enterprise-level GitHub Apps (#263) (952a2a7)
• support full repository names in repositories input (#372) (85eb8dd)

Bug Fixes

• deps: bump @​actions/core from 3.0.0 to 3.0.1 in the production-dependencies group (#364) (43e5c34)
• validate private-key input (#376) (f24bbd8)

Commits

• 64ab729 chore(main): release 3.3.0 (#402)
• f3a828e ci: create signed dist commits in release workflow (#404)
• 655017f docs: clarify when owner grants access to all repositories (#378)
• 12461a3 fix(deps): bump nested undici from 6.24.0 to 6.29.0 (#403)
• a47236f feat: update permission inputs (#399)
• a69c19d fix(deps): bump the production-dependencies group across 1 directory with 3 u...
• d5cb7ae build(deps): bump actions/checkout from 6 to 7 (#384)
• 575da86 build(deps): bump stefanzweifel/git-auto-commit-action from 7.1.0 to 7.2.0 in...
• e85f677 test: omit stack traces from snapshots (#401)
• 9419396 build(deps-dev): bump c8 from 11.0.0 to 12.0.0 (#400)
• Additional commits viewable in compare view

Updates pnpm/setup from 3.0.0 to 3.1.1

Release notes

Sourced from pnpm/setup's releases.

v3.1.1

What's Changed

• chore: update dependencies by @​github-actions[bot] in pnpm/setup#54

Full Changelog: pnpm/setup@v3.1.0...v3.1.1

v3.1.0

What's Changed

• feat: add save-cache and skip saving an unchanged store by @​EhabY in pnpm/setup#65
• fix: exit once the action settles and time out the runtime version listing by @​okisdev in pnpm/setup#70
• fix: prefer locked pnpm by @​MindTooth in pnpm/setup#72
• feat: add a registry input for downloading pnpm from a mirror by @​yoo-mat in pnpm/setup#74

New Contributors

• @​EhabY made their first contribution in pnpm/setup#65
• @​okisdev made their first contribution in pnpm/setup#70
• @​MindTooth made their first contribution in pnpm/setup#72
• @​yoo-mat made their first contribution in pnpm/setup#74

Full Changelog: pnpm/setup@v3.0.0...v3.1.0

Commits

• a088197 chore: update dependencies (#54)
• f618924 feat: add a registry input for downloading pnpm from a mirror (#74)
• 4fe0be1 fix: prefer locked pnpm (#72)
• 881f070 fix: exit once the action settles and time out the runtime version listing (#70)
• 0da5501 feat: add save-cache and skip saving an unchanged store (#65)
• See full diff in compare view

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

Release notes

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

1.15.0

Minor changes

• 80bf272 Add public group-identify delivery bindings and acceptance coverage. — Thanks @​dustinbyrne!
• 683d871 Add public capture-exception delivery bindings and structured exception assertions. — Thanks @​dustinbyrne!
• 2c5d2c9 Add request-local feature-flag snapshot reads, public result and filter assertions, and flushed exposure/context coverage. — Thanks @​dustinbyrne!

Changelog

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

posthog-sdk-test-harness

1.20.0 — 2026-10-21

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 — 2026-10-20

Minor changes

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

1.18.0 — 2026-10-20

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 — 2026-10-19

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 — 2026-10-19

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!

1.15.0 — 2026-10-11

Minor changes

• 80bf272 Add public group-identify delivery bindings and acceptance coverage. — Thanks @​dustinbyrne!
• 683d871 Add public capture-exception delivery bindings and structured exception assertions. — Thanks @​dustinbyrne!
• 2c5d2c9 Add request-local feature-flag snapshot reads, public result and filter assertions, and flushed exposure/context coverage. — Thanks @​dustinbyrne!

1.14.0 — 2026-10-08

Minor changes

• 41ee102 Add a generated Gherkin step reference and the posthog-test-harness-v2 steps command to inspect registered phrases, argument kinds, routes, and fixture requirements. — Thanks @​dustinbyrne!

... (truncated)

Commits

• 64ffa6a chore: Release v1.15.0 [skip ci]
• 2c5d2c9 feat: assert request-local feature flag snapshot reads (#77)
• 683d871 feat(v2): observe public capture-exception delivery (#75)
• 80bf272 feat(v2): bind public group-identify delivery (#73)
• See full diff 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-dotnet Compliance Report

Date: 2026-10-23T16:14:37.996833+00:00
Duration: 125006ms

✅ All Tests Passed!

47/47 tests passed

---

Capture Tests

✅ 30/30 tests passed

View Details

Test	Status	Duration
Format Validation.Event Has Required Fields	✅	257ms
Format Validation.Event Has Uuid	✅	128ms
Format Validation.Event Has Lib Properties	✅	110ms
Format Validation.Distinct Id Is String	✅	114ms
Format Validation.Token Is Present	✅	111ms
Format Validation.Custom Properties Preserved	✅	118ms
Format Validation.Event Has Timestamp	✅	110ms
Format Validation.Non Utc Event Timestamp Is Converted To Utc	✅	121ms
Retry Behavior.Retries On 503	✅	8122ms
Retry Behavior.Does Not Retry On 400	✅	2118ms
Retry Behavior.Does Not Retry On 401	✅	2113ms
Retry Behavior.Respects Retry After Header	✅	8119ms
Retry Behavior.Implements Backoff	✅	22124ms
Retry Behavior.Retries On 500	✅	6118ms
Retry Behavior.Retries On 502	✅	6119ms
Retry Behavior.Retries On 504	✅	6119ms
Retry Behavior.Max Retries Respected	✅	22133ms
Deduplication.Generates Unique Uuids	✅	116ms
Deduplication.Preserves Uuid On Retry	✅	6118ms
Deduplication.Preserves Uuid And Timestamp On Retry	✅	13129ms
Deduplication.Preserves Uuid And Timestamp On Batch Retry	✅	6123ms
Deduplication.No Duplicate Events In Batch	✅	116ms
Deduplication.Different Events Have Different Uuids	✅	112ms
Compression.Sends Gzip When Enabled	✅	109ms
Batch Format.Uses Proper Batch Structure	✅	110ms
Batch Format.Flush With No Events Sends Nothing	✅	106ms
Batch Format.Multiple Events Batched Together	✅	117ms
Error Handling.Does Not Retry On 403	✅	2112ms
Error Handling.Does Not Retry On 413	✅	2113ms
Error Handling.Retries On 408	✅	6118ms

Feature_Flags Tests

✅ 17/17 tests passed

View Details

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