Release Orchestration
September 2026
Version 1.80.2
New features and enhancements
Service mappings in Artifact Tracker can now select upstream services from any scope, account, organization, or project, regardless of the scope where the mapping is created. Previously, an account-scoped mapping could only select upstream services at the account level, and an org-scoped mapping could only select from the account and org levels. Go to Map your services to configure a service mapping. (RM-1463)
The Select Activity Queue field in the Looping Strategy panel now accepts an expression in addition to a fixed Pipeline Queue activity, so the queue activity a loop reads from can be resolved at runtime. Go to the Looping strategy panel for details.
Fixed issues
Fixed an issue where output expressions could resolve against the wrong execution scope, which could return stale or incorrect output values to downstream activities. (RM-1434)
Version 1.79.1
New features and enhancements
Release Orchestration now supports moving processes, process inputs, and activities from inline to remote Git storage using a Move to Git action. Process inputs require the parent process to already be stored in Git. Go to Move inline entities to Git to configure this for a process, process input, or activity.
OPA policy evaluation is now supported when a release is run, allowing governance policies to differentiate between regular releases and ad hoc releases. Go to Harness Governance Overview to learn about on-run policy evaluation for Release Orchestration entities.
Fixed issues
Fixed an issue where a release-triggered pipeline execution ran under the internal service identity instead of the identity of the user who started the release, so environment-level RBAC restrictions were not enforced. (RM-1147)
Version 1.72.0
New features and enhancements
Activities now support looping over deployment targets. You can run a separate iteration for each target from a single activity definition, eliminating the need to duplicate activities for multi-environment or multi-region deployments. Go to Loop phases and activities to configure looping on a phase.
Input set variables can now be marked as read-only to prevent them from being overridden during execution. This gives process owners stronger control over runtime inputs.
Process, process input, and activity pages now display a banner when GitX webhook sync is not enabled. This makes it easier to identify and activate bi-directional Git synchronization.
Release process definitions now require owners and activities to be specified for every phase. This ensures consistent accountability and completeness across process templates.
Phase inputs can now be fetched using a release's human-readable slug identifier, making API access more consistent with other endpoints.
A new Looping Strategy panel is available in the phase and activity editor, making it easier to configure deployment targets for looping. Go to Looping strategy panel for details.
Phase re-run controls are now available. Users in a phase's user group can re-run or advance to the next phase. Manual activities in re-runnable phases can no longer be skipped.
OPA policy evaluation on save is now supported for release groups. This catches governance violations at configuration time rather than at execution. Go to Harness Governance Overview to learn about on-save policy evaluation for Release Orchestration entities.
Activity looping UI improvements include fixed row-click navigation and a streamlined targets configuration form.
Reduced redundant API calls when checking for artifact updates on paused phases, improving page load performance.
Fixed issues
Fixed an issue where a release activity would get stuck in "Running" indefinitely when the triggered pipeline was blocked by an OPA governance policy before any steps executed. Activities now correctly transition to a failed state. (RM-1356)
Fixed an issue where phase inputs were not loaded correctly when re-running a Process Direct Execution phase. (RM-1465)
Fixed an issue where slug resolution for process direct execution during phase re-runs failed. (RM-1486)
Fixed an issue where subprocess activities with keyed references would fail to execute correctly after a regression was introduced. These activities now execute as expected. (RM-885)
Fixed an issue where subprocess activities failed when referencing org-level processes. References are now resolved correctly across process scopes. (RM-1247)
Security updates
Updated an underlying HTTP framework component to address CVE-2026-55677.
August 2026
Version 1.70.0
New features and enhancements
Releases and process executions now show who triggered them, with user name and avatar displayed in the releases table, release details, and execution views.
When a phase is paused, Release Management automatically checks for newer release artifact tags and shows a warning banner when updates are available. Hover over phase inputs to see current artifact tags at a glance.
Fixed governance policy metadata timestamps so created and updated dates display correctly in release governance views.
Fixed issues
Fixed an issue where the edit activity form could unexpectedly reset or lose changes while editing an activity. (RM-1002)
Fixed an issue where starting a release could leave inconsistent state if pipeline plan creation failed. Database changes are now rolled back when plan setup fails, and concurrent release starts are coordinated to prevent race conditions. (RM-1311)
Version 1.68.0
New features and enhancements
Phases can now pause when that option is enabled, then be resumed or restarted without starting the release over.
Semantic versioning can be turned on by default and overridden per service, so "previous artifact" follows version order instead of just the latest timestamp. Go to Get Started with Artifact Tracker and Changesets to configure semantic versioning.
Phase and activity outputs can now be given types and edited inline in a table, so output definitions stay structured and easier to maintain.
Fixed issues
Orchestration pipeline activities now detect completion from the execution record, so releases no longer stall after a pipeline has already finished. (RM-1293)
Last updated
Was this helpful?