Product Updates

Version 7.4.3

by Coalesce
New
Action Required
Updates

🛑Action Required🛑

Git Repo Format Upgrade must be completed by September 5, 2024.

On September 5, 2024, Coalesce will enable the Git Repo Format Upgrade for all existing customers.

As part of the upgrade, you’ll need to upgrade your CLI and enable the Git Repo Format Upgrade. Review our announcement to learn more.


We’ve released Version 7.4.3

New

Edit Nodes API

We’ve released three new endpoints that allow you to manage Nodes in your Workspaces.

  • List Nodes - Returns a list of all the Nodes in a Workspace.

  • Get Node - Returns information about a single Node.

  • Set Node - Edit existing Nodes in a Workspace.

Refresh Jobs

You can now run existing Jobs in the Coalesce App. 


Updates

  • We’ve updated our Git integration to better handle sync and validation errors.

  • We’ve improved the speed of the Build page for large data pipelines.

Bug Fixes

  • We fixed a bug where you couldn’t clear multiple sources using the Bulk Editor.

  • We fixed an issue where users received an error about uncommitted changes when updating from the remote repository, despite not making any changes.

  • We fixed a bug where not all tables were available when adding a source.

  • We fixed an issue where Docs were slow to open.

  • We fixed a bug where Node descriptions that were null wouldn't deploy.

Find Us Online


Version 7.3.11

by Coalesce
Bug Fix

Bug Fixes

  • This release includes performance improvements and bug fixes.

Version 7.3.10

by Coalesce
Bug Fix

Bug Fixes

  • We fixed an issue with validation for tabular config items.


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.

Coalesce Not Affected by Global CrowdStrike Outage

by Coalesce
Announcement

The global IT issues caused by CrowdStrike while widespread are not currently affecting Coalesce's systems. Coalesce does utilize CrowdStrike but this issue is isolated and not affecting our production cloud infrastructure. We are continuously monitoring our systems and are available via support for any questions.

Dhaulagiri 7.2.13

by Coalesce
Bug Fix

Bug Fixes

This release includes performance improvements and bug fixes.

Dhaulagiri 7.2.12

by Coalesce
Bug Fix

Bug Fixes

This release includes performance improvements and bug fixes.

Dhaulagiri 7.2.11

by Coalesce
Bug Fix

Bug Fixes

This release includes performance improvements and bug fixes.

Dhaulagiri 7.2.10

by Coalesce
Bug Fix

Bug Fixes

  • We fixed a bug where Git Resyncs would show there were uncommitted changes even if all changes had been committed.

  • We fixed a bug during Presync (Plan) where columns in the data warehouse weren’t being detected on large data sets.