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.