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

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.

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.

Node.js Version Support Has Been Updated for the Coalesce CLI

With version 7.24, we have updated the supported Node.js versions for the coa CLI to ensure you are working in a stable and secure environment.

What has changed?

The coa CLI now supports the following Node.js versions:

• 20

• 22

• 24

Support for Node.js version 18 has been removed.

Why We Made This Change

We removed support for Node.js version 18 because it is approaching its end-of-life. We have added support for version 24, a Long-Term Support (LTS) version, to ensure continued stability and security.

Action Required

If you are running Node.js version 18, you must upgrade to a supported version (20, 22, or 24) to continue using the coaCLI. If you attempt to use the CLI with Node.js 18, it will exit with an error message stating that the version is not supported.

Metadata Updates

Coalesce has introduced updates to improve metadata integrity across Nodes. In this release, null values in Node metadata are automatically removed.

When you commit changes, you may notice updates to Nodes that you haven’t directly modified. This is expected, since null fields are being removed. You should commit these changes and continue with your workflow.

What to Expect

• Git Modal: You may see diffs in the git modal where null values are removed.

No additional action is required. Commit the changes when they appear to keep your project in sync.

Updates

We’ve made a series of improvements focusing on UI consistency and run visibility.

UI Changes

• Improved Display of Long Storage Location Names - Long storage location names in your build settings are now shortened to fit the screen. You can hover over the shortened name to see the full name in a tooltip.

• Updated the "Re-Sync Source Columns" Window - We've updated the style of the "Re-sync Source Columns" window to match the rest of the application. It now provides a clearer message when there are no changes to sync.

• Improved the "Delete Column" Confirmation - When you delete one or more columns, the confirmation window now clearly lists the columns you are about to delete. This helps you confirm your changes before they are made.

• Updated Git View After Commit – The Git window has been improved so that after a successful commit and push, the view now clears automatically to show "No Files To View" This provides clearer feedback and ensures the view reflects the current state of your repository."

Run Updates

• Added a "Rendering" Status for Runs - When you start a run, you will now see a "Rendering" status indicator. This provides better visibility into the run process, especially for large jobs that take time to render SQL before execution.

• Added Tooltips to Run Details Page - On the Deploy and Refresh Runs page, you can now hover over truncated node names and error messages to see the full text in a tooltip.

• Redesigned the Run Stage Details Window - We've redesigned the window that shows the details for a run stage. The new design makes it easier to read long SQL queries and error messages, with a wider layout and resizable panels.

Git Updates

• Better Error Handling for Existing Git Branches - When creating a new workspace, you will now see a clear error message if the Git branch name you entered already exists, allowing you to choose a unique name.

Package Updates

Base Node Types – Advanced Deploy

• Added comprehensive metadata update checks for Advanced Deployment Templates.

• Fixed block comment issue for metadata update.

Streams and Tasks

• Delta Stream Merge updates:

  • Dual merge logic implemented.

  • Redeployment behavior added for column schema changes.

  • External Table and External Iceberg Table supported as source objects.

  • Deployment phasing introduced.

• Create Templates:

  • Added comprehensive metadata update checks.

  • Fixed comment block parsing.

  • Fixed default scheduler in node definition.

Running Nodes created with any version 2.2.0 and below without adding table key and partition key config options can cause rendering errors.

Create or Alter

• Added comprehensive metadata update checks for Create Templates.

• Fixed comment block parsing.

• Fixed view issues caused by join changes.

External Table

• Partitioning logic updated.

A default column PARTITION_COLUMN is added with the transformation:

split_part(metadata$filename, '/', 2) 

You can rename this column or adjust the transformation. You can also use another column with the right transformation for partitioning.

Bug Fixes

• Prevented Deployments with Empty Column Names - To prevent errors, you can no longer deploy Nodes that have columns without names. The application will now show an error message, "Empty Column Names, during the deploy plan, prompting you to name all columns before deploying.

• Fixed Drag-and-Drop for Jobs and Subgraphs - We fixed an issue where dragging and dropping nodes into a second or third Job or Subgraph would not work. You can now reliably add nodes to any Job or Subgraph using drag-and-drop.

• Fixed Workspace Loading for Nodes with Invalid Configurations - We resolved an issue that prevented workspaces from loading if a node had an invalid configuration value. The application now automatically corrects these values to ensure your workspace always loads correctly.

• Fixed Resizing of Include/Exclude Filters - We fixed a bug where the include and exclude filter boxes in the browser would shrink unexpectedly after being resized. Both filter boxes now resize correctly.

Coalesce has introduced updates to improve metadata integrity across Nodes. Starting in the 7.24 release, null values in Node metadata are automatically removed.

When you commit changes, you may notice updates to Nodes that you haven’t directly modified. This is expected, since null fields are being removed. You should commit these changes and continue with your workflow.

What to Expect

• Git Modal: You may see diffs in the git modal where null values are removed.

No additional action is required. Commit the changes when they appear to keep your project in sync.

