We fixed an issue where certain read-only editor fields could incorrectly be editable.

Bug Fixes

• Fixed an issue where certain read-only editor fields could incorrectly be editable

• Fixed an error preventing environments with large node counts from being deleted via API

• Fixed an issue where nodes with null values caused blocking errors

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.

We fixed an issue where Environments with a large number of Nodes couldn’t be deleted using the API.

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.

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.

Bug Fixes

• 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.

We fixed a bug where the Node API endpoint would sometimes return a 500 error when using the ?detailsquery parameter.

• We fixed a bug where viewing column lineage would intermittently fail.

• Retrying a job from its point of failure now allows the job to run successfully.

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.