Version 7.6.5

Updates

• A new locations.yml is part of commits. It contains the default storage location and a list of storage locations.

• You can now retry a Job from failure in the Coalesce app. When you retry a Job, the run details will have a link to the previous run.

• We’ve improved the error logging for the CLI.

• You can now extend and modify Packages.

Bug Fixes

• We fixed a bug where the API did not return the correct run URLs.

• We fixed a bug where if there were too many Hash columns, scrolling wasn’t enabled.

• We fixed a bug where users who were connected to a large number of workspaces weren’t able to login using OAuth.

• We fixed a bug where insert statements were being ran, despite a Snowflake network error.

Documentation

We’re launching a new documentation site! You can check it out at https://preview-docs.coalesce.io/docs/.

What can you expect?

• The week of September 29, 2024, Coalesce will implement the new site at https://docs.coalesce.io/docs. The documentation site URL is not changing.

• Some page URLs have changed and redirects have been created.

• We fixed a bug where large jobs were failing due to repeated processing of the same information.

• We’ve released CLI version 7.5.8
  
  

On September 5, 2024, Coalesce will begin enabling two upgrades for all organizations.

• Git Repo Format Upgrade is available now. Mandatory upgrades will start September 5, 2024 and expect to be complete by September 12, 2024.

• Role-Based Access Control (RBAC)

We encourage you to prepare for the changes by:

• Upgrade the CLI to the latest version.

• Have your organization's administrators enable the Git Repo Format Upgrade before the mandatory deadline.

• Optionally, contact support to enable the RBAC migration early.

• Review existing roles and understand the permissions they will have under the new system.

By preparing for these changes early, you can avoid unintended consequences, such as being unable to make commits until the upgrade is complete.

We encourage you to review our documentation for more details:

• Git Repo Format Upgrade

• RBAC Migration Guide

Contact our support team to start preparing.

Updates

This release includes performance improvements and bug fixes.

🛑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're excited to announce that Role-Based Access Control (RBAC) will be enabled for all Coalesce users on September 5, 2024.

RBAC enhances security by ensuring that users have only the access they need, reducing risks and simplifying permission management.

Organizations will be automatically upgraded on September 5, 2024, but if you'd like early access, please reach out to our support team. Take a look at our documentation to get started.

Review our RBAC Migration Guide to understand how these changes will affect your organization.

🛑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

• Coalesce

• LinkedIn

• YouTube

Bug Fixes

• This release includes performance improvements and bug fixes.

Bug Fixes

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

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.

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.