--- sourceDocument: yokohama Combined Product Files sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/delta-xanadu-yokohama Release : - yokohama ft:locale : - en-US ft:publication_title : - yokohama Combined Product Files ft:clusterId : - delta3yx bundleId : - delta3yx --- # Combined DevOps Change Velocity release notes for upgrades from Xanadu to Yokohama # Combined DevOps Change Velocity release notes for upgrades from Xanadu to Yokohama {#ariaid-title1} Release version: Yokohama Updated October 8, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 16 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Combined DevOps Change Velocity release notes for upgrades from Xanadu to Yokohama This consolidated release notes document covers all key updates, new features, changes, and important upgrade information for ServiceNow DevOps Change Velocity from the Xanadu release family through to the Yokohama release. It is designed to help ServiceNow customers prepare for and successfully upgrade their DevOps Change Velocity instances with relevant technical and functional details. Show full answer Show less ## Important Upgrade Information * Before upgrading to Yokohama, customers must run the **ReConfigure Bitbucket Server Repositories for PullRequest** scheduled job to enable import of pull request records from Bitbucket Server or Data Center repositories. * New customers or those on zBoot instances wanting to create type-based workflow change requests must set the system property `com.snc.changemanagement.changemodel.typecompatibility` to True. ## New Features * **Bitbucket Cloud Tool Integration:** Available to connect and process real-time repository events within DevOps Change Velocity. * **DevOps Change Workspace UI:** Simplifies creation of custom tool integrations across planning, coding, and orchestration with intuitive navigation and embedded documentation. * **OAuth 2.0 Authentication:** Enhanced security for Azure DevOps and Jira Cloud tool connections. * **Harness Integration (Yokohama):** Enables discovery of Harness pipelines and real-time notifications to automate and trace changes. * **Import-Based Evidence Collection:** Improves efficiency by skipping step-level pipeline processing for supported orchestration tools (GitHub Actions, Azure DevOps, GitLab, Jenkins). * **DevOps Health Instance Scan:** Provides anomaly detection and health scans of your instance for proactive issue identification. ## Changes and Enhancements * **DevOps Data in Change Requests:** View, add, and edit DevOps data within manually created change requests in Service Operations Workspace for a unified experience. * **Improved DevOps Model Change:** New flows to streamline DevOps change processes without disruption, including a simplified change model without an Assess state. * **Generalized Docker Container Solution:** Supports integration of any orchestration tool using a flexible Docker-based framework. * **Enhanced Security and Configuration:** Default disabling of the Track file changes option to reduce security risks; new properties enable specifying close code values for change requests. * **Improved Tool Connection Management:** Automatic status updates for tool connection checks and support for MID Server clusters to enhance load balancing and failover protection. * **Enhanced JFrog Integration:** Improved evidence gathering, bearer token authentication, and HTTP proxy support for Docker deployments. * **Health Scan Enhancements:** Additional proactive checks for configuration issues, stale requests, webhook validations, and ACL misconfigurations. * **Pipeline Association for GitHub Actions:** Onboarding now allows selection of specific pipelines to associate with DevOps Change Velocity. * **Token-Based Authentication for Rally:** Improves security for webhook configuration. * **New Roles for Vulnerability Integration:** Added roles to handle security vulnerability integrations with Veracode and other tools. ## Activation and Requirements * DevOps Change Velocity is activated by requesting it through the ServiceNow Store. * No new browser or additional requirements were introduced between Xanadu and Yokohama releases. ## Accessibility * Xanadu introduced accessibility improvements to support WCAG 2.1 Level AA conformance in the configurable workspace, including reflow support allowing up to 400% zoom without loss of content or functionality. * No accessibility updates were noted in Yokohama. ## Removed and Deprecated Features No features or functionality were removed or deprecated between Xanadu and Yokohama releases. ## Key Benefits for ServiceNow Customers * Enhanced security and integration capabilities with OAuth 2.0 and token-based authentication for key DevOps tools. * Improved efficiency with import-based evidence collection and new orchestration tool integrations like Harness and JFrog. * More robust instance health monitoring through enhanced health scans and anomaly detection. * Simplified workflows and UI improvements for creating change requests and custom tool integrations. * Greater flexibility and scalability with support for MID Server clusters and generalized Docker container integrations. * Accessibility improvements ensuring usability for all users. Consolidated page of all release notes for DevOps Change Velocity from Xanadu to Yokohama. ## 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 Xanadu to Yokohama. 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 Yokohama Before you upgrade to Yokohama, review these pre- and post-upgrade tasks and complete the tasks as needed. {#dfrn3-devopschangevelocity-summary__entry__2} | Release | Release notes | |-|-| | Xanadu | 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. | | Yokohama | Upgrade information : 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](https://www.servicenow.com/docs/access?context=t_AddAPropertyUsingSysPropsList&family=yokohama&ft:locale=en-US). 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. | [ ] ## New features Between your current release family and Yokohama, new features were introduced for DevOps Change Velocity. {#dfrn3-devopschangevelocity-summary__entry__8} | Release | Release notes | |-|-| | Xanadu | [Change Management in SOW Admin Center](https://www.servicenow.com/docs/access?context=manage-admin-console-sow-itsm&family=xanadu&ft:locale=en-US) : Configure Change Management features from the Service Operations Workspace Admin Center to increase change efficiency, accelerate change approvals, drive data-driven risk analysis, and leverage DevOps data for change automation. [OAuth 2.0 authentication for Azure DevOps (ADO)](https://www.servicenow.com/docs/access?context=set-up-azure-devops-oauth-2-0-credential&family=xanadu&ft:locale=en-US) : Use OAuth 2.0 authentication to connect your Azure DevOps tool with DevOps Change Velocity ensuring a more secure authentication method. [OAuth 2.0 authentication for Jira Cloud](https://www.servicenow.com/docs/access?context=create-jira-tool-dev-ops&family=xanadu&ft:locale=en-US) : Use OAuth 2.0 authentication to connect your Jira Cloud tool with DevOps Change Velocity ensuring a more secure authentication method. [Bitbucket Cloud tool integration with ServiceNow](https://www.servicenow.com/docs/access?context=bitbucket-integration-dev-ops&family=xanadu&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=create-a-tool-integration-from-the-devops-change-workspace&family=xanadu&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=import-based-evidence-collection-for-orchestration-capability&family=xanadu&ft:locale=en-US) : Improve instance efficiency by skipping step-level pipeline processing for accelerated change management and evidence collection for GitHub Actions and Azure DevOps (ADO) orchestration tools. | | Yokohama | [Bitbucket Cloud tool integration with ServiceNow](https://www.servicenow.com/docs/access?context=bitbucket-integration-dev-ops&family=yokohama&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=create-a-tool-integration-from-the-devops-change-workspace&family=yokohama&ft:locale=en-US) : 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. [Harness integration](https://www.servicenow.com/docs/access?context=harness-integration-with-devops-change-velocity&family=yokohama&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=run-health-scan-check&family=yokohama&ft:locale=en-US) : Detect anomalies and issues in the instance by running or scheduling health scans on your DevOps Change Velocity instance. [Import based evidence collection](https://www.servicenow.com/docs/access?context=import-based-evidence-collection-for-orchestration-capability&family=yokohama&ft:locale=en-US) : 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. | [ ] ## Changes Between your current release family and Yokohama, some changes were made to existing DevOps Change Velocity features. {#dfrn3-devopschangevelocity-summary__entry__14} | Release | Release notes | |-|-| | Xanadu | [Reflow for configurable workspace](https://www.servicenow.com/docs/access?context=auto-reflow&family=xanadu&ft:locale=en-US) : DevOps Change Configurable workspace supports reflow, which enables pages and content to be zoomed up to 400% through your browser settings without loss of content or functionality. For more information, see the [Accessibility information](https://www.servicenow.com/docs/hOo7oNuPetzbr7PeONl7_A#dfrn3-devopschangevelocity-summary__devops-rn-accessibility) section that follows. [DevOps data in change request](https://www.servicenow.com/docs/access?context=create-change-sow&family=xanadu&ft:locale=en-US) : View, add, and edit DevOps data in a manually created change request in Service Operations Workspace for a unified change request experience in both DevOps Change Workspace and Service Operations Workspace. [Enhancements to DevOps Model change](https://www.servicenow.com/docs/access?context=devops-change-multimodel&family=xanadu&ft:locale=en-US) : * In-product guidance enables you to leverage DevOps models and easily create DevOps changes without disruption of your change process. * To make the Change - DevOps -- Implement flow of the DevOps model more suitable for DevOps changes, change tasks are no longer automatically created. * The new Change -- DevOps -- Update execution state flow in the DevOps model means you no longer have to activate the DevOps Change Request Manual Approval flow to send a callback to the third-party orchestration tool. * Fast-track your change process by using a new DevOps Simplified change model, which doesn't contain the Assess state. Change approval for this model is based on the DevOps Simplified Model Change policy. [Branch details for artifacts and packages](https://www.servicenow.com/docs/access?context=using-dev-ops-release-change&family=xanadu&ft:locale=en-US) : Branch details from pipeline executions are now available for artifacts and packages for better tracking. [Create lists](https://www.servicenow.com/docs/access?context=add-new-list-in-list-module&family=xanadu&ft:locale=en-US) : Option to create customized lists added to the Changes, Tools, and Administration modules in the DevOps Change Workspace. [Jira Server connection using API key](https://www.servicenow.com/docs/access?context=create-jira-tool-dev-ops&family=xanadu&ft:locale=en-US) : Connect to your Jira Server using API key authentication rather than basic authentication. [GitHub Actions reruns](https://www.servicenow.com/docs/access?context=github-actions-integration-with-devops&family=xanadu&ft:locale=en-US) : Re-running failed GitHub jobs will now use the existing change request created for the failed jobs instead of creating new change requests. [Generalized Docker Container solution to support any orchestration tool](https://www.servicenow.com/docs/access?context=servicenow-custom-actions-for-gitlab&family=xanadu&ft:locale=en-US) : Use the generalized and extensible Docker Container solution to integrate any orchestration tool with DevOps Change Velocity for invoking pipeline actions like change request creation and collecting relevant DevOps data without having to rely on tool specific plugins or extensions. [Simplified onboarding of planning tools that are not supported in the base system](https://www.servicenow.com/docs/access?context=onboard-gitlab-to-devops-change-velocity-workspace&family=xanadu&ft:locale=en-US) : Integrate planning tools that are not supported in the base system by leveraging transformer rules. GitLab Issues is now available as one of the planning tools and is built leveraging this new approach so you can discover plans, import work items, and configure webhooks for work items (issues) in GitLab. [Enhanced manual DevOps change creation experience](https://www.servicenow.com/docs/access?context=create-change-sow&family=xanadu&ft:locale=en-US) : Add work items data in a manually created DevOps change request in  Service Operations Workspace  for  ITSM. [Default BitBucket branch property](https://www.servicenow.com/docs/access?context=dev-ops-administration&family=xanadu&ft:locale=en-US) : Specify the default Bitbucket branch name that must be used to create an import request in the sn_devops.bitbucket_default_branch property. [Additional scans for DevOps Health Scan Content pack](https://www.servicenow.com/docs/access?context=run-health-scan-check&family=xanadu&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=devops-wkspc-bitbucket-tool-conn&family=xanadu&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=change-request-creation-with-devops-data-retrieval-errors&family=xanadu&ft:locale=en-US) : Enable change request creation even if there is an error in retrieving the DevOps data for a Harness pipeline. [Branch name filter](https://www.servicenow.com/docs/access?context=create-devops-change-request-manual&family=xanadu&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=servicenow-devops-test-report-custom-action&family=xanadu&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=configure-webhooks-for-rally-manually&family=xanadu&ft:locale=en-US) : Configure webhooks for Rally using token based authentication instead of using the integration username and password. [Renamed variables for Docker](https://www.servicenow.com/docs/access?context=servicenow-custom-actions-for-gitlab&family=xanadu&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=dev-ops-change-acceleration&family=xanadu&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=create-change-sow&family=xanadu&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=sc-github&family=xanadu&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=dev-ops-administration&family=xanadu&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=playbook-enter-github-instance-details&family=xanadu&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=run-health-scan-check&family=xanadu&ft:locale=en-US) : Run health scans and analyze findings efficiently in the DevOps Change workspace with an intuitive and user-friendly interface. [Pipeline association for GitHub Actions](https://www.servicenow.com/docs/access?context=sc-github&family=xanadu&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=devops-reference-error-messages&family=xanadu&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=installed-with-dev-ops&family=xanadu&ft:locale=en-US) : * 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. | | Yokohama | [Enhanced JFrog integration with DevOps Change Velocity](https://www.servicenow.com/docs/access?context=devops-jfrog-connect-workspace&family=yokohama&ft:locale=en-US) : Gather JFrog evidence seamlessly and create change records automatically using the improved JFrog integration with DevOps Change Velocity. [Bearer authentication in JFrog](https://www.servicenow.com/docs/access?context=devops-jfrog-connect-workspace&family=yokohama&ft:locale=en-US) : Connect to JFrog using the secure bearer token authentication to comply with JFrog's updated security policies. [HTTP proxy for Docker](https://www.servicenow.com/docs/access?context=servicenow-custom-actions-for-gitlab&family=yokohama&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=run-health-scan-check&family=yokohama&ft:locale=en-US) : * 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](https://www.servicenow.com/docs/access?context=dev-ops-change-acceleration&family=yokohama&ft:locale=en-US) : Change requests can now be auto-closed without requiring you to install the Change Management - State Model \[Legacy\] plugin. [Prod deploy commit logic for other step types](https://www.servicenow.com/docs/access?context=dev-ops-commits-release&family=yokohama&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=dev-ops-config-change-details&family=yokohama&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=config-dev-ops-extensions-azure&family=yokohama&ft:locale=en-US) : The node version of the ServiceNow DevOps  extension has been upgraded to version 20.x in Azure DevOps. [Enhanced pipeline governance in GitLab](https://www.servicenow.com/docs/access?context=servicenow-custom-actions-for-gitlab&family=yokohama&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=run-health-scan-check&family=yokohama&ft:locale=en-US) : * 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.  [Support for MID Server cluster](https://www.servicenow.com/docs/access?context=playbook-enter-github-instance-details&family=yokohama&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=run-health-scan-check&family=yokohama&ft:locale=en-US) : Run health scans and analyze findings efficiently in the DevOps Change workspace with an intuitive and user-friendly interface. [Pipeline association for GitHub Actions](https://www.servicenow.com/docs/access?context=sc-github&family=yokohama&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=devops-reference-error-messages&family=yokohama&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=installed-with-dev-ops&family=yokohama&ft:locale=en-US) : * 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. [Additional scans for DevOps Health Scan Content pack](https://www.servicenow.com/docs/access?context=run-health-scan-check&family=yokohama&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=devops-wkspc-bitbucket-tool-conn&family=yokohama&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=change-request-creation-with-devops-data-retrieval-errors&family=yokohama&ft:locale=en-US) : Enable change request creation even if there is an error in retrieving the DevOps data for a Harness pipeline. [Branch name filter](https://www.servicenow.com/docs/access?context=create-devops-change-request-manual&family=yokohama&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=servicenow-devops-test-report-custom-action&family=yokohama&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=configure-webhooks-for-rally-manually&family=yokohama&ft:locale=en-US) : Configure webhooks for Rally using token based authentication instead of using the integration username and password. [Renamed variables for Docker](https://www.servicenow.com/docs/access?context=servicenow-custom-actions-for-gitlab&family=yokohama&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=dev-ops-change-acceleration&family=yokohama&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=create-change-sow&family=yokohama&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=sc-github&family=yokohama&ft:locale=en-US) : 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](https://www.servicenow.com/docs/access?context=dev-ops-administration&family=yokohama&ft:locale=en-US) : 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. [Simplified onboarding of orchestration tools not supported in the base system](https://www.servicenow.com/docs/access?context=devops-user-created-orchestration-tool-integration&family=yokohama&ft:locale=en-US) : Integrate orchestration tools that aren't supported in the base system by leveraging a generic framework. [Custom fields for planning tool integration](https://www.servicenow.com/docs/access?context=add-custom-field-for-a-planning-tool-integration&family=yokohama&ft:locale=en-US) : Add custom fields into your planning tool integration to improve configurability and access business-specific information, which facilitates more informed decision-making. | [ ] ## Removed Between your current release family and Yokohama, some DevOps Change Velocity features or functionality were removed. {#dfrn3-devopschangevelocity-summary__entry__20} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | [ ] ## Deprecations Between your current release family and Yokohama, some DevOps Change Velocity features or functionality were deprecated. {#dfrn3-devopschangevelocity-summary__entry__26} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | [ ] ## Activation information Review information on how to activate DevOps Change Velocity. {#dfrn3-devopschangevelocity-summary__entry__32} | Release | Release notes | |-|-| | Xanadu | Activate DevOps Change Velocity by requesting it from the ServiceNow Store. Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) 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](https://www.servicenow.com/docs/access?context=sn-store-release-notes&family=xanadu&ft:locale=en-US). | | Yokohama | Activation information : Activate DevOps Change Velocity by requesting it from the ServiceNow Store. Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) 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](https://www.servicenow.com/docs/access?context=sn-store-release-notes&family=yokohama&ft:locale=en-US). Important: DevOps Change Velocity is available in the ServiceNow Store. For details, see the "Activation information" section of these release notes. | [ ] ## Additional requirements If any additional requirements were introduced or changed for DevOps Change Velocity we have noted them here. {#dfrn3-devopschangevelocity-summary__entry__38} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | 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. {#dfrn3-devopschangevelocity-summary__entry__44} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | [ ] ## Accessibility information Review details on accessibility information for DevOps Change Velocity, such as specific requirements or compliance levels. {#dfrn3-devopschangevelocity-summary__entry__50} | Release | Release notes | |-|-| | Xanadu | Accessibility improvements : Accessibility improvements were completed to create a configurable workspace that supports WCAG 2.1 Level AA conformance. Reflow : The Configurable Workspace supports reflow, which enables pages and content to be zoomed up to 400% through your browser settings without loss of content or functionality. Additionally, content can be enlarged without scrolling in two dimensions at a width equivalent to 320 CSS pixels or a height equivalent to 256 CSS pixels. Page layouts are transformed into a vertical, stacked view automatically when users increase browser zoom to 400%. : This enhancement helps users with low vision or who have trouble seeing web content in a browser due to monitor size, device type, poor lighting, or other situations. Reflow can be turned off with a system property for instances, experiences, and pages. See [Reflow for Configurable Workspace](https://www.servicenow.com/docs/access?context=auto-reflow&family=xanadu&ft:locale=en-US) for details. | | Yokohama | No updates for this release. | [ ] ## Localization information If there are specific localization considerations for DevOps Change Velocity we have noted them here. {#dfrn3-devopschangevelocity-summary__entry__56} | Release | Release notes | |-|-| | Xanadu | No updates for this release. | | Yokohama | No updates for this release. | [ ] ## Highlight information If there are specific highlight considerations for DevOps Change Velocity we have noted them here. {#dfrn3-devopschangevelocity-summary__entry__62} | Release | Release notes | |-|-| | Xanadu | * Leverage DevOps data for change automation by configuring Change Management features from the Service Operations Workspace Admin Center. * Benefit from accessibility improvements to create a configurable workspace that supports Web Content Accessibility Guidelines (WCAG) 2.1 Level AA conformance. See [DevOps Change Velocity](https://www.servicenow.com/docs/access?context=devops-landing-page-new&family=xanadu&ft:locale=en-US) for more information. | | 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](https://www.servicenow.com/docs/access?context=devops-landing-page-new&family=yokohama&ft:locale=en-US) for more information. | [ ]