Skip to main content

Release Notes November 2026

Orchestrators​

The below Orchestrators release notes provide information about new features and updates in the pre-release version 5-latest. These updates are set available as an opportunity to test and validate that things work as expected in your environment before we promote them to the official release 5-stable.

To test orchestrators with 5-latest, simply set DATAOPS_RUNNER_IMAGE_TAG to 5-latest in your project's variables.yml configuration file. See Orchestrators Pre-Release Versions for more information.

Feature release status badge: Feature
Feature
dbt 1.12 Support​

Added support for dbt 1.12 in MATE, across all orchestrators, using the latest compatible third-party package versions. To use it, set DATAOPS_FEATURE_MATE_DBT_VERSION to 1.12 in your project's variables.yml.

Feature release status badge: Improvement
Improvement
dbt 1.11 Is Now the Default dbt Version​

The default dbt version used by all orchestrators has been upgraded from dbt 1.7 to dbt 1.11.

If your project relies on the default and isn't ready to move, pin your current version by setting DATAOPS_FEATURE_MATE_DBT_VERSION: "1.7" in your project's variables.yml. See Switching dbt version for more information.

Feature release status badge: Bug Fix
Bug Fix
Borrowed Environment Detection in SOLE​

Fixed how SOLE detects that a branch is borrowing another environment's objects. SOLE now compares DATAOPS_NONDB_ENV_NAME with DATAOPS_ENV_NAME instead of matching the branch name against the fixed DEV, PROD, and QA set. The two values differ only when a branch is borrowing, so branches that genuinely are the DEV, QA, or PROD environment keep management of their own objects, regardless of how the branch is named.

The protection against a borrowing branch managing objects that belong to another environment is now always on. It no longer requires DATAOPS_ENABLE_BEHAVIOR_CHANGE_BUNDLE to be set to 2023_08. No configuration changes are required.

Feature release status badge: Improvement
Improvement
Clearer Error for an Incorrect Snowflake Key Pair Passphrase​

When Snow CLI can't decrypt a private key, it reports Incorrect password, could not decrypt key. This reads like an account password rejection, even though it's a different failure with a different fix. The Snowflake and SnowflakeObjectLifecycle orchestrators now append a clarifying note whenever this message appears. The note points you to DATAOPS_SNOWFLAKE_PASSPHRASE and DATAOPS_SNOWFLAKE_KEY_PAIR, so key pair issues are no longer mistaken for account password errors.

Feature release status badge: Bug Fix
Bug Fix
Security Updates​

This release includes updated dependencies across the orchestrator images to remediate vulnerabilities identified by our automated security scanning, including high and critical severity findings in the SnowflakeObjectLifecycle, Reporting, and R orchestrators