[trunk-io]

This pull request was created and is being managed by Trunk Merge.

This pull request is based on the master branch at SHA a9bd34eb85f250b6177985a66954feffacc67b93.

See more details about each PR in the batch here:

• PR 100947
• PR 123232
• PR 123535
• PR 123695

When CI completes, this pull request will be closed automatically.

Pull Requests Being Tested

This pull request is testing a batch with the changes from pull requests 100947, 123232, 123535, and 123695 - batching documentation.

Dependencies

This pull request depends on the changes from pull requests 124184, 123250, 123419, 124125, 122639, 124028, 123708, 122978, 124226, 121966, 123512, 121720, 123456, 124023, 123983, 124039, 124042, 124157, 123897, 123927, 124204, 124198, 123698, 124218, 123938, 123999, 122437, 124242, 124241, and 123868.

[tests-posthog]

🤖 CI report

⚠️ Django migration SQL — 2 new migrations to review

We've detected new migrations on this PR. Review the SQL output for each migration:

posthog/migrations/1414_remove_filesystem_rows_for_deleted_insights.py

/home/runner/work/tmp/tool_cache/Python/3.14.7/x64/lib/python3.14/site-packages/anyio/from_thread.py:119: SyntaxWarning: 'return' in a 'finally' block
  return result
2026-10-27T17:34:34.396027Z [error    ] Path must be a valid database or directory containing databases. [posthog.exceptions_capture] pid=6772 tid=139993683696512
Traceback (most recent call last):
  File "/home/runner/work/posthog/posthog/posthog/geoip.py", line 15, in <module>
    geoip: Optional[GeoIP2] = GeoIP2(cache=8)
                              ~~~~~~^^^^^^^^^
  File "/home/runner/work/tmp/tool_cache/Python/3.14.7/x64/lib/python3.14/site-packages/django/contrib/gis/geoip2.py", line 116, in __init__
    raise GeoIP2Exception(
        "Path must be a valid database or directory containing databases."
    )
django.contrib.gis.geoip2.GeoIP2Exception: Path must be a valid database or directory containing databases.
/home/runner/work/tmp/tool_cache/Python/3.14.7/x64/lib/python3.14/site-packages/sshtunnel.py:1040: SyntaxWarning: 'return' in a 'finally' block
  return (ssh_host,
/home/runner/work/tmp/tool_cache/Python/3.14.7/x64/lib/python3.14/site-packages/langchain_core/_api/deprecation.py:27: UserWarning: Core Pydantic V1 functionality isn't compatible with Python 3.14 or greater.
  from pydantic.v1.fields import FieldInfo as FieldInfoV1
System check identified some issues:

WARNINGS:
?: (axes.W001) You are using the django-axes cache handler for login attempt tracking. Your cache configuration is however invalid and will not work correctly with django-axes. This can leave security holes in your login systems as attempts are not tracked correctly. Reconfigure settings.AXES_CACHE and settings.CACHES per django-axes configuration documentation.
?: (staticfiles.W004) The directory '/home/runner/work/posthog/posthog/frontend/dist' in the STATICFILES_DIRS setting does not exist.
--
-- Raw Python operation
--
-- THIS OPERATION CANNOT BE WRITTEN AS SQL

products/aeo/backend/migrations/0007_citation_check_brand_sentiment.py

2026-10-27T17:35:24.249785Z [error    ] Path must be a valid database or directory containing databases. [posthog.exceptions_capture] pid=8014 tid=140339864607616
Traceback (most recent call last):
  File "/home/runner/work/posthog/posthog/posthog/geoip.py", line 15, in <module>
    geoip: Optional[GeoIP2] = GeoIP2(cache=8)
                              ~~~~~~^^^^^^^^^
  File "/home/runner/work/tmp/tool_cache/Python/3.14.7/x64/lib/python3.14/site-packages/django/contrib/gis/geoip2.py", line 116, in __init__
    raise GeoIP2Exception(
        "Path must be a valid database or directory containing databases."
    )
django.contrib.gis.geoip2.GeoIP2Exception: Path must be a valid database or directory containing databases.
/home/runner/work/tmp/tool_cache/Python/3.14.7/x64/lib/python3.14/site-packages/langchain_core/_api/deprecation.py:27: UserWarning: Core Pydantic V1 functionality isn't compatible with Python 3.14 or greater.
  from pydantic.v1.fields import FieldInfo as FieldInfoV1
System check identified some issues:

WARNINGS:
?: (axes.W001) You are using the django-axes cache handler for login attempt tracking. Your cache configuration is however invalid and will not work correctly with django-axes. This can leave security holes in your login systems as attempts are not tracked correctly. Reconfigure settings.AXES_CACHE and settings.CACHES per django-axes configuration documentation.
?: (staticfiles.W004) The directory '/home/runner/work/posthog/posthog/frontend/dist' in the STATICFILES_DIRS setting does not exist.
BEGIN;
--
-- Add field brand_sentiment to aeocitationcheck
--
ALTER TABLE "posthog_aeo_citation_check" ADD COLUMN "brand_sentiment" varchar(16) NULL;
--
-- Add field brand_sentiment_score to aeocitationcheck
--
ALTER TABLE "posthog_aeo_citation_check" ADD COLUMN "brand_sentiment_score" double precision NULL;
COMMIT;

Last updated: 2026-10-27 17:35 UTC (a97e700)

✅ Django migration risk — migration analysis complete

We've analyzed your migrations for potential risks.

Summary: 1 Safe | 1 Needs Review | 0 Blocked

⚠️ Needs Review

May have performance impact

posthog.1414_remove_filesystem_rows_for_deleted_insights
  └─ #1 ⚠️ RunPython: RunPython data migration needs review for performance

✅ Safe

Brief or no lock, backwards compatible

aeo.0007_citation_check_brand_sentiment
  └─ #1 ✅ AddField
     Adding nullable field requires brief lock
     model: aeocitationcheck, field: brand_sentiment
  └─ #2 ✅ AddField
     Adding nullable field requires brief lock
     model: aeocitationcheck, field: brand_sentiment_score

📚 How to Deploy These Changes Safely

AddField:

This operation acquires a brief lock but doesn't rewrite the table.

Deployment uses lock timeouts with automatic retries, so lock contention will cause retries rather than connection pile-up.

RunPython:

Use batching for large data migrations:

• Use .iterator() to avoid loading all rows into memory
• Use .bulk_update() instead of saving individual objects
• Batch size: 1,000-10,000 rows per batch
• Add pauses between batches
• Consider background jobs for very large updates (millions of rows)

See the migration safety guide

Last updated: 2026-10-27 17:36 UTC (a97e700)

[trunk-io]

   

Failed Test	Failure Summary	Logs
Scenes-App/Experiments ExperimentWithHealthFindings play-test	The Storybook test could not find the text “Why?” on the experiment page.	Logs ↗︎
ReportContextMenu routes the dismiss submenu's note button through the dialog instead of applying it	The ReportInterviewInvite component failed because the Kea store does not contain the featureFlagLogic path required to check a feature flag.	Logs ↗︎

View Full Report ↗︎ ⋅ Docs