--- sourceDocument: australia Combined Product Files sourceDocumentLink: https://www.servicenow.com/docs/r/australia/delta-zurich-australia Release : - australia ft:locale : - en-US ft:publication_title : - australia Combined Product Files ft:clusterId : - delta3az bundleId : - delta3az --- # Combined DevOps Change Velocity release notes for upgrades from Zurich to Australia # Combined DevOps Change Velocity release notes for upgrades from Zurich to Australia {#ariaid-title1} Release version: Australia Updated November 5, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 8 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 Zurich to Australia This consolidated release notes document covers the key updates and changes in DevOps Change Velocity from the Zurich release up to the Australia release. It is intended to help ServiceNow customers prepare for their upgrade by summarizing new features, changes, removals, deprecations, activation instructions, and other relevant information across these versions. Show full answer Show less ## Key Features * **Rally Authentication with OAuth 2.0:** Strengthens tool security by enabling OAuth 2.0 authentication for Rally tool connections (introduced in Zurich and continued in Australia). * **GitHub Data Residency Support:** Allows connection to GitHub Enterprise Server with geographic data residency controls to comply with organizational policies. * **Import-Based Evidence Collection:** Improves instance efficiency by skipping step-level pipeline processing for faster change management and evidence collection with GitHub Actions, Azure DevOps, GitLab, and Jenkins. * **Jira Authentication with 3LO:** Enables secure, delegated OAuth 2.0 three-legged authentication for Jira tool connections. * **Bitbucket Cloud Authentication:** Supports connecting to Bitbucket Cloud using Basic Auth with email and API token scopes, replacing deprecated app passwords. * **Enhanced JFrog Integration:** Facilitates automatic gathering of JFrog evidence and change record creation, supporting bearer token authentication for security compliance. * **Docker HTTP Proxy Support:** Allows configuring DevOps Change Velocity to connect through HTTP proxy settings using environment variables. * **Health Scan Enhancements:** Improved diagnostics include identifying callback processing issues, ACL misconfigurations, missing DevOps tables and roles, webhook setup validation, and OAuth app configuration problems. * **Auto Close Without Legacy Plugin:** Change requests can now auto-close without requiring the deprecated Change Management - State Model \[Legacy\] plugin. * **Pipeline Governance and UX Improvements:** Enhanced GitLab pipeline governance, upgraded Node.js version for Azure DevOps extension, Coral default theme with dark mode option, and improved health scan UX. * **MID Server Cluster Support:** Enables load balancing and failover by grouping multiple MID Servers for tool connections. * **Tool Connection Status Automation:** Automatic update of tool connection status from Disconnected to Connected after successful checks unless manually disconnected. * **New Roles for Vulnerability Integration:** Additional roles added to DevOps Tool Owner for managing vulnerability integration plugins like Veracode. * **Pipeline Association for GitHub Actions:** Onboarding now allows selective association of pipelines to the DevOps app, improving control over pipeline tracking. ## Key Changes * Jira and Bitbucket authentication methods updated to OAuth 2.0 3LO and API token with scopes respectively for enhanced security and compliance. * Bearer token authentication introduced for JFrog connections aligning with updated security policies. * Health scans now provide comprehensive findings accessible directly from the DevOps Change Workspace for easier issue resolution. * Ability to override change request start and end times via system properties to better align pipeline auto-close behavior with business needs. * Updated commit logic for additional pipeline step types like Test and Deploy to unify behavior with Prod Deploy steps. * Coral theme introduced as default with a fresh, brand-neutral design and dark mode to enhance user experience across portal, web, and mobile. * Improved support for proxy environments in Docker deployments through environment variable configuration. ## Removals and Deprecations No features or functionalities were removed or deprecated between Zurich and Australia releases. ## Activation and Additional Requirements DevOps Change Velocity continues to be available via the ServiceNow Store. Customers should request installation from the store to activate the product. No additional requirements or browser changes were introduced in these releases. ## Accessibility and Localization The new Coral theme includes a dark mode option to improve readability and reduce eye strain for web and mobile users. No additional localization updates were reported. ## Why This Matters to ServiceNow Customers These enhancements enable stronger security integrations, improved operational efficiency with faster evidence collection, enhanced governance capabilities, and better user experiences through updated themes and UI improvements. Customers can expect streamlined tool connections, more robust health diagnostics, and simplified upgrade paths without losing functionality. The platform's expanded authentication methods and proxy support ensure compliance with evolving enterprise security policies. Overall, these updates help accelerate DevOps workflows while maintaining control and visibility. Consolidated page of all release notes for DevOps Change Velocity from Zurich 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 Zurich 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. {#dfrn3-devopschangevelocity-summary__entry__2} | Release | Release notes | |-|-| | 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. {#dfrn3-devopschangevelocity-summary__entry__8} | Release | Release notes | |-|-| | Zurich | [Rally authentication with OAuth 2.0](https://www.servicenow.com/docs/access?context=setting-up-rally-oauth-2-0-credentials-for-devops&family=zurich&ft:locale=en-US) : Authenticate a Rally tool connection using OAuth 2.0 credentials to strengthen your tool security. [GitHub Data Residency support](https://www.servicenow.com/docs/access?context=playbook-enter-github-instance-details&family=zurich&ft:locale=en-US) : Connect to GitHub Enterprise Server with data residency controls to keep your organization's code and data in your preferred geographic location. [Import based evidence collection](https://www.servicenow.com/docs/access?context=import-based-evidence-collection-for-orchestration-capability&family=zurich&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. | | Australia | [Rally authentication with OAuth 2.0](https://www.servicenow.com/docs/access?context=setting-up-rally-oauth-2-0-credentials-for-devops&family=australia&ft:locale=en-US) : Authenticate a Rally tool connection using OAuth 2.0 credentials to strengthen your tool security. [GitHub Data Residency support](https://www.servicenow.com/docs/access?context=playbook-enter-github-instance-details&family=australia&ft:locale=en-US) : Connect to GitHub Enterprise Server with data residency controls to keep your organization's code and data in your preferred geographic location. | [ ] ## Changes Between your current release family and Australia, some changes were made to existing DevOps Change Velocity features. {#dfrn3-devopschangevelocity-summary__entry__14} | Release | Release notes | |-|-| | Zurich | [Jira authentication with 3LO](https://www.servicenow.com/docs/access?context=connect-a-jira-tool-using-oauth-2-0-with-3lo&family=zurich&ft:locale=en-US) : Authenticate a Jira tool connection using OAuth 2.0 with three-legged OAuth (3LO) to enable secure, delegated access to your Jira account. [Bitbucket Cloud basic authentication using API token with scopes](https://www.servicenow.com/docs/access?context=bitbucket-integration-dev-ops&family=zurich&ft:locale=en-US) : Connect to Bitbucket Cloud using Basic Auth by providing the email address and API token with the required scopes for your Bitbucket Cloud account as app password has been deprecated by Bitbucket. [Enhanced JFrog integration with DevOps Change Velocity](https://www.servicenow.com/docs/access?context=devops-jfrog-connect-workspace&family=zurich&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=zurich&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=zurich&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=zurich&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=zurich&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=zurich&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=zurich&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=zurich&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=zurich&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=zurich&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.  Coral theme : Coral is now the default theme for new portal, web, and mobile experiences with Next Experience or Core UI enabled. This theme provides a fresh look and feel, featuring brand-neutral illustrations to enhance your user experience. A dark theme option is available for web and mobile experiences. [Support for MID Server cluster](https://www.servicenow.com/docs/access?context=playbook-enter-github-instance-details&family=zurich&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=zurich&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=zurich&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=zurich&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=zurich&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. | | Australia | [Jira authentication with 3LO](https://www.servicenow.com/docs/access?context=connect-a-jira-tool-using-oauth-2-0-with-3lo&family=australia&ft:locale=en-US) : Authenticate a Jira tool connection using OAuth 2.0 with three-legged OAuth (3LO) to enable secure, delegated access to your Jira account. [Bitbucket Cloud basic authentication using API token with scopes](https://www.servicenow.com/docs/access?context=bitbucket-integration-dev-ops&family=australia&ft:locale=en-US) : Connect to Bitbucket Cloud using Basic Auth by providing the email address and API token with the required scopes for your Bitbucket Cloud account as app password has been deprecated by Bitbucket. [Enhanced JFrog integration with DevOps Change Velocity](https://www.servicenow.com/docs/access?context=devops-jfrog-connect-workspace&family=australia&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=australia&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=australia&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=australia&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=australia&ft:locale=en-US) : 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. {#dfrn3-devopschangevelocity-summary__entry__20} | Release | Release notes | |-|-| | 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. {#dfrn3-devopschangevelocity-summary__entry__26} | Release | Release notes | |-|-| | Zurich | No updates for this release. | | Australia | No updates for this release. | [ ] ## Activation information Review information on how to activate DevOps Change Velocity. {#dfrn3-devopschangevelocity-summary__entry__32} | Release | Release notes | |-|-| | Zurich | Activation information : Install 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=zurich&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. | | Australia | Activation information : Install DevOps Change Velocity by requesting it from the ServiceNow Store. Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) 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=australia&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 | |-|-| | 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. {#dfrn3-devopschangevelocity-summary__entry__44} | Release | Release notes | |-|-| | 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. {#dfrn3-devopschangevelocity-summary__entry__50} | Release | Release notes | |-|-| | Zurich | Accessibility information : Dark theme : The new Coral theme includes a dark theme option for web and mobile experiences. This option is commonly used to alleviate eye strain and improve readability. | | Australia | 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 | |-|-| | 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. {#dfrn3-devopschangevelocity-summary__entry__62} | Release | Release notes | |-|-| | Zurich | * Improve visibility into your DevOps data in a single system. * Automate the change workflow and approval decisions to increase change velocity while ensuring governance and control. * Track the progress of your work items, commits, artifacts, builds, and releases using the change requests to lend additional transparency and provide a single source of truth to all the personas involved. See [DevOps Change Velocity](https://www.servicenow.com/docs/access?context=devops-landing-page-new&family=zurich&ft:locale=en-US) for more information. | | Australia | * Improve visibility into your DevOps data in a single system. * Automate the change workflow and approval decisions to increase change velocity while ensuring governance and control. * Track the progress of your work items, commits, artifacts, builds, and releases using the change requests to lend additional transparency and provide a single source of truth to all the personas involved. See [DevOps Change Velocity](https://www.servicenow.com/docs/access?context=devops-landing-page-new&family=australia&ft:locale=en-US) for more information. | [ ]