This release includes bug fixes and performance improvements.

Version 7.13.1

New Workspace Onboarding

Setting up Workspaces in Coalesce just got easier. Our new Workspace onboarding guides you through the processes step-by-step reducing configuration time. Workspace onboarding makes it easier to set up version control, authentication, and Storage Locations/Mappings. This means less setup time and more focus on building pipelines.

Updates

• Our Hash editor automatically displays all columns with proper scrolling functionality.

• Problem Scanner can detect and alert on duplicate Node names and Storage Mappings, making it easier to find potential problems.

• We've made several improvements to enhance platform speed and reliability. These changes are part of our ongoing commitment to deliver the best possible experience for our users.

Bug Fixes

• Source filters now correctly populates and displays all available results.

• Fixed an issue where, “A write batch can no longer be used after commit() has been called.”, was returning when trying to checkout branches.

• Node column details in the lower-left corner now consistently display when clicking Nodes. 

• Node Editor scrolls correctly when the “Node not enabled for deploy” banner is displayed.

Coalesce will be taking a scheduled maintenance window. During this time, search functionality within the generated documentation pages will be temporarily unavailable.

Maintenance Details:

• Date: Monday, February 17, 2025

• Time: 8:00 PM - 10:00 PM US/Pacific

We are performing this maintenance to enhance the stability and performance of our platform. We expect search services to be fully restored by 10:00 PM PST, but will notify users if there are any delays or updates.

The rest of the platform will remain fully operational during this time.

We appreciate your understanding and apologize for any inconvenience this may cause. If you have any questions or concerns, please feel free to reach out to our support team.

This release includes bug fixes and performance improvements.

Updates

• Project Architects and Project Contributors can now delete Workspaces in any projects they are part of.

• Our Join string editing capability now saves correctly when rapidly switching between multi-source nodes.

• Our Hash editor automatically displays all columns with proper scrolling functionality.

Reminder

Keep your CLI up to date to ensure access to the latest features, bug fixes, and security enhancements. Run`npm upgrade -g @coalescesoftware/coa` or download the latest version on NPM.

The previously reported issue affecting users on coa version 7.5.8 and below has been resolved.

• No immediate action is required for users on older versions.

• The fix maintains backward compatibility across versions.

• While older versions are now supported, we recommend updating to the latest version of coa when possible.

Command line users on version 7.5.8 or below should upgrade to coa version 7.10.2 immediately.

Users on`coa` version 7.5.8 and below may encounter deployment and refresh errors. The issue occurs with the presence of`platformKind:snowflake` in the data.yml.

To fix any critical deployment or refresh issues:

• Upgrade to coa version 7.10.2 as soon as possible to prevent further issues.

If you are unable to upgrade your coa version and need to deploy immediately:

• Check your commits for platformKind:snowflake in the data.yml file.

• Manually remove the platformKind:snowflake and commit the changes.

• Deploy as normal

We are working on a change to be delivered within the next 24 hours to allow backwards compatibility for older versions of coa as to not disrupt operations.

New

You can now add a "Re-Sync Columns" button to custom Nodes. This feature allows users to sync columns that are not part of a source Node. Learn more in Custom Node Types.

Updates

We’ve made updates to product feature speed.

Updates

• We’ve made it easier to manage SSO users that have been disabled or deleted.

Bug Fixes

• We resolved an issue in graph execution during deploys where changes to indirectly dependent nodes could result in failed deployments due to incomplete lineage evaluation. The deploy process now accurately accounts for the full dependency lineage of views, ensuring proper ordering of drop and add phases, even when gaps exist in the runtime graph. This fix enhances reliability and reduces the need for redeployments to resolve dependency conflicts.

• We fixed an issue where deploys for advanced deploy node types generated duplicate SQL, causing extra stages to run. SQL is now correctly generated for each stage, improving deployment efficiency and accuracy.

• We fixed an issue where trying to deploy returned an error that Node type does not exist.