Node.js Version Support Has Been Updated for the Coalesce CLI

With version 7.24, we have updated the supported Node.js versions for the coa CLI to ensure you are working in a stable and secure environment.

What has changed?

The coa CLI now supports the following Node.js versions:

• 20

• 22

• 24

⚠️ Support for Node.js version 18 has been removed.

Why we made this change

We removed support for Node.js version 18 because it is approaching its end-of-life. 5We have added support for version 24, a Long-Term Support (LTS) version, to ensure continued stability and security. 6

Action Required

If you are running Node.js version 18, you must upgrade to a supported version to continue using the coa CLI. After updating to release 7.24, running the CLI with Node.js version 18 will cause the CLI to exit with the following error message:

Invalid node version 18 not supported

Updates

We’ve made a series of improvements focusing on UI consistency, run visibility, and Git.

UI Changes

• Improved Display of Long Storage Location Names - Long storage location names in your build settings are now shortened to fit the screen. You can hover over the shortened name to see the full name in a tooltip.

• Updated the "Re-Sync Source Columns" Window - We've updated the style of the "Re-sync Source Columns" window to match the rest of the application. It now provides a clearer message when there are no changes to sync.

• Improved the "Delete Column" Confirmation - When you delete one or more columns, the confirmation window now clearly lists the columns you are about to delete. This helps you confirm your changes before they are made.

• Updated Git View After Commit – The Git window has been improved so that after a successful commit and push, the view now clears automatically to show "No Files To View" This provides clearer feedback and ensures the view reflects the current state of your repository."

Run Updates

• Added a "Rendering" Status for Runs - When you start a run, you will now see a "Rendering" status indicator. This provides better visibility into the run process, especially for large jobs that take time to render SQL before execution.

• Added Tooltips to Run Details Page - On the Deploy and Refresh Runs page, you can now hover over truncated node names and error messages to see the full text in a tooltip.

• Redesigned the Run Stage Details Window - We've redesigned the window that shows the details for a run stage. The new design makes it easier to read long SQL queries and error messages, with a wider layout and resizable panels.

Git Updates

• Better Error Handling for Existing Git Branches - When creating a new workspace, you will now see a clear error message if the Git branch name you entered already exists, allowing you to choose a unique name.

Bug Fixes

• Prevented Deployments with Empty Column Names - To prevent errors, you can no longer deploy Nodes that have columns without names. The application will now show an error message, "Empty Column Names, during the deploy plan, prompting you to name all columns before deploying.

• Fixed Drag-and-Drop for Jobs and Subgraphs - We fixed an issue where dragging and dropping nodes into a second or third Job or Subgraph would not work. You can now reliably add nodes to any Job or Subgraph using drag-and-drop.

• Fixed Workspace Loading for Nodes with Invalid Configurations - We resolved an issue that prevented workspaces from loading if a node had an invalid configuration value. The application now automatically corrects these values to ensure your workspace always loads correctly.

• Fixed Resizing of Include/Exclude Filters - We fixed a bug where the include and exclude filter boxes in the browser would shrink unexpectedly after being resized. Both filter boxes now resize correctly.

Package Updates

Base Node Types – Advanced Deploy

• Added comprehensive metadata update checks for Advanced Deployment Templates.

• Fixed block comment issue for metadata update.

Streams and Tasks

• Delta Stream Merge updates:

  • Dual merge logic implemented.

  • Redeployment behavior added for column schema changes.

  • External Table and External Iceberg Table supported as source objects.

  • Deployment phasing introduced.

• Create Templates:

  • Added comprehensive metadata update checks.

  • Fixed comment block parsing.

  • Fixed default scheduler in node definition.

Running Nodes created with any version 2.2.0 and below without adding table key and partition key config options can cause rendering errors.

Create or Alter

• Added comprehensive metadata update checks for Create Templates.

• Fixed comment block parsing.

• Fixed view issues caused by join changes.

External Table

• Partitioning logic updated.

• A default column PARTITION_COLUMN is added with the transformation:

  split_part(metadata$filename, '/', 2)

You can rename this column or adjust the transformation. You can also use another column with the right transformation for partitioning.

Update to Supported Node.js Versions for the Coalesce CLI

Starting with the 7.24 release, we are updating the supported Node.js versions for the coa CLI to ensure you are working in a stable and secure environment.

What's Changing?

The coa CLI will now enforce the use of the following Node.js versions:

• 20

• 22

• 24

⚠️ Support for Node.js version 18 will be removed.

Why We're Making This Change

We're removing support for version 18 because it reaches its end-of-life in April 2025. Support for version 24, a Long-Term Support (LTS) version, has been added to ensure continued stability and security.

Action Required

If you are running Node.js version 18, you must upgrade to a supported version to continue using the coa CLI. After updating to release 7.24, running the CLI with Node.js version 18 will cause the CLI to exit with the following error message:

Invalid node version 18 not supported

Updates

• Column lineage - We’ve improved the process by adding in app guidance and improving the visual indicators making it easier to see the propagation before commiting.

