[dependabot]

Bumps the python-dependencies group with 2 updates in the /fp-cloud-cli directory: posthog and pytest.

Updates posthog from 7.75.11 to 7.81.1

Release notes

Sourced from posthog's releases.

posthog-v7.81.1

Patch changes

• be77b83 Keep the choices of a streamed OpenAI chat completion with n > 1 apart in $ai_output_choices, as a non-streamed one already does. Their text and tool calls were interleaved into one choice. — Thanks @​jaeminbird for your first contribution 🎉!
• a61e64d Preserve Gemini tool call IDs in captured generations, on output tool calls and on tool calls and results in the input history. — Thanks @​mosafariuk!

posthog-v7.81.0

Minor changes

• 01e91db Send transactional email from PostHog email templates with client.emails.send() on Posthog and AsyncPosthog, or with Emails and AsyncEmails from posthog.emails in a process that only sends email. A send needs a project secret API key, goes to the app host, sends an idempotency key, and retries network errors, rate limits and an unavailable service with the same key. Set app_host, email_request_timeout_seconds and email_request_max_retries on the client to configure sends, or max_retries on one send. Errors raise EmailError with PostHog's error code and a category name. Read what happened to a sent email with client.emails.get(message_id), which returns an EmailStatus with status, created_at, status_at and reason for 30 days after the send. — Thanks @​mayteio for your first contribution 🎉!

posthog-v7.80.3

Patch changes

• 4d6e447 Report cached input tokens from OpenAI Agents generation and response spans, which nest them under the usage details fields, and declare them inclusive. — Thanks @​mosafariuk!

posthog-v7.80.2

Patch changes

• ad1b1cb Capture an $ai_embedding event with $ai_is_error and $ai_error when an OpenAI embeddings.create() call fails, in the sync and async wrappers. Before, a failed embeddings call left no event. — Thanks @​pcbeingused333!

posthog-v7.80.1

Patch changes

• 1625f4f Fix streaming OpenAI chat completions when stream_options is None or NOT_GIVEN (it raised a TypeError), and stop adding include_usage to the stream_options dict the caller passed in. — Thanks @​pcbeingused333!

posthog-v7.80.0

Minor changes

• febb3ed Add metrics={"autocapture": True} (alpha): HTTP, database and runtime metrics from the official OpenTelemetry instrumentations, with no instrumentation code. Install posthog[metrics] and run opentelemetry-bootstrap -a install to add the instrumentors for your libraries. Create the client before your web app (Django: in AppConfig.ready()): apps created earlier are not measured. For Flask, use module lookup as below, or import the Flask class only after the client starts; an earlier from flask import Flask alias is not instrumented. Already-served Flask apps are not re-instrumented after shutdown; create a new app for a replacement client. Autocapture does not start when the app already set up OpenTelemetry; export those metrics to PostHog instead. Raw URLs and paths, client addresses, user agents and captured headers are never recorded. metrics.before_send also applies to autocaptured measurements: it can change their value and attributes, or drop them.

  import flask
  from posthog import Posthog
  client = Posthog("phc_...", metrics={"autocapture": True})
  app = flask.Flask(name)

  — Thanks @​DanielVisca!

posthog-v7.79.0

Minor changes

• bb2b9d6 Report flags that local evaluation could not resolve on evaluate_flags() snapshots. FeatureFlagEvaluations.unresolved_flags maps each such flag to an UnresolvedFlagReason (experience_continuity, unsupported_definition, unresolved_dependency or missing_context), and reading one reports the local_evaluation_inconclusive error instead of flag_missing. When definitions load, log one warning per flag that local evaluation can never resolve (experience continuity, a static cohort, an unknown operator, a malformed value, or a missing or circular flag dependency), and again only when its definition changes. AsyncClient evaluates only remotely, so its snapshots have no unresolved flags.

  Behavior changes:

  • A condition with a filter that local evaluation can't check and a filter that does not match now resolves locally as no match. Before, such a flag fell back to a remote request, or stayed unresolved with only_evaluate_locally=True.
  • An inactive flag with experience continuity enabled now resolves to false locally instead of falling back to a remote request.
  • A flag that depends on a flag with experience continuity enabled is no longer evaluated locally. It falls back to a remote request, or stays unresolved with only_evaluate_locally=True.

... (truncated)

Commits

