Combined DevOps Change Velocity release notes for upgrades from Yokohama to Australia

  • Release version: Australia
  • Updated May 4, 2026
  • 13 minutes to read

    • Consolidated page of all release notes for DevOps Change Velocity from Yokohama to Australia.

    How to use this page

    To help you prepare for your upgrade, we have combined the cross-family DevOps Change Velocity release notes onto one page. Read this summary of the new features, changes, and updated information for your product from Yokohama to Australia.

    Tip:
    If there were no updates for a release notes section in a certain family release, we included a short note for your reference. For example, if a product did not have any updates in Tokyo, the row says "No updates for this release."

    Important information for upgrading DevOps Change Velocity to Australia

    Before you upgrade to Australia, review these pre- and post-upgrade tasks and complete the tasks as needed.

    Release Release notes

    Yokohama

    If you are a new customer or are using a zBoot instance and you want to create type-based workflow change requests in DevOps Change Velocity, you must add the com.snc.change_management.change_model.type_compatibility property and set it to True. For more information, see Add a system property.

    If you are an upgrading customer, you must run the ReConfigure Bitbucket Server Repositories for PullRequest job to re-configure your existing Bitbucket Server or Bitbucket Data Center repositories so that pull request records can be imported. You can navigate to All > System Definition > Scheduled Jobs to search for this job and run it.

    Zurich

    		 No updates for this release.

    Australia

    		 No updates for this release.

    New features

    Between your current release family and Australia, new features were introduced for DevOps Change Velocity.

    Release Release notes

    Yokohama
    Harness integration
    Discover Harness pipelines and configure real-time notifications to enable change traceability and automation by integrating the Harness orchestration tool with DevOps Change Velocity.
    DevOps Health instance scan
    Detect anomalies and issues in the instance by running or scheduling health scans on your DevOps Change Velocity instance.
    Bitbucket Cloud tool integration with ServiceNow
    Integrate the Bitbucket Cloud coding tool with DevOps Change Velocity to connect, discover, import, and process real-time repository events in DevOps Change Velocity.
    DevOps Change Workspace UI for simplified creation of custom tool integration with planning, coding and orchestration capabilities
    Integrate a new custom tool across planning, coding and orchestration capabilities with basic know-how of ServiceNow using an intuitive DevOps Change Workspace UI. It offers easy navigation to the ServiceNow Platform for defining transformer or adapter rules, or integrate the ability to do so within the Workspace wherever applicable, and embeds necessary documentation links and tooltips to support self-service.
    Import based evidence collection
    Improve instance efficiency by skipping step-level pipeline processing for accelerated change management and evidence collection for GitHub Actions, Azure DevOps (ADO), GitLab and  Jenkins orchestration tools.

    Zurich
    Import based evidence collection
    Improve instance efficiency by skipping step-level pipeline processing for accelerated change management and evidence collection for GitHub Actions, Azure DevOps (ADO), GitLab and  Jenkins orchestration tools.

    Australia

    		 No updates for this release.

    Changes

    Between your current release family and Australia, some changes were made to existing DevOps Change Velocity features.

    Release Release notes

    Yokohama
    Simplified onboarding of orchestration tools not supported in the base system
    Integrate orchestration tools that aren’t supported in the base system by leveraging a generic framework.
    Custom fields for planning tool integration
    Add custom fields into your planning tool integration to improve configurability and access business-specific information, which facilitates more informed decision-making.
    Additional scans for DevOps Health Scan Content pack
    Additional set of proactive checks focused on problems that tend to occur before or after an upgrade along with identifying configuration issues like plugin and version incompatibilities, or pipelines that chronically fail, have been added.
    Import pull-request records for Bitbucket Server or Bitbucket Data Center
    Import pull-request records for Bitbucket Server or Data Center for improved insights and efficiency.
    Change request creation with errors in DevOps data retrieval for Harness pipelines
    Enable change request creation even if there is an error in retrieving the DevOps data for a Harness pipeline.
    Branch name filter
    Search for build numbers by the branch name while associating DevOps data to a change request in the Service Operations Workspace (SOW) or Classic UI.
    Test summary name in GitHub Actions
    The servicenow-devops-test-report custom action in GitHub now includes an optional test-summary-name parameter to specify the test summary results name.
    Token based authentication for Rally
    Configure webhooks for Rally using token based authentication instead of using the integration username and password.
    Renamed variables for Docker
    The environmental variables in the Generic Docker actions for DevOps Change Velocity have been renamed by removing the CI prefix for better clarity.
    Security scan results
    Security scan results on the change record associated to a pipeline execution with a linked package are now displayed in the Security Summaries tab.
    Source of commits in SOW
    View the source of commits like pipeline execution, branch, repository, and so on for a change request in the DevOps data section of the Service Operations Workspace.
    Track file changes
    The Track file changes option is now disabled by default when a repository is configured to prevent any potential security risks.
    Close code value for a change request
    Two new properties have been added in DevOps Change Velocity, so that you can specify a close code value for a change request based on the change request completion state when the autoCloseChange parameter is enabled.
    Support for MID Server cluster
    Improve load balancing and failover protection by selecting a MID Server cluster when connecting to a tool instance associated with a MID Server cluster. This configuration enables multiple MID Servers with relevant capabilities to be grouped.
    Improved UX for DevOps Change health scans
    Run health scans and analyze findings efficiently in the DevOps Change workspace with an intuitive and user-friendly interface.
    Pipeline association for GitHub Actions
    When onboarding GitHub Actions pipelines through the App onboarding catalog or the onboarding APIs, now only the selected pipelines are associated with the DevOps app. If no pipeline is selected, all pipelines within the specified repository are associated.
    Tool connection check status
    If a tool is marked as Disconnected because of a system-generated failure during an unsuccessful connection check, any subsequent successful check automatically updates the connection status to Connected. If you manually disconnect the tool, the tool status remains Disconnected even if there’s a subsequent successful connection check.
    New roles for vulnerability integration
    • The sn_vul.app_sec_manager role is added to the DevOps Tool Owner [sn_devops.tool_owner] role when the DevOps Vulnerability Integrations plugin (sn_devops_vul_ints) is installed.
    • The sn_vul_veracode.configure_integration role is added to the DevOps Tool Owner [sn_devops.tool_owner] role when the Vulnerability Response Integration with Veracode plugin (sn_vul_veracode) is installed.
    Prod deploy commit logic for other step types
    Update the sn_devops.commit_rel_change_step_type property to have other step types, like Test or Deploy, use the same commit logic as Prod Deploy.
    Override start and end time of a change request
    Set the  sn_devops.change_request.auto_close_allow_override_start_time  and  sn_devops.change_request.auto_close_allow_override_end_time  properties as false to consider the change request start and end time instead of the pipeline’s when the  autoCloseChange  parameter is enabled in a pipeline.
    Node version of DevOps extension
    The node version of the ServiceNow DevOps  extension has been upgraded to version 20.x in Azure DevOps.
    Enhanced pipeline governance in GitLab
    View change request details like status, sys_id, priority in the GitLab console when a change request is created in GitLab using Docker image.
    Health scan enhancements
    • Identify outdated or prolonged discover and import requests using the DevOps -Stale or Long-Running Discover and Import Requests health check.
    • Verify whether webhooks have been configured correctly for any tracked repository, pipeline, or plan in  GitHub,  GitLab,  Azure DevOps, and  Jenkins using the DevOps webhook configuration analysis health check.
    • Identify OAuth app configuration issues for GitHub tools in the connected state using the DevOps webhook configuration analysis health check.
    • Verify if any scheduled job has been configured to run as an invalid or non-admin user.
    • Navigate to the Findings list from the DevOps Change Workspace home page by selecting  View all findings  in the  Health scan findings  widget. 
    Enhanced JFrog integration with DevOps Change Velocity
    Gather JFrog evidence seamlessly and create change records automatically using the improved JFrog integration with DevOps Change Velocity.
    Bearer authentication in JFrog
    Connect to JFrog using the secure bearer token authentication to comply with JFrog’s updated security policies.
    HTTP proxy for Docker
    Connect to DevOps Change Velocity through HTTP proxy settings using environment variables in your Docker deployment for instances that run a proxy server.
    Health scan enhancements
    • Identify any callback processing issues in your instance.
    • Identify any access control rule (ACL) that is incorrectly associated with a role in your instance.
    • Verify whether all DevOps tables are present in your instance and confirm whether all metadata in sys_* tables is present.
    • Verify whether all DevOps roles in your instance contain all expected roles, including inherited roles.
    Auto close without Change Management - State Model [Legacy] plugin
    Change requests can now be auto-closed without requiring you to install the Change Management - State Model [Legacy] plugin.

    Zurich
    Support for MID Server cluster
    Improve load balancing and failover protection by selecting a MID Server cluster when connecting to a tool instance associated with a MID Server cluster. This configuration enables multiple MID Servers with relevant capabilities to be grouped.
    Improved UX for DevOps Change health scans
    Run health scans and analyze findings efficiently in the DevOps Change workspace with an intuitive and user-friendly interface.
    Pipeline association for GitHub Actions
    When onboarding GitHub Actions pipelines through the App onboarding catalog or the onboarding APIs, now only the selected pipelines are associated with the DevOps app. If no pipeline is selected, all pipelines within the specified repository are associated.
    Tool connection check status
    If a tool is marked as Disconnected because of a system-generated failure during an unsuccessful connection check, any subsequent successful check automatically updates the connection status to Connected. If you manually disconnect the tool, the tool status remains Disconnected even if there’s a subsequent successful connection check.
    New roles for vulnerability integration
    • The sn_vul.app_sec_manager role is added to the DevOps Tool Owner [sn_devops.tool_owner] role when the DevOps Vulnerability Integrations plugin (sn_devops_vul_ints) is installed.
    • The sn_vul_veracode.configure_integration role is added to the DevOps Tool Owner [sn_devops.tool_owner] role when the Vulnerability Response Integration with Veracode plugin (sn_vul_veracode) is installed.
    Prod deploy commit logic for other step types
    Update the sn_devops.commit_rel_change_step_type property to have other step types, like Test or Deploy, use the same commit logic as Prod Deploy.
    Override start and end time of a change request
    Set the  sn_devops.change_request.auto_close_allow_override_start_time  and  sn_devops.change_request.auto_close_allow_override_end_time  properties as false to consider the change request start and end time instead of the pipeline’s when the  autoCloseChange  parameter is enabled in a pipeline.
    Node version of DevOps extension
    The node version of the ServiceNow DevOps  extension has been upgraded to version 20.x in Azure DevOps.
    Enhanced pipeline governance in GitLab
    View change request details like status, sys_id, priority in the GitLab console when a change request is created in GitLab using Docker image.
    Health scan enhancements
    • Identify outdated or prolonged discover and import requests using the DevOps -Stale or Long-Running Discover and Import Requests health check.
    • Verify whether webhooks have been configured correctly for any tracked repository, pipeline, or plan in  GitHub,  GitLab,  Azure DevOps, and  Jenkins using the DevOps webhook configuration analysis health check.
    • Identify OAuth app configuration issues for GitHub tools in the connected state using the DevOps webhook configuration analysis health check.
    • Verify if any scheduled job has been configured to run as an invalid or non-admin user.
    • Navigate to the Findings list from the DevOps Change Workspace home page by selecting  View all findings  in the  Health scan findings  widget. 
    Enhanced JFrog integration with DevOps Change Velocity
    Gather JFrog evidence seamlessly and create change records automatically using the improved JFrog integration with DevOps Change Velocity.
    Bearer authentication in JFrog
    Connect to JFrog using the secure bearer token authentication to comply with JFrog’s updated security policies.
    HTTP proxy for Docker
    Connect to DevOps Change Velocity through HTTP proxy settings using environment variables in your Docker deployment for instances that run a proxy server.
    Health scan enhancements
    • Identify any callback processing issues in your instance.
    • Identify any access control rule (ACL) that is incorrectly associated with a role in your instance.
    • Verify whether all DevOps tables are present in your instance and confirm whether all metadata in sys_* tables is present.
    • Verify whether all DevOps roles in your instance contain all expected roles, including inherited roles.
    Auto close without Change Management - State Model [Legacy] plugin
    Change requests can now be auto-closed without requiring you to install the Change Management - State Model [Legacy] plugin.

    Australia
    Enhanced JFrog integration with DevOps Change Velocity
    Gather JFrog evidence seamlessly and create change records automatically using the improved JFrog integration with DevOps Change Velocity.
    Bearer authentication in JFrog
    Connect to JFrog using the secure bearer token authentication to comply with JFrog’s updated security policies.
    HTTP proxy for Docker
    Connect to DevOps Change Velocity through HTTP proxy settings using environment variables in your Docker deployment for instances that run a proxy server.
    Health scan enhancements
    • Identify any callback processing issues in your instance.
    • Identify any access control rule (ACL) that is incorrectly associated with a role in your instance.
    • Verify whether all DevOps tables are present in your instance and confirm whether all metadata in sys_* tables is present.
    • Verify whether all DevOps roles in your instance contain all expected roles, including inherited roles.
    Auto close without Change Management - State Model [Legacy] plugin
    Change requests can now be auto-closed without requiring you to install the Change Management - State Model [Legacy] plugin.

    Removed

    Between your current release family and Australia, some DevOps Change Velocity features or functionality were removed.

    Release Release notes

    Yokohama

    		 No updates for this release.

    Zurich

    		 No updates for this release.

    Australia

    		 No updates for this release.

    Deprecations

    Between your current release family and Australia, some DevOps Change Velocity features or functionality were deprecated.

    Release Release notes

    Yokohama

    		 No updates for this release.

    Zurich

    		 No updates for this release.

    Australia

    		 No updates for this release.

    Activation information

    Review information on how to activate DevOps Change Velocity.

    Release Release notes

    Yokohama

    Activate DevOps Change Velocity by requesting it from the ServiceNow Store. Visit the ServiceNow Store website to view all the available apps and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the ServiceNow Store version history release notes.

    Zurich

    Install DevOps Change Velocity by requesting it from the ServiceNow Store.

    Australia

    Install DevOps Change Velocity by requesting it from the ServiceNow Store. Visit the ServiceNow Store to view all the available apps, and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the ServiceNow Store version history release notes.

    Additional requirements

    If any additional requirements were introduced or changed for DevOps Change Velocity we have noted them here.

    Release Release notes

    Yokohama

    		 No updates for this release.

    Zurich

    		 No updates for this release.

    Australia

    		 No updates for this release.

    Browser requirements

    If any specific browser requirements were introduced or changed for DevOps Change Velocity we have noted them here.

    Release Release notes

    Yokohama

    		 No updates for this release.

    Zurich

    		 No updates for this release.

    Australia

    		 No updates for this release.

    Accessibility information

    Review details on accessibility information for DevOps Change Velocity, such as specific requirements or compliance levels.

    Release Release notes

    Yokohama

    		 No updates for this release.

    Zurich

    Australia

    		 No updates for this release.

    Localization information

    If there are specific localization considerations for DevOps Change Velocity we have noted them here.

    Release Release notes

    Yokohama

    		 No updates for this release.

    Zurich

    		 No updates for this release.

    Australia

    		 No updates for this release.

    Highlight information

    If there are specific highlight considerations for DevOps Change Velocity we have noted them here.

    Release Release notes

    Yokohama
    • Integrate with the Harness orchestration tool to discover Harness pipelines and enable change automation.
    • Detect anomalies and issues in your DevOps Change Velocity instance using health scans.

    See DevOps Change Velocity for more information.

    Zurich
    • Improve instance efficiency by skipping step-level pipeline processing.
    • Improve load balancing and failover protection by selecting a MID Server cluster during tool connection.

    See DevOps Change Velocity for more information.

    Australia
    • Gather JFrog evidence seamlessly and create change records automatically.
    • Connect to JFrog using the secure bearer token authentication.
    • Connect to DevOps Change Velocity through HTTP proxy settings in your Docker deployment.

    See DevOps Change Velocity for more information.