Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: astral-sh/setup-uv@v6. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

WARNING: SQL-parsed foreign key constraint '('user_id', 'user', 'id')' could not be located in PRAGMA foreign_keys for table flow

WARNING: SQL-parsed foreign key constraint '('flow_id', 'flow', 'id')' could not be located in PRAGMA foreign_keys for table trace

WARNING: SQL-parsed foreign key constraint '('user_id', 'user', 'id')' could not be located in PRAGMA foreign_keys for table file

autogenerate skipping metadata-specified expression-based index 'ix_message_session_metadata_user'; dialect 'sqlite' under SQLAlchemy 2.0.49 can't reflect these indexes so they can't be compared

autogenerate skipping metadata-specified expression-based index 'ix_message_session_metadata_tenant'; dialect 'sqlite' under SQLAlchemy 2.0.49 can't reflect these indexes so they can't be compared

WARNING: SQL-parsed foreign key constraint '('flow_id', 'flow', 'id')' could not be located in PRAGMA foreign_keys for table trace

WARNING: SQL-parsed foreign key constraint '('user_id', 'user', 'id')' could not be located in PRAGMA foreign_keys for table file

Skipped unsupported reflection of expression-based index ix_message_session_metadata_tenant

Skipped unsupported reflection of expression-based index ix_message_session_metadata_user