2025.52 Infrastructure Changes

1 min read

Changes to the Infrastructure

Self-hosting clients shall apply an API Gateway update provided by Unique Solution Engineering to patch a Broken Access Control vulnerability.

The advisory and patch guides are provided in disclosed format only.

Changes on Application environment

Change	Name	Default	Example	Required	Applications	Short Description
Added	`FEATURE_FLAG_AGENTIC_TABLE_CONTEXT_UN_14904`	`false`	`false`	`false`	`web-app-chat`	Allows defining Agentic Table instructions to be sent to the LLM for processing.
Added	`FEATURE_FLAG_AGENTIC_TABLE_SHEET_METADATA_UN_14904`	`false`	`false`	`false`	`web-app-chat`	Allows defining sheet-level metadata to be considered when processing an Agentic Table.
Added	`FEATURE_FLAG_AGENTIC_TABLE_ROW_METADATA_UN_14904`	`false`	`false`	`false`	`web-app-chat`	Allows defining row-level metadata to be considered when processing an Agentic Table.
Added	`PG_DATABASE_SSL_MODE`	n/a (must be set)	`verify`, `verify-full`	`true`	`backend-service-app-repository` `backend-service-chat` `backend-service-ingestion` `backend-service-scope-management` `backend-service-configuration`	With Prisma upgrade to 7.0. It now requires we explicitly set the SSL_MODE of the database. Setting to `verify` is usually enough. More details about this here

Prisma 7.0 Upgrade

We’ve upgraded our ORM, Prisma, from v4.9 to v7.2. This release delivers notable performance improvements and resolves a memory leak previously caused by how the Rust-based Prisma engine handled memory allocation.

⚠️ Breaking change: Sorting behavior in internal GraphQL API

Prisma 7 introduces changes to sorting semantics that affect our internal GraphQL API. If you rely on sorted results, please review the updated behavior and adjust queries accordingly.

Details: Breaking Change: Release 2025.52
Impact: Sorting order may differ for null values, case sensitivity, or default collation depending on fields and database configuration.

🔒 SSL configuration requirement

If your PostgreSQL server enforces SSL, it is now mandatory to set the PG_DATABASE_SSL_MODE environment variable.

Supported values: verify, verify-full
Action: Ensure your deployment configuration includes PG_DATABASE_SSL_MODE aligned with your DB server’s SSL requirements.
Note: verify-full requires the server hostname to match the certificate’s CN/SAN.

Author	Solution Engineering