Skip to content

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

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/github-actions-2effbdfd18
Closed

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

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 2, 2026 •

Copy link
Copy Markdown
Contributor

Bumps the github-actions group with 6 updates:

Package From To
actions/setup-python 7.0.0 7.1.0
astral-sh/setup-uv 10.3.0 10.3.2
github/codeql-action/init 4.39.0 4.39.1
github/codeql-action/analyze 4.39.0 4.39.1
pypa/gh-action-pypi-publish 1.14.2 1.14.3
PostHog/posthog-sdk-test-harness/.github/workflows/test-sdk-action.yml 1.17.0 1.22.0

Updates actions/setup-python from 7.0.0 to 7.1.0

Release notes

Sourced from actions/setup-python's releases.

v7.1.0

What's Changed

Enhancements

Dependency Upgrade

New Contributors

Full Changelog: actions/setup-python@v7.0.0...v7.1.0

Commits
  • 6d4fd22 Cache upgrade to 6.3.0 (#1370)
  • ec52d0a Bump @​typescript-eslint/eslint-plugin from 8.62.0 to 8.71.1 (#1369)
  • ff73b24 Bump prettier from 3.8.4 to 3.9.9 and package.json from 7.0.0 to 7.1.0 (#1363)
  • 0e40890 Bump brace-expansion from 5.0.9 to 5.0.12 (#1365)
  • 3892123 Bump ts-jest from 29.4.11 to 29.4.14 (#1361)
  • 6609657 Bump undici from 6.28.0 to 6.29.0 (#1364)
  • e1be392 Bump @​types/semver from 7.7.1 to 7.8.0 (#1359)
  • 06da627 Bump @​vercel/ncc from 0.44.0 to 0.45.0 (#1357)
  • af9bcc7 Bump eslint-plugin-jest from 29.15.2 to 29.16.6 (#1342)
  • 7aeabeb Bump @​typescript-eslint/parser from 8.62.0 to 8.70.0 (#1343)
  • Additional commits viewable in compare view

Updates astral-sh/setup-uv from 10.3.0 to 10.3.2

Release notes

Sourced from astral-sh/setup-uv's releases.

v10.3.2 🌈 update known checksums for 0.13.5

Changes

🧰 Maintenance

📚 Documentation

v10.3.1 🌈 preserve cache error class names in save-cache bundle

Changes

This release includes a fix so that multiple concurrent workflows trying to upload the same cache no longer warn

##[warning]Failed to save: Unable to reserve cache with key ..., another job may be creating this cache.

🐛 Bug fixes

🧰 Maintenance

📚 Documentation

⬆️ Dependency updates

Commits
  • 07a047e chore: update known checksums for 0.13.5 (#1103)
  • e1b8536 docs: update version references to v10.3.1 (#1102)
  • 18d369b chore(deps): roll up Dependabot updates (#1101)
  • 4ad2329 chore: update known checksums for 0.13.4 (#1099)
  • 4bc6759 chore: update known checksums for 0.13.2/0.13.3 (#1098)
  • c97f06e fix: preserve cache error class names in save-cache bundle (#1093)
  • 8ca4be0 chore: update known checksums for 0.13.1 (#1094)
  • b627d85 docs: cache-dependency-glob matches relative to the working directory (#1092)
  • f8c8897 Verify npm dependency signatures before builds (#1027)
  • f64d32b docs: update version references to v10.3.0 (#1090)
  • See full diff in compare view

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

Release notes

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

v4.39.1

  • Update default CodeQL bundle version to 2.27.3. #4256
Changelog

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

CodeQL Action Changelog

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

[UNRELEASED]

No user facing changes.

4.39.1 - 21 Oct 2026

  • Update default CodeQL bundle version to 2.27.3. #4256

4.39.0 - 15 Oct 2026

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

4.38.3 - 08 Oct 2026

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

4.38.2 - 24 Sept 2026

  • Update default CodeQL bundle version to 2.27.1. #4160

4.38.1 - 18 Sept 2026

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

4.38.0 - 09 Sept 2026

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

4.37.9 - 26 Aug 2026

  • Update default CodeQL bundle version to 2.26.4. #4106

4.37.8 - 21 Aug 2026

No user facing changes.

4.37.7 - 13 Aug 2026

  • Update default CodeQL bundle version to 2.26.3. #4085

... (truncated)

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

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

Release notes

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

v4.39.1

  • Update default CodeQL bundle version to 2.27.3. #4256
Changelog

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

CodeQL Action Changelog

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

[UNRELEASED]

No user facing changes.

4.39.1 - 21 Oct 2026

  • Update default CodeQL bundle version to 2.27.3. #4256

4.39.0 - 15 Oct 2026

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

4.38.3 - 08 Oct 2026

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

4.38.2 - 24 Sept 2026

  • Update default CodeQL bundle version to 2.27.1. #4160

4.38.1 - 18 Sept 2026

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

4.38.0 - 09 Sept 2026

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

4.37.9 - 26 Aug 2026

  • Update default CodeQL bundle version to 2.26.4. #4106

4.37.8 - 21 Aug 2026

No user facing changes.

4.37.7 - 13 Aug 2026

  • Update default CodeQL bundle version to 2.26.3. #4085

... (truncated)

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

Updates pypa/gh-action-pypi-publish from 1.14.2 to 1.14.3

Release notes

Sourced from pypa/gh-action-pypi-publish's releases.

v1.14.3

[!important] 🚨 This release includes fixes for GHSA-5xjx-3w67-w9x9 patched up by @​sethmlarson💰 in #427 and in other places across the ecosystem.

Additional ecosystem and related mitigations beyond you might want to watch out for:

🛠️ Security Tightening

@​webknjaz💰 made sure the dependency tree within the action runtime uses hash-checking from now on via pypa/gh-action-pypi-publish#420.

🪞 Full Diff: pypa/gh-action-pypi-publish@v1.14.2...v1.14.3

🧔‍♂️ Release Manager: @​webknjaz 🇺🇦

💬 Discuss on Bluesky 🦋, on Mastodon 🐘 and on GitHub.

GH Sponsors badge

Commits
  • 7245906 Merge pull request #427 from sethmlarson/certifi-sigstore
  • 331eccb Upgrade certifi and sigstore
  • f68fee4 💰 Sync the FUNDING config
  • c0d6f8e Merge branch 'integrity/runtime/deptree' into unstable/v1
  • 9090099 🧪 Make smoke test deps hash-pinned in CI
  • 34e40c2 📌 Bump pip-tools managed transitive deptrees
  • e800ed5 👷 Enable hash-checking in the runtime deptree 🔗
  • dd8c5f4 🔧 Make pip-tools config available in container
  • See full diff in compare view

Updates PostHog/posthog-sdk-test-harness/.github/workflows/test-sdk-action.yml from 1.17.0 to 1.22.0

Release notes

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

1.22.0

Minor changes

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

    • corpus/v2_experiment_evaluation.json gains defaults with the flag and context every case shares. A case no longer carries flag, and its context holds only the fields that differ from the default context.
    • Cases no longer carry legacy; consumers derive it from expected.value with the typed value corpus table.
    • hash_evidence entries keep use, prefix, identifier, salt and hash01_binary64_hex. The SHA-1 intermediates move out to corpus/hash_sha1_60_v1.json, which already pins them, and the threshold or boundaries follow from the rule.
    • Removed cases: v2_experiment.assignment.fifty_fifty_test, an exact copy of v2_experiment.ordering.split, and seven parser rows that repeat a config fixture: parser.experiment_id, parser.holdout_id, parser.missing_paused, parser.one_variant, parser.twenty_one_variants, parser.variant_key_characters and parser.variant_value_type. The corpus has 73 cases. — Thanks @​andehen!

1.21.0

Minor changes

  • 2c3a2ae Rename the feature flag rules v2 /flags response record from v3 to v4 (contract package 7.0.0). Clients already send v=3 and arbitrary v values to /flags, so the service selects the typed record only for an exact v=4, and the contract now names the record after that request version. The record's shape and every expectation are unchanged.

    • Schemas: schemas/flags_response_v3.schema.json is renamed to schemas/flags_response_v4.schema.json, with $id https://posthog.com/contracts/feature_flag_rules_v2/flags_response_v4.schema.json and title POST /flags?v=4 response (producer contract). schemas/flags_response_v3_presence.schema.json is renamed to schemas/flags_response_v4_presence.schema.json, with the matching $id, title and $ref. These $id changes are a deliberate exception to the stable-$id rule, made in this major version.
    • Fixtures: fixtures/wire/responses.json and fixtures/wire/readers.json point at the renamed producer schema. The reader cases readers.v3_value_takes_precedence and readers.v1_at_v3 are renamed to readers.v4_value_takes_precedence and readers.v1_at_v4, with the same expectations.
    • Manifest and README follow the renames. — Thanks @​andehen!

1.20.0

Minor changes

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

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

1.19.0

Minor changes

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

1.18.0

Minor changes

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

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

posthog-sdk-test-harness

1.27.0 — 2026-10-30

Minor changes

  • 0e31ca6 Trim the feature flag rules v2 SDK experiment exposure contract and drop the reason description from config version 2 flag calls, following PostHog/sdk-specs#162 (contract package 8.0.0).

    • schemas/experiment_exposure_properties.schema.json requires exactly $feature_flag, $feature_flag_response, $feature_flag_variant, $feature_flag_rule_id and locally_evaluated. $feature_flag_config_version, $feature_flag_rule_type, $feature_flag_reason_code and $experiment_exposure_source are removed, so the closed schema rejects an exposure that carries them. An SDK sends the exposure only for a config version 2 experiment split, so their values were constants; the rule ID identifies the experiment rule and marks the exposure as SDK-sent. $feature_flag_forced_variant stays rejected.
    • schemas/feature_flag_called_context.schema.json declares $feature_flag_reason and rejects it on a config version 2 call, which carries $feature_flag_reason_code instead. Config version 1 calls keep $feature_flag_reason with any value.
    • The meta-tests check both schemas against projections they build: an exposure without each required property, an exposure with each forbidden property, and a config version 2 call with $feature_flag_reason for every presence-matrix row. No fixture set is added.
    • Consumers that vendor the exposure schema need to copy this release. — Thanks @​andehen!

1.26.0 — 2026-10-29

Minor changes

  • 48f69e1 event_size.batches_close_before_byte_target_and_keep_order is now event_size.batches_close_before_byte_target and no longer checks arrival order across requests: an SDK may send batches in parallel. assert_events_property_values takes any_order: true for this.

    The capture AI v1 suite now runs the reported_drops, property_layers and fail_open tests the analytics suite already had, on the AI lane: an AI event capture drops (or a dropped duplicate copy) is reported, a capture_ai property beats a registered one and before_send runs last, and an empty or personal API key sends no AI request. — Thanks @​eli-r-ph!

1.25.0 — 2026-10-28

Minor changes

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

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

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

1.24.0 — 2026-10-28

Minor changes

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

    • New retry tests: SDKs retry 404, 429 and 502 like 408 and the other 5xx statuses.
    • implements_backoff measures the SDK's own waits (100, 200 and 400 ms, jitter down to 0.75x) on a 502 that carries no Retry-After.
    • The mock answers a repeated uuid the way capture does: it keeps the first copy's result and adds duplicates_dropped. A new test checks that only the first copy is resent when capture asks for a retry.
    • Partial-batch tests use capture's warning result instead of limited, which capture never sends. The mock still accepts limited for older feature files.

... (truncated)

Commits
  • 17d861f chore: Release v1.22.0 [skip ci]
  • 0bc2c7c test(flags): slim the experiment rule evaluation corpus (#90)
  • 3103998 chore: Release v1.21.0 [skip ci]
  • 2c3a2ae feat(flags): name the rules v2 response record v4 (contract 7.0.0) (#91)
  • 466cd60 chore(deps): bump uv to 0.13.4 (#89)
  • aa725c8 chore: Release v1.20.0 [skip ci]
  • 34fd648 feat(flags): add the experiment rule evaluation corpus without experiment or ...
  • 129fbb4 chore: Release v1.19.0 [skip ci]
  • 65b0eb7 feat(v2): unify migrated and canonical SDK acceptance (#88)
  • 3957869 chore: Release v1.18.0 [skip ci]
  • 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 6 updates:

| Package | From | To |
| --- | --- | --- |
| [actions/setup-python](https://github.com/actions/setup-python) | `7.0.0` | `7.1.0` |
| [astral-sh/setup-uv](https://github.com/astral-sh/setup-uv) | `10.3.0` | `10.3.2` |
| [github/codeql-action/init](https://github.com/github/codeql-action) | `4.39.0` | `4.39.1` |
| [github/codeql-action/analyze](https://github.com/github/codeql-action) | `4.39.0` | `4.39.1` |
| [pypa/gh-action-pypi-publish](https://github.com/pypa/gh-action-pypi-publish) | `1.14.2` | `1.14.3` |
| [PostHog/posthog-sdk-test-harness/.github/workflows/test-sdk-action.yml](https://github.com/posthog/posthog-sdk-test-harness) | `1.17.0` | `1.22.0` |


Updates `actions/setup-python` from 7.0.0 to 7.1.0
- [Release notes](https://github.com/actions/setup-python/releases)
- [Commits](actions/setup-python@5fda3b9...6d4fd22)

Updates `astral-sh/setup-uv` from 10.3.0 to 10.3.2
- [Release notes](https://github.com/astral-sh/setup-uv/releases)
- [Commits](astral-sh/setup-uv@1c37ad0...07a047e)

Updates `github/codeql-action/init` from 4.39.0 to 4.39.1
- [Release notes](https://github.com/github/codeql-action/releases)
- [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md)
- [Commits](github/codeql-action@6f2ac81...9b32540)

Updates `github/codeql-action/analyze` from 4.39.0 to 4.39.1
- [Release notes](https://github.com/github/codeql-action/releases)
- [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md)
- [Commits](github/codeql-action@6f2ac81...9b32540)

Updates `pypa/gh-action-pypi-publish` from 1.14.2 to 1.14.3
- [Release notes](https://github.com/pypa/gh-action-pypi-publish/releases)
- [Commits](pypa/gh-action-pypi-publish@dc37677...7245906)

Updates `PostHog/posthog-sdk-test-harness/.github/workflows/test-sdk-action.yml` from 1.17.0 to 1.22.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@8ca75c4...17d861f)

---
updated-dependencies:
- dependency-name: actions/setup-python
  dependency-version: 7.1.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: github-actions
- dependency-name: astral-sh/setup-uv
  dependency-version: 10.3.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: github-actions
- dependency-name: github/codeql-action/init
  dependency-version: 4.39.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: github-actions
- dependency-name: github/codeql-action/analyze
  dependency-version: 4.39.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: github-actions
- dependency-name: pypa/gh-action-pypi-publish
  dependency-version: 1.14.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.22.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 added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Nov 2, 2026
@dependabot
dependabot Bot requested a review from a team as a code owner November 2, 2026 10:11
@github-actions

github-actions Bot commented Nov 2, 2026 •

Copy link
Copy Markdown
Contributor

posthog-python Compliance Report

Date: 2026-11-02T10:16:17.964120+00:00
Duration: 259878ms

✅ All Tests Passed!

121/121 tests passed


Capture_V1 Tests

✅ 95/95 tests passed

View Details
Test Status Duration
Endpoint And Method.Targets V1 Endpoint ✅ 518ms
Endpoint And Method.Does Not Use Legacy Endpoints ✅ 510ms
Required Headers.Has Authorization Bearer Header ✅ 510ms
Required Headers.Has Content Type Json ✅ 510ms
Required Headers.Has Posthog Sdk Info Format ✅ 510ms
Required Headers.Has Posthog Attempt Header ✅ 510ms
Required Headers.Has Posthog Request Id ✅ 511ms
Required Headers.Has Posthog Request Timestamp ✅ 510ms
Required Headers.Has User Agent ✅ 510ms
Body Format.Body Has Created At And Batch ✅ 510ms
Body Format.No Api Key In Body ✅ 510ms
Body Format.No Sent At In Body ✅ 510ms
Event Format.Event Has Required Root Fields ✅ 510ms
Event Format.Event Uuid Is Valid ✅ 510ms
Event Format.Event Timestamp Is Rfc3339 ✅ 510ms
Event Format.Non Utc Event Timestamp Is Converted To Utc ✅ 527ms
Event Format.Distinct Id Is String ✅ 510ms
Event Format.Distinct Id At Root Not Properties ✅ 510ms
Event Format.Custom Properties Preserved ✅ 510ms
Event Format.Set Properties Preserved ✅ 510ms
Event Format.Set Once Properties Preserved ✅ 510ms
Event Format.Groups Properties Preserved ✅ 510ms
Event Format.Sdk Generates Uuid If Not Provided ✅ 510ms
Event Format.Event Has Required Root Fields Batch ✅ 514ms
Event Format.Event Uuid Is Valid Batch ✅ 513ms
Event Format.Event Timestamp Is Rfc3339 Batch ✅ 514ms
Event Format.Distinct Id Is String Batch ✅ 513ms
Event Format.Distinct Id At Root Not Properties Batch ✅ 514ms
Event Format.Custom Properties Preserved Batch ✅ 515ms
Event Format.Set Properties Preserved Batch ✅ 513ms
Event Format.Set Once Properties Preserved Batch ✅ 514ms
Event Format.Groups Properties Preserved Batch ✅ 513ms
Event Format.Sdk Generates Uuid If Not Provided Batch ✅ 513ms
Batch Behavior.Multiple Events In Single Batch ✅ 519ms
Batch Behavior.Batch Envelope Smoke ✅ 515ms
Batch Behavior.Flush With No Events Sends Nothing ✅ 506ms
Batch Behavior.Flush At Triggers Batch ✅ 1011ms
Batch Behavior.Created At Reflects Batch Creation Time ✅ 511ms
Deduplication.Generates Unique Uuids ✅ 517ms
Deduplication.Different Events Same Content Different Uuids ✅ 513ms
Deduplication.Preserves Uuid On Retry ✅ 6519ms
Deduplication.Preserves Timestamp On Retry ✅ 6519ms
Deduplication.Preserves Uuid And Timestamp On Batch Retry ✅ 6523ms
Deduplication.No Duplicate Events In Batch ✅ 518ms
Header Behavior On Retry.Attempt Header Starts At One ✅ 510ms
Header Behavior On Retry.Attempt Header Increments On Retry ✅ 13527ms
Header Behavior On Retry.Request Id Preserved On Retry ✅ 6516ms
Header Behavior On Retry.Different Requests Have Different Request Ids ✅ 3019ms
Header Behavior On Retry.Request Timestamp Changes On Retry ✅ 6520ms
Response Format Validation.Success Response Has Uuid Keyed Results ✅ 510ms
Response Format Validation.Success Response Has Ok For Each Event ✅ 515ms
Response Format Validation.Success No Retry After When All Ok ✅ 512ms
Response Format Validation.Success Retry After Present When Retry Events ✅ 1516ms
Response Format Validation.Success No Retry After When Drop Only ✅ 514ms
Response Format Validation.Response Echoes Request Id ✅ 511ms
Retry Behavior.Retries On 408 ✅ 6520ms
Retry Behavior.Retries On 500 ✅ 6515ms
Retry Behavior.Retries On 503 ✅ 8523ms
Retry Behavior.Retries On 504 ✅ 6519ms
Retry Behavior.Retryable Errors Have Retry After ✅ 3516ms
Retry Behavior.Respects Retry After On Retryable Error ✅ 11517ms
Retry Behavior.Does Not Retry On 400 ✅ 2513ms
Retry Behavior.Does Not Retry On 401 ✅ 2512ms
Retry Behavior.Does Not Retry On 402 ✅ 2514ms
Retry Behavior.Does Not Retry On 413 ✅ 2513ms
Retry Behavior.Does Not Retry On 415 ✅ 2514ms
Retry Behavior.Non Retryable Errors Have No Retry After ✅ 2510ms
Retry Behavior.Implements Backoff ✅ 22531ms
Retry Behavior.Max Retries Respected ✅ 22526ms
Partial Batch Handling.Handles 200 Full Success ✅ 2513ms
Partial Batch Handling.Handles 200 With All Ok ✅ 3515ms
Partial Batch Handling.Does Not Retry Dropped Events ✅ 3514ms
Partial Batch Handling.Does Not Retry Limited Events ✅ 3515ms
Partial Batch Handling.Prunes Ok Events On Partial Retry ✅ 6522ms
Partial Batch Handling.Prunes Dropped Events On Partial Retry ✅ 6520ms
Partial Batch Handling.Retries Only Retry Events From Partial ✅ 6523ms
Partial Batch Handling.Partial Retry Preserves Uuids ✅ 6518ms
Partial Batch Handling.Partial Retry Attempt Header Increments ✅ 6521ms
Partial Batch Handling.Partial Retry Request Id Preserved ✅ 6521ms
Partial Batch Handling.Respects Retry After On Partial ✅ 8518ms
Partial Batch Handling.Unknown Result Treated As Terminal ✅ 3516ms
Partial Batch Handling.Mixed Ok Drop Limited No Retry ✅ 3519ms
Compression.Sends Gzip Content Encoding ✅ 511ms
Compression.No Content Encoding When Disabled ✅ 510ms
Compression.Compressed Body Is Decompressible ✅ 510ms
Error Handling.Does Not Retry On Unknown 4Xx ✅ 2512ms
Event Options.Cookieless Mode Override ✅ 510ms
Event Options.Disable Skew Correction Override ✅ 511ms
Event Options.Process Person Profile Override ✅ 510ms
Event Options.Product Tour Id Override ✅ 510ms
Event Options.Unset Options Omitted ✅ 510ms
Event Options.Options Override In Batch ✅ 514ms
Geoip And Historical Migration.Geoip Disable Injected Into Properties ✅ 510ms
Geoip And Historical Migration.Historical Migration Set In Body ✅ 511ms
Geoip And Historical Migration.Historical Migration Absent By Default ✅ 511ms

Capture_Ai Tests

✅ 5/5 tests passed

View Details
Test Status Duration
Routing.Capture Ai Posts To Ai Endpoint ✅ 512ms
Routing.Capture Does Not Reroute Ai Named Events ✅ 510ms
Identity.Capture Ai Event Has Uuid ✅ 511ms
Identity.Capture Ai Keeps Supplied Uuid ✅ 510ms
Timestamp Format.Non Utc Event Timestamp Is Converted To Utc ✅ 511ms

Feature_Flags Tests

✅ 17/17 tests passed

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

Feature_Flags_Local_Evaluation Tests

✅ 4/4 tests passed

View Details
Test Status Duration
Versioned Boolean Matching.Matching Version Missing ✅ 72ms
Versioned Boolean Matching.Matching Version 1 ✅ 70ms
Versioned Boolean Matching.Matching Version 2 ✅ 68ms
Versioned Boolean Matching.Version Only Reload 1 2 1 2 Missing ✅ 35ms

@dependabot @github

dependabot Bot commented on behalf of github Nov 9, 2026

Copy link
Copy Markdown
Contributor Author

Looks like these dependencies are updatable in another way, so this is no longer needed.

@dependabot dependabot Bot closed this Nov 9, 2026
@dependabot
dependabot Bot deleted the dependabot/github_actions/github-actions-2effbdfd18 branch November 9, 2026 10:09
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