Combined DevOps Change Velocity release notes for upgrades from Washington DC to Australia
On this page
Combined DevOps Change Velocity release notes for upgrades from Washington DC to Australia
Consolidated page of all release notes for DevOps Change Velocity from Washington DC 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 Washington DC 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.
<table class=“custom-rows”><thead><tr><th class=“filter”>
Release
</th><th>
Release notes
</th></tr></thead><tbody><tr><td>
Washington DC
</td><td>
No updates for this release.
</td></tr><tr><td>
Xanadu
</td><td>
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.
</td></tr><tr><td>
Yokohama
</td><td>
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 thecom.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.
</td></tr><tr><td>
Zurich
</td><td>
No updates for this release.
</td></tr><tr><td>
Australia
</td><td>
No updates for this release.
</td></tr></tbody> </table>## New features
Between your current release family and Australia, new features were introduced for DevOps Change Velocity.
<table class=“custom-rows”><thead><tr><th class=“filter”>
Release
</th><th>
Release notes
</th></tr></thead><tbody><tr><td>
Washington DC
</td><td>
Discover GitHub issues in GitHub repositories as part of the planning capability to link the GitHub issues with GitHub code commits.
Collect data related to change request creation, Sonar scan, artifact registration, and package registration in your GitLab pipeline using the custom actions for GitLab.
Integrate DevOps Change Velocity with any orchestration tool that is not supported in the base system to discover the orchestration tool, configure webhooks, import historical data, receive live data, and enable change control on your pipelines.
Track GitLab merge request (pull request) pipeline executions in DevOps Change Velocity, link pull request and orchestration pipelines and to enable change approval tracking.
Integrate DevOps Change Velocity with Jira Cloud and track Jira Issues for the configured projects.
Import the artifact data published to JFrog Artifactory for the corresponding pipeline executions for GitHub Actions, GitLab, and Azure DevOps.
Use OAuth 2.0 authentication to connect your Azure DevOps tool with DevOps Change Velocity ensuring a more secure authentication method.
Use OAuth 2.0 authentication to connect your Jira Cloud tool with DevOps Change Velocity ensuring a more secure authentication method.
</td></tr><tr><td>
Xanadu
</td><td>
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.
Use OAuth 2.0 authentication to connect your Azure DevOps tool with DevOps Change Velocity ensuring a more secure authentication method.
Use OAuth 2.0 authentication to connect your Jira Cloud tool with DevOps Change Velocity ensuring a more secure authentication method.
Integrate the Bitbucket Cloud coding tool with DevOps Change Velocity to connect, discover, import, and process real-time repository events in DevOps Change Velocity.
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.
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.
</td></tr><tr><td>
Yokohama
</td><td>
Discover Harness pipelines and configure real-time notifications to enable change traceability and automation by integrating the Harness orchestration tool with DevOps Change Velocity.
Detect anomalies and issues in the instance by running or scheduling health scans on your DevOps Change Velocity instance.
Integrate the Bitbucket Cloud coding tool with DevOps Change Velocity to connect, discover, import, and process real-time repository events in DevOps Change Velocity.
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.
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.
</td></tr><tr><td>
Zurich
</td><td>
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.
</td></tr><tr><td>
Australia
</td><td>
No updates for this release.
</td></tr></tbody> </table>## Changes
Between your current release family and Australia, some changes were made to existing DevOps Change Velocity features.
<table class=“custom-rows”><thead><tr><th class=“filter”>
Release
</th><th>
Release notes
</th></tr></thead><tbody><tr><td>
Washington DC
</td><td>
Avoid issues that might occur in the automated change request creation guided procedure because of the tool connection state.
Move and track changes through added transition flows for the Change - DevOps - New and Change - DevOps - Schedule states in the DevOps change model.
View errors corresponding to a change request in the work notes of a change request and console logs of the pipeline tool when a business rule or data policy causes an issue while updating a change in the DevOps Change Request Manual Approval, DevOps Change Request Minimal Automation Approval, or DevOps Change Request Advanced Automation Approval flows.
Retrieve data associated with a change request based on the specified relation type using the DevOpsChangeRelationshipHelper script include.
Specify the maximum number of times the discover action will be automatically retried after it reaches the rate limit using the Maximum limit for the number of times the discover action that exceeds the rate limit will be retried property.
Restart an import request from the Import Request record that couldn’t be completed due to an error.
Repositories are automatically associated to applications when a corresponding pipeline identifies commits of repositories that are not yet associated.
Automatically publish unit test results of types NUnit, pytest, jest, JUnit, and XUnit from GitHub Actions workflows without any custom Application Programming Interface (API) calls.
Enable change request creation even if there is an error in retrieving the DevOps data in a pipeline.
Configure multiple ServiceNow DevOps connections in one Jenkins server.
Retrieve and update change request details associated with a GitLab pipeline and publish unit test results. Automatically update close code based on the overall pipeline execution status for simple GitLab pipelines.
-
Manual retry of downstream events
If an error occurs for an event, and there are subsequent downstream events associated with it, then you must manually retry each downstream event by selecting the Retry button. Automatically retrying of downstream events is not supported anymore.
-
Enhancements to DevOps Model change
-
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 from pipeline executions are now available for artifacts and packages for better tracking.
Option to create customized lists added to the Changes, Tools, and Administration modules in the DevOps Change Workspace.
Connect to your Jira Server using API key authentication rather than basic authentication.
Re-running failed GitHub jobs will now use the existing change request created for the failed jobs instead of creating new change requests.
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.
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.
Specify the default Bitbucket branch name that must be used to create an import request in the sn_devops.bitbucket_default_branch property.
</td></tr><tr><td>
Xanadu
</td><td>
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 section that follows.
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
-
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 from pipeline executions are now available for artifacts and packages for better tracking.
Option to create customized lists added to the Changes, Tools, and Administration modules in the DevOps Change Workspace.
Connect to your Jira Server using API key authentication rather than basic authentication.
Re-running failed GitHub jobs will now use the existing change request created for the failed jobs instead of creating new change requests.
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.
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.
Add work items data in a manually created DevOps change request in Service Operations Workspace for ITSM.
Specify the default Bitbucket branch name that must be used to create an import request in the sn_devops.bitbucket_default_branch property.
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 Data Center for improved insights and efficiency.
Enable change request creation even if there is an error in retrieving the DevOps data for a Harness pipeline.
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.
The servicenow-devops-test-report custom action in GitHub now includes an optional test-summary-name parameter to specify the test summary results name.
Configure webhooks for Rally using token based authentication instead of using the integration username and password.
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 on the change record associated to a pipeline execution with a linked package are now displayed in the Security Summaries tab.
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.
The Track file changes option is now disabled by default when a repository is configured to prevent any potential security risks.
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.
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.
Run health scans and analyze findings efficiently in the DevOps Change workspace with an intuitive and user-friendly interface.
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.
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.
-
</td></tr><tr><td>
Yokohama
</td><td>
Integrate orchestration tools that aren’t supported in the base system by leveraging a generic framework.
Add custom fields into your planning tool integration to improve configurability and access business-specific information, which facilitates more informed decision-making.
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 Data Center for improved insights and efficiency.
Enable change request creation even if there is an error in retrieving the DevOps data for a Harness pipeline.
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.
The servicenow-devops-test-report custom action in GitHub now includes an optional test-summary-name parameter to specify the test summary results name.
Configure webhooks for Rally using token based authentication instead of using the integration username and password.
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 on the change record associated to a pipeline execution with a linked package are now displayed in the Security Summaries tab.
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.
The Track file changes option is now disabled by default when a repository is configured to prevent any potential security risks.
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.
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.
Run health scans and analyze findings efficiently in the DevOps Change workspace with an intuitive and user-friendly interface.
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.
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.
-
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.
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.
The node version of the ServiceNow DevOps extension has been upgraded to version 20.x in Azure DevOps.
View change request details like status, sys_id, priority in the GitLab console when a change request is created in GitLab using Docker image.
-
-
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.
-
Gather JFrog evidence seamlessly and create change records automatically using the improved JFrog integration with DevOps Change Velocity.
Connect to JFrog using the secure bearer token authentication to comply with JFrog’s updated security policies.
Connect to DevOps Change Velocity through HTTP proxy settings using environment variables in your Docker deployment for instances that run a proxy server.
-
-
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.
</td></tr><tr><td>
Zurich
</td><td>
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.
Run health scans and analyze findings efficiently in the DevOps Change workspace with an intuitive and user-friendly interface.
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.
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.
-
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.
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.
The node version of the ServiceNow DevOps extension has been upgraded to version 20.x in Azure DevOps.
View change request details like status, sys_id, priority in the GitLab console when a change request is created in GitLab using Docker image.
-
-
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.
-
Gather JFrog evidence seamlessly and create change records automatically using the improved JFrog integration with DevOps Change Velocity.
Connect to JFrog using the secure bearer token authentication to comply with JFrog’s updated security policies.
Connect to DevOps Change Velocity through HTTP proxy settings using environment variables in your Docker deployment for instances that run a proxy server.
-
-
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.
</td></tr><tr><td>
Australia
</td><td>
Gather JFrog evidence seamlessly and create change records automatically using the improved JFrog integration with DevOps Change Velocity.
Connect to JFrog using the secure bearer token authentication to comply with JFrog’s updated security policies.
Connect to DevOps Change Velocity through HTTP proxy settings using environment variables in your Docker deployment for instances that run a proxy server.
-
-
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.
</td></tr></tbody> </table>## Removed
Between your current release family and Australia, some DevOps Change Velocity features or functionality were removed.
<table class=“custom-rows”><thead><tr><th class=“filter”>
Release
</th><th>
Release notes
</th></tr></thead><tbody><tr><td>
Washington DC
</td><td>
No updates for this release.
</td></tr><tr><td>
Xanadu
</td><td>
No updates for this release.
</td></tr><tr><td>
Yokohama
</td><td>
No updates for this release.
</td></tr><tr><td>
Zurich
</td><td>
No updates for this release.
</td></tr><tr><td>
Australia
</td><td>
No updates for this release.
</td></tr></tbody> </table>## Deprecations
Between your current release family and Australia, some DevOps Change Velocity features or functionality were deprecated.
<table class=“custom-rows”><thead><tr><th class=“filter”>
Release
</th><th>
Release notes
</th></tr></thead><tbody><tr><td>
Washington DC
</td><td>
No updates for this release.
</td></tr><tr><td>
Xanadu
</td><td>
No updates for this release.
</td></tr><tr><td>
Yokohama
</td><td>
No updates for this release.
</td></tr><tr><td>
Zurich
</td><td>
No updates for this release.
</td></tr><tr><td>
Australia
</td><td>
No updates for this release.
</td></tr></tbody> </table>## Activation information
Review information on how to activate DevOps Change Velocity.
<table class=“custom-rows”><thead><tr><th class=“filter”>
Release
</th><th>
Release notes
</th></tr></thead><tbody><tr><td>
Washington DC
</td><td>
Install 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.
</td></tr><tr><td>
Xanadu
</td><td>
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.
</td></tr><tr><td>
Yokohama
</td><td>
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.
</td></tr><tr><td>
Zurich
</td><td>
Install DevOps Change Velocity by requesting it from the ServiceNow Store.
</td></tr><tr><td>
Australia
</td><td>
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.
</td></tr></tbody> </table>## Additional requirements
If any additional requirements were introduced or changed for DevOps Change Velocity we have noted them here.
<table class=“custom-rows”><thead><tr><th class=“filter”>
Release
</th><th>
Release notes
</th></tr></thead><tbody><tr><td>
Washington DC
</td><td>
No updates for this release.
</td></tr><tr><td>
Xanadu
</td><td>
No updates for this release.
</td></tr><tr><td>
Yokohama
</td><td>
No updates for this release.
</td></tr><tr><td>
Zurich
</td><td>
No updates for this release.
</td></tr><tr><td>
Australia
</td><td>
No updates for this release.
</td></tr></tbody> </table>## Browser requirements
If any specific browser requirements were introduced or changed for DevOps Change Velocity we have noted them here.
<table class=“custom-rows”><thead><tr><th class=“filter”>
Release
</th><th>
Release notes
</th></tr></thead><tbody><tr><td>
Washington DC
</td><td>
No updates for this release.
</td></tr><tr><td>
Xanadu
</td><td>
No updates for this release.
</td></tr><tr><td>
Yokohama
</td><td>
No updates for this release.
</td></tr><tr><td>
Zurich
</td><td>
No updates for this release.
</td></tr><tr><td>
Australia
</td><td>
No updates for this release.
</td></tr></tbody> </table>## Accessibility information
Review details on accessibility information for DevOps Change Velocity, such as specific requirements or compliance levels.
<table class=“custom-rows”><thead><tr><th class=“filter”>
Release
</th><th>
Release notes
</th></tr></thead><tbody><tr><td>
Washington DC
</td><td>
No updates for this release.
</td></tr><tr><td>
Xanadu
</td><td>
-
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 for details.
</td></tr><tr><td>
Yokohama
</td><td>
No updates for this release.
</td></tr><tr><td>
Zurich
</td><td>
-
****
</td></tr><tr><td>
Australia
</td><td>
No updates for this release.
</td></tr></tbody> </table>## Localization information
If there are specific localization considerations for DevOps Change Velocity we have noted them here.
<table class=“custom-rows”><thead><tr><th class=“filter”>
Release
</th><th>
Release notes
</th></tr></thead><tbody><tr><td>
Washington DC
</td><td>
No updates for this release.
</td></tr><tr><td>
Xanadu
</td><td>
No updates for this release.
</td></tr><tr><td>
Yokohama
</td><td>
No updates for this release.
</td></tr><tr><td>
Zurich
</td><td>
No updates for this release.
</td></tr><tr><td>
Australia
</td><td>
No updates for this release.
</td></tr></tbody> </table>## Highlight information
If there are specific highlight considerations for DevOps Change Velocity we have noted them here.
<table class=“custom-rows”><thead><tr><th class=“filter”>
Release
</th><th>
Release notes
</th></tr></thead><tbody><tr><td>
Washington DC
</td><td>
-
Discover GitHub issues in GitHub repositories as part of the planning capability.
-
Collect data related to change request creation, Sonar scan, artifact registration, and package registration in your GitLab pipeline.
-
Retrieve data associated with a change request using the DevOpsChangeRelationshipHelper script.
See DevOps Change Velocity for more information.
</td></tr><tr><td>
Xanadu
</td><td>
-
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 for more information.
</td></tr><tr><td>
Yokohama
</td><td>
-
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.
</td></tr><tr><td>
Zurich
</td><td>
-
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.
</td></tr><tr><td>
Australia
</td><td>
-
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.
</td></tr></tbody> </table>Parent Topic:Products combined by family
Keep exploring.
Find another answer, or bring this documentation into your own tools.