Dear Coalesce Customers,

We're writing to inform you of an important backend migration that will be completed on or after December 1, 2025 to improve the performance and reliability of the Coalesce platform. We are migrating our database infrastructure from Google Firestore to PostgreSQL, which will enhance our platform's scalability and query performance.

What This Means for You

As part of this migration, some automatic updates will be applied to your workspace configurations to ensure compatibility with our new backend infrastructure. On or after December 1, 2025, when you next load your workspaces, you may notice changes to your YAML files in Git that require your attention.

Additionally, this upgrade will require you to upgrade the version of your Coalesce CLI (coa) to version 7.25 or later to continue to performing operations with our product.

CLI Upgrade Requirements

Due to changes in how we store and retrieve data in our product, we had to make breaking changes to our CLI that require all users to upgrade to version 7.25 or later to allow you to continue operating the CLI. Versions 7.24 and earlier will improperly attempt to read and write to API endpoints that will no longer be supported or used.

How to Upgrade Your CLI:

1. Check your current version:
   coa --version

2. Upgrade to version 7.25 or later:
   npm install -g @coalescesoftware/cli@latest

3. Verify the upgrade:
   coa --version

For detailed instructions, see our documentation.

Please upgrade your CLI by December 1, 2025.

Changes Made to Your Workspaces

The following updates will be automatically applied on or after December 1, 2025 to ensure your workspaces function correctly with our new system:

1. Source Node Cleanup

• Empty sources have been removed - Sources without any configuration or data connections have been deleted from your workspace.

• Null database/schema values corrected - Sources with missing database or schema information have been updated with appropriate default values.

2. Node and Column ID Updates

• Subgraph node IDs standardized - Node identifiers within subgraphs have been updated to maintain consistency.

• Hash column IDs normalized - Column identifiers used in hash operations have been refreshed to ensure proper functionality.

3. Node Configuration Standardization

• SQL node materialization types - SQL nodes without a specified materialization type have been assigned appropriate defaults (typically 'table' or 'view').

• Column name length limits enforced - Columns with names exceeding 256 characters have been truncated or renamed following standard naming conventions.

• Deploy enabled defaults - Nodes with undefined deploy_enabled properties have been set to true by default.

• Column nullable properties - All columns now have explicit nullable values set (true/false) rather than undefined states.

4. Job Cleanup

• Invalid jobs removed - Jobs without proper ID or jobCounter properties have been deleted from your workspace configuration.
  

What You’ll Need To Do After December 1

Immediate Actions Required:

1. Validate Your Workspaces

   • Load each of your Workspaces in Coalesce.

   • Commit any changes triggered by this update to Git via the Git Modal.

   • Verify that all Nodes are functioning as expected.

   • Test critical data pipelines to ensure proper operation.

2. Update Any Hardcoded References

   • If you have any external scripts or references that use the old node IDs or column IDs, these may need to be updated.

   • Review any custom integrations that might reference the modified elements.

Best Practices Moving Forward:

• Column Naming: Ensure column names are under 256 characters.

• Node Configuration: Always specify materialization types for SQL nodes.

• Job Management: Ensure all jobs have proper ID and counter properties.

• Schema Definition: Always specify database and schema values for sources.

Examples of Changes

Here are some examples of the types of changes you might see:

Column Name Length Fix:

# Before (invalid - too long) - name: "this_is_an_extremely_long_column_name_that_exceeds_the_maximum_allowed_length_of_256_characters_and_needs_to_be_truncated_or_renamed_to_comply_with_system_requirements_and_best_practices" 
# After (corrected) - name: "long_column_name_truncated"

Deploy Enabled Standardization:

# Before (undefined) node:   name: my_node   # deploy_enabled property missing
# After (defined)   node:   name: my_node   deploy_enabled: true

Nullable Property Addition:

# Before (missing nullable) columns:   - name: customer_id     dataType: NUMBER
# After (nullable defined) columns:   - name: customer_id     dataType: NUMBER     nullable: false 

Support and Documentation

Getting Help

If you encounter any issues or have questions about these changes:

1. Check the Problem Scanner - Use the built-in Problem Scanner in the Coalesce interface to identify any workspace issues

2. Contact Support - Reach out to your Customer Success Manager or submit a support ticket

Support Contact Information:

• Email: support@coalesce.io

Questions or Concerns?

We understand that any change to your development environment can be concerning. Our Engineering and Support teams have thoroughly tested this migration process, and we're confident that these changes will improve your experience with Coalesce.

If you have any questions, concerns, or encounter any issues, please don't hesitate to reach out to us. We're here to ensure a smooth transition.

Additional Resources:

• Coalesce Documentation

• Git Integration Guide

• Coalesce Support

Resolved an issue where the deployment plan could incorrectly generate ALTER statements to add columns that already existed in the target schema.

We've made backend improvements to boost system performance and reliability.

