Product Updates

Upgrade Your Git Repo

by Coalesce
Action Required

On September 5, 2024, Coalesce will enable the Git Repo Format Upgrade . After September 5, 2024, all Git repos will be automatically updated.

What is the Git Repo Format Upgrade?

We have updated the way files are committed into Git. Previously it was split into a data.yml and the specific nodes.yml files. Now you can see the changes for:

  • Node Types

  • Environment Mappings

  • Subgraphs

  • Jobs

  • Macros

  • Packages

The upgrade is required for Packages and CLI use.

How to Opt-In

Organization Administrators can turn it on for the whole organization. Go to Org Settings > Preferences and Enable Git Repository Format Update. Once enabled, all Workspace users will be prompted to switch to the new format. They won't be able to make commits until they switch to the new format.

  • Users will be notified the upgrade is available, but won't be able to upgrade.

  • Previously committed metadata can still be deployed after the upgrade.

Packages

You must be using the new Git Repo Format Upgrade to use Coalesce Packages.

CLI

If you use the CLI and HAVE NOT upgraded to the new Git Repo Format, you have until September 5, 2024 to upgrade your CLI. After September 5, 2024, the Git Repo Format Upgrade will be turned on for all Coalesce organizations and any CLI versions below 7.0.18 won't be compatible with Coalesce versions 7.2.x and above.

If you have upgraded to the new Git Repo Format and use the Coalesce CLI, please upgrade your CLI version to prevent interruptions in workflow.

Dhaulagiri 7.3.7

by Coalesce
Preview

These features are in private preview. Learn more about Private Preview.


Bug Fixes

  • We fixed an issue where organizations with a large number of Snowflake OAuth secrets couldn't save them.

  • This release includes performance improvements and bug fixes.

Preview Dhaulagiri 7.3.6

by Coalesce
Preview

These features are in private preview. Learn more about Private Preview.


This release includes bug fixes and performance improvements.

Preview Dhaulagiri 7.3.5

by Coalesce
Preview

These features are in private preview. Learn more about Private Preview.


Bug Fixes

  • We fixed an issue where when adding source tables, not all tables were available.

  • We fixed an issue where Docs were loading slowly.

  • We fixed an issue where surrogate key wasn't being rendered in Nodes.

Preview Dhaulagiri 7.3.4

by Coalesce
Preview

These features are in private preview. Learn more about Private Preview.


  • This release includes performance improvements and bug fixes.


Preview Dhaulagiri 7.3.3

by Coalesce
Preview

These features are in private preview. Learn more about Private Preview.


  • This release includes performance improvements and bug fixes.


Preview Dhaulagiri 7.3.2

by Coalesce
Preview

These features are in private preview. Learn more about Private Preview.


Bug Fixes

  • We fixed an issue where coa deploy would fail on Windows.

Preview Dhaulagiri 7.3.1

by Coalesce
Preview

These features are in private preview. Learn more about Private Preview.


Bug Fixes

  • Fixed an issue where the Coalesce app would throw an error if a View node had no columns in deployment.

  • Improved CLI logging for when coa plan fails.

Preview Dhaulagiri 7.3.0

by Coalesce
Preview

These features are in private preview. Learn more about Private Preview.


RBAC (Role Based Access Control)

We’re testing Role-Based Access Control (RBAC) to enhance security and streamline user management across our platform. This security enhancement requires users to perform secondary verification to gain access to their accounts, significantly increasing account security.

Take a look at our RBAC documentation.

Git Merge Conflicts Improvements

We’re testing our Merge Conflicts workflow. Now you can clearly see which lines need to be reviewed, move between each conflict easily, and can decide to keep or reject changes with the click of a button.

Take a look at our Merge Conflicts documentation.

Bug Fixes

  • We fixed an error where clicking on Column Lineage caused the page to not respond.

  • We fixes an issue where a the Refresh status indicator would keep spinning, even if the Refresh was canceled.