Skip to content

chore(deps): bump the github-actions group with 6 updates - #5750

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/github-actions-1230f44feb
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/github-actions-1230f44feb

Conversation

@dependabot

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

Copy link
Copy Markdown
Contributor

Bumps the github-actions group with 6 updates:

Package From To
github/codeql-action/init 4.39.2 4.39.3
github/codeql-action/analyze 4.39.2 4.39.3
amannn/action-semantic-pull-request 6.1.1 6.1.2
peter-evans/create-pull-request 8.1.1 8.1.2
actions/setup-java 6.1.0 6.2.0
PostHog/posthog-sdk-test-harness/.github/workflows/test-sdk-action.yml 1.27.0 1.29.0

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 amannn/action-semantic-pull-request from 6.1.1 to 6.1.2

Release notes

Sourced from amannn/action-semantic-pull-request's releases.

v6.1.2

6.1.2 (2026-11-05)

Bug Fixes

  • Release accumulated dependency updates (closes #321) (fc7da0c)
Changelog

Sourced from amannn/action-semantic-pull-request's changelog.

Changelog

6.1.2 (2026-11-05)

Bug Fixes

  • Release accumulated dependency updates (closes #321) (fc7da0c)

6.1.1 (2025-08-22)

Bug Fixes

  • Parse headerPatternCorrespondence properly (#295) (800da4c)

6.1.0 (2025-08-19)

Features

Bug Fixes

  • Remove trailing whitespace from "unknown release type" error message (#291) (afa4edb)

6.0.1 (2025-08-13)

Bug Fixes

6.0.0 (2025-08-13)

⚠ BREAKING CHANGES

  • Upgrade action to use Node.js 24 and ESM (#287)

Features

  • Upgrade action to use Node.js 24 and ESM (#287) (bc0c9a7)

5.5.3 (2024-06-28)

Bug Fixes

5.5.2 (2024-04-24)

... (truncated)

Commits
  • 2252a14 chore: Release 6.1.2 [skip ci]
  • af97545 ci: pin conventional-changelog-conventionalcommits to v9 (#323)
  • fc7da0c fix: Release accumulated dependency updates (closes #321)
  • 4e8becf ci: bump the npm-packages group with 10 updates (#319)
  • b3fa6ed ci: bump actions/setup-node from 6 to 7 in the github-action-workflows group ...
  • 2c9480c chore: bump the npm-packages group with 12 updates (#315)
  • 58e675f ci: bump the github-action-workflows group with 2 updates (#313)
  • 45b9ed7 chore: bump the npm-packages group with 12 updates (#308)
  • 9d28649 ci: Bump the github-action-workflows group with 2 updates (#309)
  • ac7e3fc docs: Fix snippet (#306)
  • Additional commits viewable in compare view

Updates peter-evans/create-pull-request from 8.1.1 to 8.1.2

Release notes

Sourced from peter-evans/create-pull-request's releases.

Create Pull Request v8.1.2

What's Changed

New Contributors

Full Changelog: peter-evans/create-pull-request@v8.1.1...v8.1.2

Commits
  • 15733db fix: submodule deletion with sign-commits (#4473)
  • 3afad46 build(deps-dev): bump the npm group with 4 updates (#4509)
  • aee70be build(deps): bump the github-actions group with 3 updates (#4510)
  • 86c87cf build(deps-dev): bump undici from 6.29.0 to 6.29.1 (#4504)
  • bd09a93 build(deps-dev): bump handlebars from 4.7.9 to 4.7.10 (#4494)
  • 59910dc build(deps): bump brace-expansion (#4486)
  • 753b437 build(deps-dev): bump the npm group with 4 updates (#4483)
  • abadea5 build(deps-dev): bump undici from 6.28.0 to 6.29.0 (#4478)
  • 11e8dc7 build(deps-dev): bump js-yaml from 4.2.0 to 5.4.2 (#4468)
  • c9f8b51 build(deps-dev): bump browserslist from 4.28.4 to 4.28.8 (#4462)
  • Additional commits viewable in compare view

Updates actions/setup-java from 6.1.0 to 6.2.0

Release notes

Sourced from actions/setup-java's releases.

v6.2.0

What's Changed

New Contributors

Full Changelog: actions/setup-java@v6.1.0...v6.2.0

Commits

Updates 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 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 6 updates:

| Package | From | To |
| --- | --- | --- |
| [github/codeql-action/init](https://github.com/github/codeql-action) | `4.39.2` | `4.39.3` |
| [github/codeql-action/analyze](https://github.com/github/codeql-action) | `4.39.2` | `4.39.3` |
| [amannn/action-semantic-pull-request](https://github.com/amannn/action-semantic-pull-request) | `6.1.1` | `6.1.2` |
| [peter-evans/create-pull-request](https://github.com/peter-evans/create-pull-request) | `8.1.1` | `8.1.2` |
| [actions/setup-java](https://github.com/actions/setup-java) | `6.1.0` | `6.2.0` |
| [PostHog/posthog-sdk-test-harness/.github/workflows/test-sdk-action.yml](https://github.com/posthog/posthog-sdk-test-harness) | `1.27.0` | `1.29.0` |


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 `amannn/action-semantic-pull-request` from 6.1.1 to 6.1.2
- [Release notes](https://github.com/amannn/action-semantic-pull-request/releases)
- [Changelog](https://github.com/amannn/action-semantic-pull-request/blob/main/CHANGELOG.md)
- [Commits](amannn/action-semantic-pull-request@48f2562...2252a14)

Updates `peter-evans/create-pull-request` from 8.1.1 to 8.1.2
- [Release notes](https://github.com/peter-evans/create-pull-request/releases)
- [Commits](peter-evans/create-pull-request@5f6978f...15733db)

Updates `actions/setup-java` from 6.1.0 to 6.2.0
- [Release notes](https://github.com/actions/setup-java/releases)
- [Commits](actions/setup-java@b843ebf...77dd5b2)

Updates `PostHog/posthog-sdk-test-harness/.github/workflows/test-sdk-action.yml` 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: 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: amannn/action-semantic-pull-request
  dependency-version: 6.1.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: github-actions
- dependency-name: peter-evans/create-pull-request
  dependency-version: 8.1.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: github-actions
- dependency-name: actions/setup-java
  dependency-version: 6.2.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: github-actions
- 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
  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 16, 2026 10:12
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Nov 16, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Coherence

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

What is Coherence?

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

This check read 44 parts of the code and 7 rules.

Tip

Nothing to fix.

@github-actions

Copy link
Copy Markdown
Contributor

posthog-js Compliance Report

Date: 2026-11-16 10:20:14 UTC
Duration: 88599ms

✅ All Tests Passed!

26/26 tests passed


Capture Tests

✅ 26/26 tests passed

View Details
Test Status Duration
Format Validation.Event Has Required Fields Client ✅ 93ms
Format Validation.Event Has Uuid ✅ 14ms
Format Validation.Event Has Lib Properties ✅ 10ms
Format Validation.Distinct Id Is String Client ✅ 11ms
Format Validation.Token Is Present Client ✅ 11ms
Format Validation.Custom Properties Preserved ✅ 11ms
Format Validation.Event Has Timestamp ✅ 12ms
Retry Behavior.Retries On 503 ✅ 5018ms
Retry Behavior.Does Not Retry On 400 ✅ 2013ms
Retry Behavior.Does Not Retry On 401 ✅ 2011ms
Retry Behavior.Respects Retry After Header ✅ 5012ms
Retry Behavior.Implements Backoff ✅ 15026ms
Retry Behavior.Retries On 500 ✅ 5015ms
Retry Behavior.Retries On 502 ✅ 5010ms
Retry Behavior.Retries On 504 ✅ 5014ms
Retry Behavior.Max Retries Respected ✅ 15025ms
Deduplication.Generates Unique Uuids ✅ 29ms
Deduplication.Preserves Uuid On Retry ✅ 5009ms
Deduplication.Preserves Uuid And Timestamp On Retry ✅ 10020ms
Deduplication.Preserves Uuid And Timestamp On Batch Retry ✅ 5018ms
Deduplication.No Duplicate Events In Batch ✅ 17ms
Deduplication.Different Events Have Different Uuids ✅ 12ms
Batch Format.Flush With No Events Sends Nothing ✅ 6ms
Error Handling.Does Not Retry On 403 ✅ 2011ms
Error Handling.Does Not Retry On 413 ✅ 2012ms
Error Handling.Retries On 408 ✅ 5014ms

@github-actions

Copy link
Copy Markdown
Contributor

SDK performance: posthog-node

3 changes worth reviewing: 3 observed regressions.

Flags require at least a 5% change in the median and all six pairs agreeing on direction. This is a noise filter, not proof of a performance change or a CI gate.

Test Measurement Before PR With PR Change
Capture and deliver events (32-byte payload, steady) Allocated memory per operation (estimated) 9.85 KiB/op 10.7 KiB/op 8.6% more memory
Evaluate a regex-filtered flag Process CPU time per operation 52.02 µs/op 55.3 µs/op 6.3% more time
Evaluate a regex-filtered flag Time per operation 49.28 µs/op 52.36 µs/op 6.2% more time
View all results
Test Measurement Before PR With PR Change Assessment
Capture and deliver events (32-byte payload, burst)
Shard: capture
Allocations per operation — — — unavailable; base:​ unsupported; head:​ unsupported; base:​ V8 samples do not expose total allocation count; sample count is not object count.​; head:​ V8 samples do not expose total allocation count; sample count is not object count.​
Capture and deliver events (4,096-byte payload, burst)
Shard: capture
Allocations per operation — — — unavailable; base:​ unsupported; head:​ unsupported; base:​ V8 samples do not expose total allocation count; sample count is not object count.​; head:​ V8 samples do not expose total allocation count; sample count is not object count.​
Capture and deliver events (32-byte payload, steady)
Shard: capture
Allocations per operation — — — unavailable; base:​ unsupported; head:​ unsupported; base:​ V8 samples do not expose total allocation count; sample count is not object count.​; head:​ V8 samples do not expose total allocation count; sample count is not object count.​
Capture and deliver events (4,096-byte payload, steady)
Shard: capture
Allocations per operation — — — unavailable; base:​ unsupported; head:​ unsupported; base:​ V8 samples do not expose total allocation count; sample count is not object count.​; head:​ V8 samples do not expose total allocation count; sample count is not object count.​
Queue an event (32-byte payload)
Shard: capture
Allocations per operation — — — unavailable; base:​ unsupported; head:​ unsupported; base:​ V8 samples do not expose total allocation count; sample count is not object count.​; head:​ V8 samples do not expose total allocation count; sample count is not object count.​
Queue an event (4,096-byte payload)
Shard: capture
Allocations per operation — — — unavailable; base:​ unsupported; head:​ unsupported; base:​ V8 samples do not expose total allocation count; sample count is not object count.​; head:​ V8 samples do not expose total allocation count; sample count is not object count.​
Evaluate all 10 flags
Shard: flags-scaling
Allocations per operation — — — unavailable; base:​ unsupported; head:​ unsupported; base:​ V8 samples do not expose total allocation count; sample count is not object count.​; head:​ V8 samples do not expose total allocation count; sample count is not object count.​
Evaluate all 100 flags
Shard: flags-scaling
Allocations per operation — — — unavailable; base:​ unsupported; head:​ unsupported; base:​ V8 samples do not expose total allocation count; sample count is not object count.​; head:​ V8 samples do not expose total allocation count; sample count is not object count.​
Evaluate all 1,000 flags
Shard: flags-scaling
Allocations per operation — — — unavailable; base:​ unsupported; head:​ unsupported; base:​ V8 samples do not expose total allocation count; sample count is not object count.​; head:​ V8 samples do not expose total allocation count; sample count is not object count.​
Evaluate one boolean flag
Shard: flags-single
Allocations per operation — — — unavailable; base:​ unsupported; head:​ unsupported; base:​ V8 samples do not expose total allocation count; sample count is not object count.​; head:​ V8 samples do not expose total allocation count; sample count is not object count.​
Evaluate a cohort-filtered flag
Shard: flags-single
Allocations per operation — — — unavailable; base:​ unsupported; head:​ unsupported; base:​ V8 samples do not expose total allocation count; sample count is not object count.​; head:​ V8 samples do not expose total allocation count; sample count is not object count.​
Evaluate a flag (early match)
Shard: flags-single
Allocations per operation — — — unavailable; base:​ unsupported; head:​ unsupported; base:​ V8 samples do not expose total allocation count; sample count is not object count.​; head:​ V8 samples do not expose total allocation count; sample count is not object count.​
Evaluate a flag (late match)
Shard: flags-single
Allocations per operation — — — unavailable; base:​ unsupported; head:​ unsupported; base:​ V8 samples do not expose total allocation count; sample count is not object count.​; head:​ V8 samples do not expose total allocation count; sample count is not object count.​
Evaluate a flag (no match)
Shard: flags-single
Allocations per operation — — — unavailable; base:​ unsupported; head:​ unsupported; base:​ V8 samples do not expose total allocation count; sample count is not object count.​; head:​ V8 samples do not expose total allocation count; sample count is not object count.​
Evaluate a property-filtered flag
Shard: flags-single
Allocations per operation — — — unavailable; base:​ unsupported; head:​ unsupported; base:​ V8 samples do not expose total allocation count; sample count is not object count.​; head:​ V8 samples do not expose total allocation count; sample count is not object count.​
Evaluate a regex-filtered flag
Shard: flags-single
Allocations per operation — — — unavailable; base:​ unsupported; head:​ unsupported; base:​ V8 samples do not expose total allocation count; sample count is not object count.​; head:​ V8 samples do not expose total allocation count; sample count is not object count.​
Evaluate a rollout flag
Shard: flags-single
Allocations per operation — — — unavailable; base:​ unsupported; head:​ unsupported; base:​ V8 samples do not expose total allocation count; sample count is not object count.​; head:​ V8 samples do not expose total allocation count; sample count is not object count.​
Evaluate a multivariate flag
Shard: flags-single
Allocations per operation — — — unavailable; base:​ unsupported; head:​ unsupported; base:​ V8 samples do not expose total allocation count; sample count is not object count.​; head:​ V8 samples do not expose total allocation count; sample count is not object count.​
Capture and deliver events (32-byte payload, burst)
Shard: capture
Allocated memory per operation (estimated) 9.7 KiB/op 10.27 KiB/op 5.9% more memory Not flagged
Capture and deliver events (32-byte payload, burst)
Shard: capture
Time per operation 15.05 µs/op 14.98 µs/op 0.4% less time Not flagged
Capture and deliver events (32-byte payload, burst)
Shard: capture
Idle process memory (RSS) 102.65 MiB 102.59 MiB <0.1% less memory Not flagged
Capture and deliver events (32-byte payload, burst)
Shard: capture
Observed peak process memory (RSS) 106.39 MiB 106.66 MiB 0.2% more memory Not flagged
Capture and deliver events (32-byte payload, burst)
Shard: capture
Managed heap after settling 10.15 MiB 10.15 MiB <0.1% less memory Not flagged
Capture and deliver events (32-byte payload, burst)
Shard: capture
Process memory after settling (RSS) 106.06 MiB 106.35 MiB 0.3% more memory Not flagged
Capture and deliver events (32-byte payload, burst)
Shard: capture
Process CPU time per operation 28.16 µs/op 27.94 µs/op 0.8% less time Not flagged
Capture and deliver events (32-byte payload, burst)
Shard: capture
Lifetime peak process memory (RSS) 106.61 MiB 106.88 MiB 0.3% more memory Not flagged
Capture and deliver events (4,096-byte payload, burst)
Shard: capture
Allocated memory per operation (estimated) 17.81 KiB/op 18.2 KiB/op 2.2% more memory Not flagged
Capture and deliver events (4,096-byte payload, burst)
Shard: capture
Time per operation 25.69 µs/op 25.32 µs/op 1.4% less time Not flagged
Capture and deliver events (4,096-byte payload, burst)
Shard: capture
Idle process memory (RSS) 102.53 MiB 102.58 MiB <0.1% more memory Not flagged
Capture and deliver events (4,096-byte payload, burst)
Shard: capture
Observed peak process memory (RSS) 113.95 MiB 114.02 MiB <0.1% more memory Not flagged
Capture and deliver events (4,096-byte payload, burst)
Shard: capture
Managed heap after settling 10.16 MiB 10.16 MiB <0.1% less memory Not flagged
Capture and deliver events (4,096-byte payload, burst)
Shard: capture
Process memory after settling (RSS) 109.89 MiB 109.88 MiB <0.1% less memory Not flagged
Capture and deliver events (4,096-byte payload, burst)
Shard: capture
Process CPU time per operation 39.3 µs/op 38.52 µs/op 2% less time Not flagged
Capture and deliver events (4,096-byte payload, burst)
Shard: capture
Lifetime peak process memory (RSS) 116.23 MiB 116.26 MiB <0.1% more memory Not flagged
Capture and deliver events (32-byte payload, steady)
Shard: capture
Allocated memory per operation (estimated) 9.85 KiB/op 10.7 KiB/op 8.6% more memory Worth reviewing: observed regression
Capture and deliver events (32-byte payload, steady)
Shard: capture
Time per operation 15.66 µs/op 15.32 µs/op 2.2% less time Not flagged
Capture and deliver events (32-byte payload, steady)
Shard: capture
Idle process memory (RSS) 102.71 MiB 102.68 MiB <0.1% less memory Not flagged
Capture and deliver events (32-byte payload, steady)
Shard: capture
Observed peak process memory (RSS) 107.11 MiB 106.96 MiB 0.1% less memory Not flagged
Capture and deliver events (32-byte payload, steady)
Shard: capture
Managed heap after settling 10.23 MiB 10.23 MiB <0.1% less memory Not flagged
Capture and deliver events (32-byte payload, steady)
Shard: capture
Process memory after settling (RSS) 107.18 MiB 106.98 MiB 0.2% less memory Not flagged
Capture and deliver events (32-byte payload, steady)
Shard: capture
Process CPU time per operation 28.8 µs/op 28.23 µs/op 2% less time Not flagged
Capture and deliver events (32-byte payload, steady)
Shard: capture
Lifetime peak process memory (RSS) 107.13 MiB 107.15 MiB <0.1% more memory Not flagged
Capture and deliver events (4,096-byte payload, steady)
Shard: capture
Allocated memory per operation (estimated) 17.93 KiB/op 17.58 KiB/op 2% less memory Not flagged
Capture and deliver events (4,096-byte payload, steady)
Shard: capture
Time per operation 22.47 µs/op 21.71 µs/op 3.4% less time Not flagged
Capture and deliver events (4,096-byte payload, steady)
Shard: capture
Idle process memory (RSS) 103.12 MiB 103.16 MiB <0.1% more memory Not flagged
Capture and deliver events (4,096-byte payload, steady)
Shard: capture
Observed peak process memory (RSS) 109.21 MiB 109.54 MiB 0.3% more memory Not flagged
Capture and deliver events (4,096-byte payload, steady)
Shard: capture
Managed heap after settling 10.24 MiB 10.24 MiB <0.1% less memory Not flagged
Capture and deliver events (4,096-byte payload, steady)
Shard: capture
Process memory after settling (RSS) 108 MiB 108.35 MiB 0.3% more memory Not flagged
Capture and deliver events (4,096-byte payload, steady)
Shard: capture
Process CPU time per operation 35.92 µs/op 34.52 µs/op 3.9% less time Not flagged
Capture and deliver events (4,096-byte payload, steady)
Shard: capture
Lifetime peak process memory (RSS) 109.24 MiB 109.58 MiB 0.3% more memory Not flagged
Queue an event (32-byte payload)
Shard: capture
Allocated memory per operation (estimated) 8.92 KiB/op 8.72 KiB/op 2.2% less memory Not flagged
Queue an event (32-byte payload)
Shard: capture
Time per operation 10.92 µs/op 10.81 µs/op 1% less time Not flagged
Queue an event (32-byte payload)
Shard: capture
Process CPU time per operation 22.18 µs/op 21.69 µs/op 2.2% less time Not flagged
Queue an event (4,096-byte payload)
Shard: capture
Allocated memory per operation (estimated) 8.55 KiB/op 9.19 KiB/op 7.4% more memory Not flagged
Queue an event (4,096-byte payload)
Shard: capture
Time per operation 10.21 µs/op 10.28 µs/op 0.6% more time Not flagged
Queue an event (4,096-byte payload)
Shard: capture
Process CPU time per operation 21.04 µs/op 21.39 µs/op 1.6% more time Not flagged
Evaluate all 10 flags
Shard: flags-scaling
Allocated memory per operation (estimated) 131.26 KiB/op 132.54 KiB/op 1% more memory Not flagged
Evaluate all 10 flags
Shard: flags-scaling
Time per operation 186.5 µs/op 186.01 µs/op 0.3% less time Not flagged
Evaluate all 10 flags
Shard: flags-scaling
Process CPU time per operation 314.22 µs/op 314.13 µs/op <0.1% less time Not flagged
Evaluate all 100 flags
Shard: flags-scaling
Allocated memory per operation (estimated) 1.23 MiB/op 1.23 MiB/op 0.1% less memory Not flagged
Evaluate all 100 flags
Shard: flags-scaling
Time per operation 1.62 ms/op 1.65 ms/op 1.8% more time Not flagged
Evaluate all 100 flags
Shard: flags-scaling
Process CPU time per operation 2.68 ms/op 2.7 ms/op 0.7% more time Not flagged
Evaluate all 1,000 flags
Shard: flags-scaling
Allocated memory per operation (estimated) 12.16 MiB/op 12.13 MiB/op 0.3% less memory Not flagged
Evaluate all 1,000 flags
Shard: flags-scaling
Time per operation 18.85 ms/op 18.86 ms/op <0.1% more time Not flagged
Evaluate all 1,000 flags
Shard: flags-scaling
Process CPU time per operation 28.17 ms/op 28.27 ms/op 0.4% more time Not flagged
Evaluate 1,000 flags under concurrent load
Shard: flags-memory
Idle process memory (RSS) 286.27 MiB 286.29 MiB <0.1% more memory Not flagged
Evaluate 1,000 flags under concurrent load
Shard: flags-memory
Observed peak process memory (RSS) 295.4 MiB 295.65 MiB <0.1% more memory Not flagged
Evaluate 1,000 flags under concurrent load
Shard: flags-memory
Managed heap after settling 9.77 MiB 9.77 MiB <0.1% less memory Not flagged
Evaluate 1,000 flags under concurrent load
Shard: flags-memory
Process memory after settling (RSS) 295.4 MiB 295.65 MiB <0.1% more memory Not flagged
Evaluate 1,000 flags under concurrent load
Shard: flags-memory
Lifetime peak process memory (RSS) 296.2 MiB 295.95 MiB <0.1% less memory Not flagged
Refresh 1,000 flag definitions
Shard: flags-memory
Idle process memory (RSS) 227.74 MiB 222.57 MiB 2.3% less memory Not flagged
Refresh 1,000 flag definitions
Shard: flags-memory
Observed peak process memory (RSS) 240.04 MiB 238.27 MiB 0.7% less memory Not flagged
Refresh 1,000 flag definitions
Shard: flags-memory
Managed heap after settling 11.8 MiB 11.81 MiB <0.1% more memory Not flagged
Refresh 1,000 flag definitions
Shard: flags-memory
Process memory after settling (RSS) 234.45 MiB 233.76 MiB 0.3% less memory Not flagged
Refresh 1,000 flag definitions
Shard: flags-memory
Lifetime peak process memory (RSS) 240.63 MiB 240.41 MiB <0.1% less memory Not flagged
Evaluate one boolean flag
Shard: flags-single
Allocated memory per operation (estimated) 17.14 KiB/op 17.18 KiB/op 0.2% more memory Not flagged
Evaluate one boolean flag
Shard: flags-single
Time per operation 44.43 µs/op 44.08 µs/op 0.8% less time Not flagged
Evaluate one boolean flag
Shard: flags-single
Process CPU time per operation 47.13 µs/op 46.58 µs/op 1.1% less time Not flagged
Evaluate a cohort-filtered flag
Shard: flags-single
Allocated memory per operation (estimated) 14.33 KiB/op 14.28 KiB/op 0.3% less memory Not flagged
Evaluate a cohort-filtered flag
Shard: flags-single
Time per operation 23.29 µs/op 24.01 µs/op 3.1% more time Not flagged
Evaluate a cohort-filtered flag
Shard: flags-single
Process CPU time per operation 27.69 µs/op 28.51 µs/op 2.9% more time Not flagged
Evaluate a flag (early match)
Shard: flags-single
Allocated memory per operation (estimated) 17.51 KiB/op 17.59 KiB/op 0.5% more memory Not flagged
Evaluate a flag (early match)
Shard: flags-single
Time per operation 26.97 µs/op 26.97 µs/op <0.1% more time Not flagged
Evaluate a flag (early match)
Shard: flags-single
Process CPU time per operation 30.05 µs/op 30.78 µs/op 2.4% more time Not flagged
Evaluate a flag (late match)
Shard: flags-single
Allocated memory per operation (estimated) 22.37 KiB/op 22.37 KiB/op <0.1% more memory Not flagged
Evaluate a flag (late match)
Shard: flags-single
Time per operation 25.38 µs/op 26.78 µs/op 5.5% more time Not flagged
Evaluate a flag (late match)
Shard: flags-single
Process CPU time per operation 29.2 µs/op 30.5 µs/op 4.5% more time Not flagged
Evaluate a flag (no match)
Shard: flags-single
Allocated memory per operation (estimated) 16.93 KiB/op 16.98 KiB/op 0.3% more memory Not flagged
Evaluate a flag (no match)
Shard: flags-single
Time per operation 3.58 µs/op 3.6 µs/op 0.4% more time Not flagged
Evaluate a flag (no match)
Shard: flags-single
Process CPU time per operation 6.92 µs/op 7.06 µs/op 2% more time Not flagged
Evaluate a property-filtered flag
Shard: flags-single
Allocated memory per operation (estimated) 12.78 KiB/op 12.59 KiB/op 1.5% less memory Not flagged
Evaluate a property-filtered flag
Shard: flags-single
Time per operation 23.64 µs/op 25.51 µs/op 7.9% more time Not flagged
Evaluate a property-filtered flag
Shard: flags-single
Process CPU time per operation 27.24 µs/op 28.79 µs/op 5.7% more time Not flagged
Evaluate a regex-filtered flag
Shard: flags-single
Allocated memory per operation (estimated) 18.22 KiB/op 18.24 KiB/op <0.1% more memory Not flagged
Evaluate a regex-filtered flag
Shard: flags-single
Time per operation 49.28 µs/op 52.36 µs/op 6.2% more time Worth reviewing: observed regression
Evaluate a regex-filtered flag
Shard: flags-single
Process CPU time per operation 52.02 µs/op 55.3 µs/op 6.3% more time Worth reviewing: observed regression
Evaluate a rollout flag
Shard: flags-single
Allocated memory per operation (estimated) 14.24 KiB/op 14.2 KiB/op 0.2% less memory Not flagged
Evaluate a rollout flag
Shard: flags-single
Time per operation 34.29 µs/op 35.42 µs/op 3.3% more time Not flagged
Evaluate a rollout flag
Shard: flags-single
Process CPU time per operation 37.54 µs/op 38.26 µs/op 1.9% more time Not flagged
Evaluate a multivariate flag
Shard: flags-single
Allocated memory per operation (estimated) 17.33 KiB/op 17.39 KiB/op 0.4% more memory Not flagged
Evaluate a multivariate flag
Shard: flags-single
Time per operation 46.55 µs/op 48.02 µs/op 3.2% more time Not flagged
Evaluate a multivariate flag
Shard: flags-single
Process CPU time per operation 49.47 µs/op 50.21 µs/op 1.5% more time Not flagged

Values are medians of paired measurements. Not flagged does not mean unchanged. Unavailable means a measurement could not be provided, not zero. Estimated allocation measurements retain their instrumentation uncertainty. RSS measures the whole process, not just SDK allocations; observed peaks are sampled checkpoints. Paired ranges in the diagnostics describe variability, not confidence intervals.

Each shard uses its own runner; compare Before PR against With PR within a row, not across shards.

Compared 74013ba51f537a0bf09bfbf1289f5d932471e5ab → 52a7aed8f8db77d3149adc756b97719b2fb4e70a.

Full report and diagnostics

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

This branch has not been deployed

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

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.

0 participants