This release focuses on improving deployment reliability, user interface validation, and API consistency.

UI Enhancements

• Bulk Edit Validation Improvements – Added validation and error messaging when bulk editing columns in the column grid to prevent invalid input or missing selections. This ensures users receive clear guidance on required fields and attribute selections.

• Parser Sample Size Limit and Error Messaging – Updated JSON and XML parser settings to limit the sample size and provide more helpful error messages when exceeding recommended limits.

• Run Log Drawer Fix – Adjusted the layout so long Node lists no longer overlap the footer when filters or banners are active in the Run Log view.

API Updates

• Dynamic Table Node Creation – Fixed an issue where creating an empty dynamic table Node via the Create Workspace Node API failed due to incorrect validation. Dynamic table Node types can now be created, updated, and managed through all supported APIs.

• Duplicate Node Validation – Added validation to prevent creating Nodes with duplicate names or storage locations when using the Set Node API.

• Get Workspace Node Enhancements – The Get Workspace Node API now correctly returns database and schema values for mapped Nodes in workspaces, ensuring consistency with the UI.

Deployment and Execution

• Presync Column Query Truncation Fix – Resolved an issue that caused column metadata loss during large schema queries. The fix improves data integrity by correctly handling response size limits.

• Deployment Failure Due to Missing Subgraph IDs – Fixed an issue that caused deployment errors when subgraph or folder IDs were missing in request validation.

• Improved Plan Storage – Refactored Plan handling to no longer await storage completion during API operations, improving plan execution efficiency.

Problem Scanner

• Column Dependency Refresh Fix – The Problem Scanner now updates column dependency errors in real time after changes, without requiring a browser refresh. This improves accuracy and workflow speed when resolving column-level issues.

Packages

Dynamic Tables Package

• Version 2.1.3 - Removed all Iceberg-related code from the Dynamic Tables Package. Dynamic Iceberg table creation is now handled through the new Iceberg Package. This update also includes a minor fix that removes redundant sort order logic.

Iceberg Tables Package

• Version 3.0.0 — Introduced three new Dynamic Iceberg Table Node types to support Iceberg table workflows.

  • Dynamic Iceberg Table Work

  • Dynamic Iceberg Table Dimension

  • Dynamic Iceberg Table Latest Record Version

Streams and Tasks Package

• Version 2.4.1 — Added the Task DAG Create Root node type with new triggered task functionality. Fixed an issue where SIM and DSM node types did not correctly detect source information.

We've made backend improvements to boost system performance and reliability.

Updates

We’ve focused this release on UI clarity, smoother onboarding, and CLI updates.

UI Changes

• Clearer Join Error When a Source Is Missing — If you attempt to join to a source Node that doesn’t exist in Coalesce, the error message now explains exactly what’s missing and where to fix it.

Connections and Authentication

• Private Key Formatting Guidance — The Snowflake User Credentials screen now clarifies the expected private key format, reducing auth setup errors.

Onboarding

• Skip Steps 2 and 3 — You can now skip steps 2 and 3 of the Onboarding Wizard when you already have those items configured, speeding up project setup.

CLI Updates

• Readable Errors and Warnings — The Coalesce CLI now formats deployment errors and warnings for easier scanning during runs.

Bug Fixes

• Mixed JSON Key Types Could Drop Derived Columns — Resolved an issue where derived mappings omitted columns when JSON keys mixed data types.

• Environment Deletion via API — Fixed an error that prevented deleting Environments using the API.

• CLI Hang on Exit — Addressed a rare case where the CLI could hang after completing work.

• Required Metadata Discard Error — Fixed an error thrown when discarding required metadata updates.

Packages

Streams and Tasks Package

Introduced a newInsert Or Merge With Task Node type for the Streams and Tasks package.

• Enables developing a stream on top of a table, view, or external table.

• Adds an option to create a target table and insert or merge data from a source, with a task orchestrating the operation.

Other Updates For Streams and Tasks

• Added comprehensive metadata update checks in create templates.

• Fixed comment block parsing.

• Updated node definition default scheduler option to prevent predecessor validation issues.

Functional Node Types

Added comprehensivemetadata update checks to the create templates flow to prevent mismatches during template generation.

Dynamic Tables

• Timestamp field uses a transform when configured.

• Record versioning now supports integer columns.

• When multiple timestamp columns exist, only the first selected column is considered.

• Fixed an issue that caused the Workspace to stop responding when loading the Node right-side navigation, creating or editing columns, or creating new Nodes.

• Fixed an issue where commits could generate invalid YAML syntax because of incorrect indentation or missing escape characters in multi-line join statements.

 We've made backend improvements to boost system performance and reliability.

Bug Fix

We fixed an issue that caused deployments to fail when Subgraphs or Folders lacked required IDs. This issue would occur after successful plan generation but during the deployment validation phase. Deployments now run as expected.