• Snowflake Authentication - The Problem Scanner now alerts you when Snowflake authentication is missing.

• Subgraphs and Jobs

  • The process for creating a Job or Subgraph is now easier. Enter a name in the modal, click Create, and you’ll be taken straight to your new Job or Subgraph.

  • We alert you in the Problem Scanner for duplicate Subgraph or Job names.

  • Previously, when a was Node was added or removed from a Subgraph it would be done silently. Now we let you know it was successful or failed along with either the Node name or number of Nodes.

Bug Fixes

• When editing user roles, the role summary shows in the dropdown correctly.

• Testing a Databricks SQL Warehouse connection will no longer fail with a "Missing token" error when a valid token has been entered.

• Service accounts with Environment Admin permissions for Snowflake environments will no longer receive an "Invalid Connection Information" error on API calls.

• Deploying a Storage Mapping change will no longer result in a "No schema found" error if the old schema or database was deleted directly from the data warehouse before deployment.

• Deleting a source from a column now works consistently when using a trackpad or a mouse.

• Sorting and filtering by Node Status or Stage Status on the deployment runs page will no longer revert or disappear on runs with a large number of objects.

• Deleting a Source Node and creating a new table Node with the same name and location in a single deployment will no longer replace the existing table and cause data loss.

New API Endpoints: User Management & Git Accounts

We're excited to announce the addition of User Management API and Git Account API endpoints.

User Management

Automate user provisioning workflows, implement bulk role assignments, and manage permissions across organizations, projects, and environments programmatically.

Review the User Management API documentation.

Git Accounts

Programmatically configure Git connections, manage account credentials, and maintain Git repository associations as part of your CI/CD pipelines.

Review the Git Accounts API documentation.

Updates

We’ve continued to improve the user experience by:

• Adding alphabetical sorting for Storage Locations and Environments.

• Sorting the Nodes Panel alphabetically while also considering the Storage Location name. For example, if both Nodes are named analytics_source, the one with the Storage Location of SRC would come before the one with TGT.

Packages

• Snowflake Deferred Merge Package v2.0.0 - Now correctly adds and removes deploy phases at the appropriate stages.

• Snowflake Iceberg Tables package v2.0.0 – Fixes issues with removing deploy phases at the right stages.

Bug Fixes

• When zoomed in, the Add Member button in the Project settings no longer disappears.

Private Preview Features

These features are currently in Private Preview. Please reach out to your Coalesce account manager to sign up.

Onboarding Wizard

The Onboarding Wizard is back—and better aligned with your needs. This step-by-step setup guides you through authentication and storage configuration so you can spend less time on setup and more time building pipelines.

Your Feedback in Action

• Storage & Mapping Optional on Duplication: When you duplicate a Workspace, you can now skip Storage Location configuration and Storage Mapping entirely—no need to fill them in unless you want to change them.

• Existing Commits: If you’re branching off an existing Workspace with mappings already in your repo, the Onboarding Wizard will automatically pull in those Storage Locations and Storage Mappings for you.

• Auto-Populate Existing Settings: If your original Workspace already had Storage Locations or Storage Mappings, we’ll carry those over automatically so you don’t have to reconfigure.

Why You’ll Love It

These tweaks remove unnecessary clicks when duplicating a Workspace and ensure your existing settings stick—giving you a seamless transition every time.

Deploy Wizard Improvements

We’ve refined the Deploy Wizard to give you clearer visibility into errors and warnings during the Review Plan step. Now, issues are organized into separate Errors and Warnings tabs—so you can quickly zero in on what needs fixing before you deploy.

Updates

• We've improved the display of Projects and Environments with long names on the Deploy Page to make it easier to filter:

  • Selected environments in the filter now show their full names instead of project-name combinations.

  • Hover tooltips now appear in both the dropdown list and selection textbox to show full names when they're cut off.

  • The “×” remove button is now consistently visible on all selected filter tags, even when their labels are truncated. This ensures users can always remove applied filters without needing to hover or expand the text.

• Syntax highlighting was added to the Parameter pages, making it easier to spot errors and understand the code structure at a glance.

• A next parameter has been added to the List Runs endpoint response, making it easier to track your position while paginating through results.

• Improved support for systemColumns in Node endpoints:

  • The Get Workspace Node endpoint now includes all systemColumns attributes in its response.

  • The Set Workspace Node endpoint has been updated to preserve existing systemColumns attributes when updating a Node.

  • System columns were added to the metadata.column .

Bug Fixes

• Fixed incorrect error message when making change tracking configuration required in UDNs. The message now correctly states "Please select a change tracking column."

• Previously, users were incorrectly prompted to upgrade already-upgraded repositories. Coalesce now properly verifies Git commits and provides clear error messages when Git account testing is needed.

• Environments no longer get stuck in a "Refreshing" state when no jobs are actively running.

• Long Azure DevOps PR descriptions now properly truncate before being included in commit messages, preventing SQL compilation errors during deployment.