• f23efe9 chore: Release v7.81.1 [skip ci]
• a61e64d fix(ai): preserve Gemini tool call IDs in captured generations (#1150)
• be77b83 fix(ai): keep the choices of an n>1 OpenAI chat stream apart (#1152)
• af8e1aa Update generated references
• 139161e chore: Release v7.81.0 [skip ci]
• 01e91db feat: send transactional email from posthog templates (#1093)
• 50cf357 ci: pin Python 3.11 by minor version for Ubuntu 26.04 runners (#1153)
• c9105c5 chore(deps): bump the ai-providers group across 1 directory with 7 updates (#...
• 871ad9e chore(deps): bump authlib from 1.7.2 to 1.9.1 (#1140)
• 6f765a3 chore(deps): bump setuptools from 83.0.0 to 84.1.0 in /examples/example-ai-au...
• Additional commits viewable in compare view

Updates pytest from 9.1.1 to 9.2.0

Release notes

Sourced from pytest's releases.

9.2.0

pytest 9.2.0 (2026-10-27)

Removals and backward incompatible breaking changes

• #14716: -c now raises a usage error for a path that does not exist, is a directory, or is in a format pytest has no loader for. Such paths were previously either ignored or reported as an unhandled FileNotFoundError.

• #8593: The indirect, ids and scope arguments of Metafunc.parametrize() <pytest.Metafunc.parametrize> -- and therefore of @pytest.mark.parametrize <pytest.mark.parametrize ref> -- are now keyword-only.

  Passing them positionally was a common source of confusing errors, e.g. parametrize("arg1", "arg2", [(1, 2)]) made the argvalues land in indirect and failed with indirect fixture '(1, 2)' doesn't exist; such mistakes now fail with an understandable TypeError. The type annotations have always declared these arguments as keyword-only.

• #993: Plugin import failures at startup are now reported and classified instead of escaping as a raw traceback with the accidental exit code 1:

  • a plugin that cannot be found -- via -p, pytest_plugins or PYTEST_PLUGINS -- exits with pytest.ExitCode USAGE_ERROR (4), like a conftest.py that fails to import;
  • a plugin that is found but raises while importing -- including a broken pytest11 entry point or a missing plugin dependency -- exits with pytest.ExitCode INTERNAL_ERROR (3), with the traceback preserved.

  pytest.main now returns these codes instead of raising ImportError. Also fixed an IndexError from pytest's own internals when the plugin raised an exception with no arguments.

Deprecations (removal in next major release)

• #14742: The private _pytest.python.CallSpec2 name has been renamed to CallSpec. The old CallSpec2 alias remains available for now and will be removed in pytest 10 or 11.

• #14755: Schedule yield_fixture decorator for removal in pytest 10 or 11.

• #14774: Similarly to the deprecation of class-scoped fixtures defined as instance methods in pytest 9.1, all higher-scoped fixtures (module, package, and session) defined as instance methods are now deprecated.

  They suffer from the same issue the original deprecation only fixed for class-scoped fixtures, see 10819 and 14011.

• #14808: Passing a non-string value to a string-typed ini option now emits a pytest.PytestRemovedIn10Warning. This affects [tool.pytest.ini_options] in pyproject.toml. In pytest 10 this will raise a TypeError, matching the behavior of the corresponding TOML config path.

• #7323: Passing bytes to TerminalReporter.write_line() is now deprecated, pass a str instead.

New features

• #14743: Full diff: now contains a legend explaining the + & - symbols in diff output.
• #2781: When strict_markers is enabled, marker names used in -m expressions are now validated against registered markers.
• #6881: Added the parametrize_long_str_id_strategy configuration option to control how long str/bytes parameter values are handled in auto-generated test IDs. Explicit IDs set via ids=[...] or pytest.param(..., id=...) are not affected. Available strategies: short (default, values over 100 chars fall back to argname+index), sha256 (SHA-256 hex digest), legacy (keep full value), and disallow (error requesting explicit IDs).

Improvements in existing functionality

• #10745: A RecursionError whose recursion origin cannot be located now shows only the first and last 10 stack frames, matching what pytest already did when locating the origin failed outright. Previously the full traceback -- often around a thousand near-identical frames -- was rendered, which was both slow and unreadable. Pass --full-trace to see every frame.

... (truncated)

Commits

• ae1d0ff Prepare release version 9.2.0
• 143ce31 pre-commit: exclude codespell on generated release announcements
• 532dc5f tox: add attrs dependency to regen, needed in reportingdemo.rst
• a7b2446 Merge pull request #15245 from pytest-dev/claude/project-thread-9jcf91
• 679d09c [pre-commit.ci] pre-commit autoupdate (#15266)
• 41d12cd docs: clarify typing for yield fixtures
• b9022ba Merge pull request #15182 from 1871698/docs/improve-getting-started-description
• 16f87a7 docs: improve getting-started.rst test execution description
• 082ed70 Merge pull request #15255 from pytest-dev/claude/project-thread-eoi3d6
• ae37a01 Merge pull request #15227 from pytest-dev/claude/project-thread-4etye4
• Additional commits viewable in compare view

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: a9e9a16c-b011-4b42-8f5d-5efdb1ee6f4e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

• X
• Mastodon
• Reddit
• LinkedIn

[github-actions]

Thanks @dependabot[bot] for keeping our dependencies current! 🙌

[github-actions]

Automated approval for Dependabot dependency update.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	pypi/​posthog@​7.75.11 ⏵ 7.81.1	-6

View full report

[hermes-exosphere]

pr-autopilot reviewed this and approves it (commit f16640a), so no person is needed any more.

Safe to merge: the actual PR updates only PostHog and pytest. The reported Authlib and setuptools bumps belong to PostHog’s upstream history, not this repository’s diff. Release notes, package artifacts, repository usage, and green Python CI reveal no issue requiring human review.

Findings

• info setuptools: The actual diff contains no setuptools bump. Its build requirements remain unchanged; reviewed 84.0 compiler compatibility changes and 84.1 archive protections do not affect the CLI’s pure-Python PEP 517 build.
• info authlib: No Authlib bump or CLI dependency exists. Its OAuth, nonce validation, and httpx2 compatibility changes appear only in upstream history and do not reach this repository through PostHog’s dependencies.
• info posthog: Reviewed every intervening release. Feature-flag, MCP, and AI changes affect integrations the CLI does not use; metrics and email features require opt-in. The CLI’s capture implementation remains compatible, and telemetry is currently disabled.
• info pytest: Reviewed 9.2.0’s breaking changes. All 103 parametrization calls avoid the newly forbidden positional arguments; CLI tests do not use affected configuration or plugin-failure handling. Existing locked dependencies satisfy raised minimums, and green CI exercises the suite on Python 3.10–3.13.
• info posthog, pytest: Both updated packages retain Python >=3.10 and MIT licensing, and provide pure-Python wheels without install hooks or binary downloads. PostHog’s setup.py is unchanged; pytest raises its source-build setuptools-scm minimum to 10.1.
• info fp-cloud-cli/uv.lock: Only two package versions and their artifacts change; dependency graphs and manifests remain consistent. Downloaded artifacts match PyPI URLs, SHA-256 hashes, and sizes. No new packages or GitHub Actions pins change.

Reviewed by gpt-6.1-sol.

_{pr-autopilot · Codex in a locked-down container · traced by failproofai}

[hermes-exosphere]

pr-autopilot finished reviewing commit f16640a: approved and merged.

[hermes-exosphere]

Automated approval: trivial dependency update.

Safe to merge: the actual PR updates only PostHog and pytest. The reported Authlib and setuptools bumps belong to PostHog’s upstream history, not this repository’s diff. Release notes, package artifacts, repository usage, and green Python CI reveal no issue requiring human review.

Bumps

• posthog 7.75.11 → 7.81.1 (Minor)
• authlib 1.7.2 → 1.9.1 (Minor)
• setuptools 83.0.0 → 84.1.0 (Major)
• pytest 9.1.1 → 9.2.0 (Minor)

Findings

• info setuptools: The actual diff contains no setuptools bump. Its build requirements remain unchanged; reviewed 84.0 compiler compatibility changes and 84.1 archive protections do not affect the CLI’s pure-Python PEP 517 build.
• info authlib: No Authlib bump or CLI dependency exists. Its OAuth, nonce validation, and httpx2 compatibility changes appear only in upstream history and do not reach this repository through PostHog’s dependencies.
• info posthog: Reviewed every intervening release. Feature-flag, MCP, and AI changes affect integrations the CLI does not use; metrics and email features require opt-in. The CLI’s capture implementation remains compatible, and telemetry is currently disabled.
• info pytest: Reviewed 9.2.0’s breaking changes. All 103 parametrization calls avoid the newly forbidden positional arguments; CLI tests do not use affected configuration or plugin-failure handling. Existing locked dependencies satisfy raised minimums, and green CI exercises the suite on Python 3.10–3.13.
• info posthog, pytest: Both updated packages retain Python >=3.10 and MIT licensing, and provide pure-Python wheels without install hooks or binary downloads. PostHog’s setup.py is unchanged; pytest raises its source-build setuptools-scm minimum to 10.1.
• info fp-cloud-cli/uv.lock: Only two package versions and their artifacts change; dependency graphs and manifests remain consistent. Downloaded artifacts match PyPI URLs, SHA-256 hashes, and sizes. No new packages or GitHub Actions pins change.

Checked: allowlisted bot author, only dependency files, patch/minor bumps, green CI on this commit, no merge conflicts; then a supply-chain review by gpt-6.1-sol (changelogs, install scripts, lockfile, action pins).

_{pr-autopilot · Codex in a locked-down container · traced by failproofai}