Aurora (PostgreSQL data connector) - Fixed an issue where PostgreSQL data generation to an Amazon Aurora destination failed on every run after the first when the source database had Aurora's pg_columnmask dynamic data masking extension installed. Structural no longer copies provider-managed extensions into the destination.
Oracle workspaces now always run on Data Pipeline V2. The option on the Confirm Generation panel to choose between classic flow and Data Pipeline V2 is removed. Existing Oracle workspaces will automatically use the Data Pipeline V2 flow.
Removed the Oracle database-link generation path and the TONIC_ORACLE_DBLINK_ENABLED environment setting. The setting no longer has any effect. You can remove it from your configuration. Database links that exist as objects in your Oracle schema are not affected. Structural still discovers them, and still warns when the destination is missing a link that is referenced by a source synonym.
OAuth for MCP authentication - You can now sign in through your browser to connect supported MCP clients to Structural. Before you approve the access, Structural shows you which application is requesting access. Existing API key connections continue to work and are not changed. To see everything you've authorized, or to revoke access at any time, go to User Settings → Connected applications.