• Column Lineage now renders correctly.

• Fixed an issue where createdAt and updatedAt fields in and older version of packages caused deployment failures.

• Fixed issue where changes made to Nodes would not appear in Deploy and Refresh operations.

Deprecated node metadata changes were completed with the release of 7.15.

Previous posts

• March 13, 2025 - Upcoming Deprecated Node Metadata Changes

• March 3, 2025 - Deprecated Node Metadata Changes

• Minor internal bugfix to support user onboarding.

• The coa CLI will now display plan warning messages even if the plan was successfully created. This will help you identify any issues that come up before deployment.

• The /api/v1/environments/{environmentID}/nodes and /api/v1/workspaces/{workspaceID}/nodes endpoints now have pagination. You can use the following query parameters to organize your responses:

  • Limit - The maximum number of Nodes to return.

  • startingfrom - The cursor point for paging the query results.

  • orderBy - The field to order the results by.`

Version 7.15.1

• Turning off the multi-source toggle will now properly remove the additional source from the YAML file.

• [Object Object] no longer appears in the hash column.

• Column lineage will now display a loading spinner and will only render when column lineage is ready.

In our ongoing efforts to enhance performance and maintainability, we're removing some legacy metadata fields that are no longer needed.

This process is happening in two stages:

• Release 7.14 - Already completed ✅

• Release 7.15 - Coming soonCompleted on March 18, 2025 ✅.

What this means for you:

• No workflows will be disrupted.

• No data will be affected.

When doing a commit, you might see changes for Nodes that you haven’t modified. This is expected when deprecated metadata is removed. You will need to:

1. Making a commit with the changes.

2. Continue on with your workflow.

Example of a commit with metadata changes

Deprecated Properties Removed:

Deprecated fields in 7.15 will affect all Source Node Types regardless of age or activity status. These fields may still appear in our API, but are no longer used in the Node metadata.

• dataset

• table

• metadata.join

• metadata.sourceMapping - already absent from most sources

See our previous changelog post about the changes in 7.14.

AI-Generated Documentation: Automatic Descriptions for Nodes, Columns, and Git Commit Messages

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

Coalesce is introducing AI-generated descriptions for Node, Columns, and Git Commit messages.

By analyzing your data pipelines lineage and transformation metadata, it creates natural language descriptions. AI-generated descriptions streamlines documentation by creating clear explanations of data transformations and Git commits. Now you can focus on development while making sure your data pipelines are well documented.

Organization admins can opt-in by going to Organization Settings > Preferences and toggling AI Features.

Updates

• Run results, Column Headers now support numeric names, ensuring your data displays accurately.

• We've temporarily rolled back Workspace Onboarding based on valuable customer feedback. This change was made to ensure the best customer experience possible. We're working on improvements to deliver a refined version in the future. Sign up for our changelog email to keep to date.

Bug Fixes

• We fixed an issue where, when switching tabs in multi-source Nodes the incorrect join string was saved.

Version 7.14.3

Coalesce cleaning up deprecated metadata fields in Nodes. The change will improve data integrity across Coalesce. This will happen in two stages:

• Release 7.14

• Release 7.15

When doing a commit, you might see changes for Nodes that you haven’t modified. This is expected while deprecated metadata is removed. We suggest making a commit with the changes then continuing on with your workflow. Do not delete, edit, or modify the deprecated fields in any way.

Changes in Release 7.14

Deprecated fields in 7.14 will primarily affect older workspaces that haven't been accessed recently. For actively maintained workspaces, the impact should be minimal. However, if you attempt to commit against previously archived or long-dormant workspaces, you may encounter these changes.

Deprecated Properties Removed

The following properties will be completely removed if present:

Top-level column properties:

• ghostRecordValue

• descendedFrom

• hashColumns

• columnsForHash

Inside hashDetails object:

• hashType

• hubHashes

Properties corrected for Invalid Data

Properties set to empty string (""):

• dataType - if not a string type

• transform - if empty

Properties completely removed if invalid

• appliedColumnTests - if null

• config - if null

• hashDetails - if it's a string (should be an object)

Column Reference Fixes

Column Reference (columnReference)

• stepCounter - if null/undefined, set to the node's ID

• All IDs within column references are converted to strings (previously numbers were allowed - this change has been around for a long time)

Source Column References (sourceColumnReferences)

For each reference in the array:

• All IDs within column references are converted to strings

• stepCounter - if null/undefined, set to empty string ("")

Hashed Columns Fixes

For hashedColumns array:

• All IDs within column references are converted to strings

Upcoming Changes in Release 7.15

Deprecated fields in 7.15 will affect all Source Node Types regardless of age or activity status.

Deprecated Properties Removed:

• dataset

• table

• metadata.join

• metadata.sourceMapping - already absent from most sources