| \n\nWashington DC\n\n | \n\n- **[Enhanced automated change creation](https://www.servicenow.com/docs/access?context=automate-devops-change-request&family=washingtondc&ft:locale=en-US)**\n\nAvoid issues that might occur in the automated change request creation guided procedure because of the tool connection state.\n\n- **[New state transition flows for DevOps change model](https://www.servicenow.com/docs/access?context=devops-change-multimodel&family=washingtondc&ft:locale=en-US)**\n\nMove and track changes through added transition flows for the Change - DevOps - New and Change - DevOps - Schedule states in the DevOps change model.\n\n- **[Error handling for DevOps flows](https://www.servicenow.com/docs/access?context=dev-ops-change-acceleration&family=washingtondc&ft:locale=en-US)**\n\nView 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.\n\n- **[DevOpsChangeRelationshipHelper script to retrieve change data](https://www.servicenow.com/docs/access?context=retrieve-change-request-data-using-devopschangerelationshiphelper-script&family=washingtondc&ft:locale=en-US)**\n\nRetrieve data associated with a change request based on the specified relation type using the `DevOpsChangeRelationshipHelper` script include.\n\n- **[New property to specify retry limit](https://www.servicenow.com/docs/access?context=dev-ops-administration&family=washingtondc&ft:locale=en-US)**\n\nSpecify 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.\n\n- **[Import request restart](https://www.servicenow.com/docs/access?context=app-create-workspace&family=washingtondc&ft:locale=en-US)**\n\nRestart an import request from the Import Request record that couldn’t be completed due to an error.\n\n- **[Automatically associate repositories](https://www.servicenow.com/docs/access?context=apps-associate-objects-wkspc&family=washingtondc&ft:locale=en-US)**\n\nRepositories are automatically associated to applications when a corresponding pipeline identifies commits of repositories that are not yet associated.\n\n- **[Unit test type support for GitHub](https://www.servicenow.com/docs/access?context=dev-ops-test-tool-integration&family=washingtondc&ft:locale=en-US)**\n\nAutomatically publish unit test results of types NUnit, pytest, jest, JUnit, and XUnit from GitHub Actions workflows without any custom Application Programming Interface \\(API\\) calls.\n\n- **[Change request creation with errors in DevOps data retrieval](https://www.servicenow.com/docs/access?context=change-request-creation-with-devops-data-retrieval-errors&family=washingtondc&ft:locale=en-US)**\n\nEnable change request creation even if there is an error in retrieving the DevOps data in a pipeline.\n\n- **[Multiple ServiceNow DevOps configurations in the same Jenkins instance](https://www.servicenow.com/docs/access?context=configure-webhooks-manually-for-jenkins&family=washingtondc&ft:locale=en-US)**\n\nConfigure multiple ServiceNow DevOps connections in one Jenkins server.\n\n- **[Custom actions for GitLab using Docker](https://www.servicenow.com/docs/access?context=servicenow-custom-actions-for-gitlab&family=washingtondc&ft:locale=en-US)**\n\nRetrieve 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.\n\n- **Manual retry of downstream events**\n\nIf 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.\n\n- **[Enhancements to DevOps Model change](https://www.servicenow.com/docs/access?context=devops-change-multimodel&family=washingtondc&ft:locale=en-US)**\n - In-product guidance enables you to leverage DevOps models and easily create DevOps changes without disruption of your change process.\n - To make the Change - DevOps – Implement flow of the DevOps model more suitable for DevOps changes, change tasks are no longer automatically created.\n - 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.\n - 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.\n- **[Branch details for artifacts and packages](https://www.servicenow.com/docs/access?context=using-dev-ops-release-change&family=washingtondc&ft:locale=en-US)**\n\nBranch details from pipeline executions are now available for artifacts and packages for better tracking.\n\n- **[Create lists](https://www.servicenow.com/docs/access?context=add-new-list-in-list-module&family=washingtondc&ft:locale=en-US)**\n\nOption to create customized lists added to the Changes, Tools, and Administration modules in the DevOps Change Workspace.\n\n- **[Jira Server connection using API key](https://www.servicenow.com/docs/access?context=create-jira-tool-dev-ops&family=washingtondc&ft:locale=en-US)**\n\nConnect to your Jira Server using API key authentication rather than basic authentication.\n\n- **[GitHub Actions reruns](https://www.servicenow.com/docs/access?context=github-actions-integration-with-devops&family=washingtondc&ft:locale=en-US)**\n\nRe-running failed GitHub jobs will now use the existing change request created for the failed jobs instead of creating new change requests.\n\n- **[Generalized Docker Container solution to support any orchestration tool](https://www.servicenow.com/docs/access?context=servicenow-custom-actions-for-gitlab&family=washingtondc&ft:locale=en-US)**\n\nUse 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.\n\n- **[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=washingtondc&ft:locale=en-US)**\n\nIntegrate 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.\n\n- **[Default BitBucket branch property](https://www.servicenow.com/docs/access?context=dev-ops-administration&family=washingtondc&ft:locale=en-US)**\n\nSpecify the default Bitbucket branch name that must be used to create an import request in the **sn\\_devops.bitbucket\\_default\\_branch** property.\n\n\n |
| \n\nXanadu\n\n | \n\n- **[Reflow for configurable workspace](https://www.servicenow.com/docs/access?context=auto-reflow&family=xanadu&ft:locale=en-US)**\n\nDevOps 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://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown) section that follows.\n\n- **[DevOps data in change request](https://www.servicenow.com/docs/access?context=create-change-sow&family=xanadu&ft:locale=en-US)**\n\nView, 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.\n\n- **[Enhancements to DevOps Model change](https://www.servicenow.com/docs/access?context=devops-change-multimodel&family=xanadu&ft:locale=en-US)**\n - In-product guidance enables you to leverage DevOps models and easily create DevOps changes without disruption of your change process.\n - To make the Change - DevOps – Implement flow of the DevOps model more suitable for DevOps changes, change tasks are no longer automatically created.\n - 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.\n - 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.\n- **[Branch details for artifacts and packages](https://www.servicenow.com/docs/access?context=using-dev-ops-release-change&family=xanadu&ft:locale=en-US)**\n\nBranch details from pipeline executions are now available for artifacts and packages for better tracking.\n\n- **[Create lists](https://www.servicenow.com/docs/access?context=add-new-list-in-list-module&family=xanadu&ft:locale=en-US)**\n\nOption to create customized lists added to the Changes, Tools, and Administration modules in the DevOps Change Workspace.\n\n- **[Jira Server connection using API key](https://www.servicenow.com/docs/access?context=create-jira-tool-dev-ops&family=xanadu&ft:locale=en-US)**\n\nConnect to your Jira Server using API key authentication rather than basic authentication.\n\n- **[GitHub Actions reruns](https://www.servicenow.com/docs/access?context=github-actions-integration-with-devops&family=xanadu&ft:locale=en-US)**\n\nRe-running failed GitHub jobs will now use the existing change request created for the failed jobs instead of creating new change requests.\n\n- **[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)**\n\nUse 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.\n\n- **[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)**\n\nIntegrate 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.\n\n- **[Enhanced manual DevOps change creation experience](https://www.servicenow.com/docs/access?context=create-change-sow&family=xanadu&ft:locale=en-US)**\n\nAdd work items data in a manually created DevOps change request in Service Operations Workspace for ITSM.\n\n- **[Default BitBucket branch property](https://www.servicenow.com/docs/access?context=dev-ops-administration&family=xanadu&ft:locale=en-US)**\n\nSpecify the default Bitbucket branch name that must be used to create an import request in the **sn\\_devops.bitbucket\\_default\\_branch** property.\n\n- **[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)**\n\nAdditional 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.\n\n- **[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)**\n\nImport pull-request records for Bitbucket Server or Data Center for improved insights and efficiency.\n\n- **[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)**\n\nEnable change request creation even if there is an error in retrieving the DevOps data for a Harness pipeline.\n\n- **[Branch name filter](https://www.servicenow.com/docs/access?context=create-devops-change-request-manual&family=xanadu&ft:locale=en-US)**\n\nSearch for build numbers by the branch name while associating DevOps data to a change request in the Service Operations Workspace \\(SOW\\) or Classic UI.\n\n- **[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)**\n\nThe servicenow-devops-test-report custom action in GitHub now includes an optional test-summary-name parameter to specify the test summary results name.\n\n- **[Token based authentication for Rally](https://www.servicenow.com/docs/access?context=configure-webhooks-for-rally-manually&family=xanadu&ft:locale=en-US)**\n\nConfigure webhooks for Rally using token based authentication instead of using the integration username and password.\n\n- **[Renamed variables for Docker](https://www.servicenow.com/docs/access?context=servicenow-custom-actions-for-gitlab&family=xanadu&ft:locale=en-US)**\n\nThe environmental variables in the Generic Docker actions for DevOps Change Velocity have been renamed by removing the CI prefix for better clarity.\n\n- **[Security scan results](https://www.servicenow.com/docs/access?context=dev-ops-change-acceleration&family=xanadu&ft:locale=en-US)**\n\nSecurity scan results on the change record associated to a pipeline execution with a linked package are now displayed in the **Security Summaries** tab.\n\n- **[Source of commits in SOW](https://www.servicenow.com/docs/access?context=create-change-sow&family=xanadu&ft:locale=en-US)**\n\nView 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.\n\n- **[Track file changes](https://www.servicenow.com/docs/access?context=sc-github&family=xanadu&ft:locale=en-US)**\n\nThe **Track file changes** option is now disabled by default when a repository is configured to prevent any potential security risks.\n\n- **[Close code value for a change request](https://www.servicenow.com/docs/access?context=dev-ops-administration&family=xanadu&ft:locale=en-US)**\n\nTwo 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.\n\n- **[Support for MID Server cluster](https://www.servicenow.com/docs/access?context=playbook-enter-github-instance-details&family=xanadu&ft:locale=en-US)**\n\nImprove 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.\n\n- **[Improved UX for DevOps Change health scans](https://www.servicenow.com/docs/access?context=run-health-scan-check&family=xanadu&ft:locale=en-US)**\n\nRun health scans and analyze findings efficiently in the DevOps Change workspace with an intuitive and user-friendly interface.\n\n- **[Pipeline association for GitHub Actions](https://www.servicenow.com/docs/access?context=sc-github&family=xanadu&ft:locale=en-US)**\n\nWhen 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.\n\n- **[Tool connection check status](https://www.servicenow.com/docs/access?context=devops-reference-error-messages&family=xanadu&ft:locale=en-US)**\n\nIf 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.\n\n- **[New roles for vulnerability integration](https://www.servicenow.com/docs/access?context=installed-with-dev-ops&family=xanadu&ft:locale=en-US)**\n - 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.\n - 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.\n\n |
| \n\nYokohama\n\n | \n\n- **[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)**\n\nIntegrate orchestration tools that aren’t supported in the base system by leveraging a generic framework.\n\n- **[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)**\n\nAdd custom fields into your planning tool integration to improve configurability and access business-specific information, which facilitates more informed decision-making.\n\n- **[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)**\n\nAdditional 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.\n\n- **[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)**\n\nImport pull-request records for Bitbucket Server or Data Center for improved insights and efficiency.\n\n- **[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)**\n\nEnable change request creation even if there is an error in retrieving the DevOps data for a Harness pipeline.\n\n- **[Branch name filter](https://www.servicenow.com/docs/access?context=create-devops-change-request-manual&family=yokohama&ft:locale=en-US)**\n\nSearch for build numbers by the branch name while associating DevOps data to a change request in the Service Operations Workspace \\(SOW\\) or Classic UI.\n\n- **[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)**\n\nThe servicenow-devops-test-report custom action in GitHub now includes an optional test-summary-name parameter to specify the test summary results name.\n\n- **[Token based authentication for Rally](https://www.servicenow.com/docs/access?context=configure-webhooks-for-rally-manually&family=yokohama&ft:locale=en-US)**\n\nConfigure webhooks for Rally using token based authentication instead of using the integration username and password.\n\n- **[Renamed variables for Docker](https://www.servicenow.com/docs/access?context=servicenow-custom-actions-for-gitlab&family=yokohama&ft:locale=en-US)**\n\nThe environmental variables in the Generic Docker actions for DevOps Change Velocity have been renamed by removing the CI prefix for better clarity.\n\n- **[Security scan results](https://www.servicenow.com/docs/access?context=dev-ops-change-acceleration&family=yokohama&ft:locale=en-US)**\n\nSecurity scan results on the change record associated to a pipeline execution with a linked package are now displayed in the **Security Summaries** tab.\n\n- **[Source of commits in SOW](https://www.servicenow.com/docs/access?context=create-change-sow&family=yokohama&ft:locale=en-US)**\n\nView 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.\n\n- **[Track file changes](https://www.servicenow.com/docs/access?context=sc-github&family=yokohama&ft:locale=en-US)**\n\nThe **Track file changes** option is now disabled by default when a repository is configured to prevent any potential security risks.\n\n- **[Close code value for a change request](https://www.servicenow.com/docs/access?context=dev-ops-administration&family=yokohama&ft:locale=en-US)**\n\nTwo 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.\n\n- **[Support for MID Server cluster](https://www.servicenow.com/docs/access?context=playbook-enter-github-instance-details&family=yokohama&ft:locale=en-US)**\n\nImprove 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.\n\n- **[Improved UX for DevOps Change health scans](https://www.servicenow.com/docs/access?context=run-health-scan-check&family=yokohama&ft:locale=en-US)**\n\nRun health scans and analyze findings efficiently in the DevOps Change workspace with an intuitive and user-friendly interface.\n\n- **[Pipeline association for GitHub Actions](https://www.servicenow.com/docs/access?context=sc-github&family=yokohama&ft:locale=en-US)**\n\nWhen 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.\n\n- **[Tool connection check status](https://www.servicenow.com/docs/access?context=devops-reference-error-messages&family=yokohama&ft:locale=en-US)**\n\nIf 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.\n\n- **[New roles for vulnerability integration](https://www.servicenow.com/docs/access?context=installed-with-dev-ops&family=yokohama&ft:locale=en-US)**\n - 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.\n - 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.\n- **[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)**\n\nUpdate 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.\n\n- **[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)**\n\nSet 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.\n\n- **[Node version of DevOps extension](https://www.servicenow.com/docs/access?context=config-dev-ops-extensions-azure&family=yokohama&ft:locale=en-US)**\n\nThe node version of the ServiceNow DevOps extension has been upgraded to version 20.x in Azure DevOps.\n\n- **[Enhanced pipeline governance in GitLab](https://www.servicenow.com/docs/access?context=servicenow-custom-actions-for-gitlab&family=yokohama&ft:locale=en-US)**\n\nView change request details like status, sys\\_id, priority in the GitLab console when a change request is created in GitLab using Docker image.\n\n- **[Health scan enhancements](https://www.servicenow.com/docs/access?context=run-health-scan-check&family=yokohama&ft:locale=en-US)**\n - Identify outdated or prolonged discover and import requests using the DevOps -Stale or Long-Running Discover and Import Requests health check.\n - 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.\n - Identify OAuth app configuration issues for GitHub tools in the connected state using the DevOps webhook configuration analysis health check.\n - Verify if any scheduled job has been configured to run as an invalid or non-admin user.\n - Navigate to the Findings list from the DevOps Change Workspace home page by selecting **View all findings ** in the Health scan findings widget. \n- **[Enhanced JFrog integration with DevOps Change Velocity](https://www.servicenow.com/docs/access?context=devops-jfrog-connect-workspace&family=yokohama&ft:locale=en-US)**\n\nGather JFrog evidence seamlessly and create change records automatically using the improved JFrog integration with DevOps Change Velocity.\n\n- **[Bearer authentication in JFrog](https://www.servicenow.com/docs/access?context=devops-jfrog-connect-workspace&family=yokohama&ft:locale=en-US)**\n\nConnect to JFrog using the secure bearer token authentication to comply with JFrog’s updated security policies.\n\n- **[HTTP proxy for Docker](https://www.servicenow.com/docs/access?context=servicenow-custom-actions-for-gitlab&family=yokohama&ft:locale=en-US)**\n\nConnect to DevOps Change Velocity through HTTP proxy settings using environment variables in your Docker deployment for instances that run a proxy server.\n\n- **[Health scan enhancements](https://www.servicenow.com/docs/access?context=run-health-scan-check&family=yokohama&ft:locale=en-US)**\n - Identify any callback processing issues in your instance.\n - Identify any access control rule \\(ACL\\) that is incorrectly associated with a role in your instance.\n - Verify whether all DevOps tables are present in your instance and confirm whether all metadata in sys\\_\\* tables is present.\n - Verify whether all DevOps roles in your instance contain all expected roles, including inherited roles.\n- **[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)**\n\nChange requests can now be auto-closed without requiring you to install the Change Management - State Model \\[Legacy\\] plugin.\n\n\n |
| \n\nZurich\n\n | \n\n- **[Support for MID Server cluster](https://www.servicenow.com/docs/access?context=playbook-enter-github-instance-details&family=zurich&ft:locale=en-US)**\n\nImprove 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.\n\n- **[Improved UX for DevOps Change health scans](https://www.servicenow.com/docs/access?context=run-health-scan-check&family=zurich&ft:locale=en-US)**\n\nRun health scans and analyze findings efficiently in the DevOps Change workspace with an intuitive and user-friendly interface.\n\n- **[Pipeline association for GitHub Actions](https://www.servicenow.com/docs/access?context=sc-github&family=zurich&ft:locale=en-US)**\n\nWhen 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.\n\n- **[Tool connection check status](https://www.servicenow.com/docs/access?context=devops-reference-error-messages&family=zurich&ft:locale=en-US)**\n\nIf 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.\n\n- **[New roles for vulnerability integration](https://www.servicenow.com/docs/access?context=installed-with-dev-ops&family=zurich&ft:locale=en-US)**\n - 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.\n - 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.\n- **[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)**\n\nUpdate 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.\n\n- **[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)**\n\nSet 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.\n\n- **[Node version of DevOps extension](https://www.servicenow.com/docs/access?context=config-dev-ops-extensions-azure&family=zurich&ft:locale=en-US)**\n\nThe node version of the ServiceNow DevOps extension has been upgraded to version 20.x in Azure DevOps.\n\n- **[Enhanced pipeline governance in GitLab](https://www.servicenow.com/docs/access?context=servicenow-custom-actions-for-gitlab&family=zurich&ft:locale=en-US)**\n\nView change request details like status, sys\\_id, priority in the GitLab console when a change request is created in GitLab using Docker image.\n\n- **[Health scan enhancements](https://www.servicenow.com/docs/access?context=run-health-scan-check&family=zurich&ft:locale=en-US)**\n - Identify outdated or prolonged discover and import requests using the DevOps -Stale or Long-Running Discover and Import Requests health check.\n - 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.\n - Identify OAuth app configuration issues for GitHub tools in the connected state using the DevOps webhook configuration analysis health check.\n - Verify if any scheduled job has been configured to run as an invalid or non-admin user.\n - Navigate to the Findings list from the DevOps Change Workspace home page by selecting **View all findings ** in the Health scan findings widget. \n- **[Enhanced JFrog integration with DevOps Change Velocity](https://www.servicenow.com/docs/access?context=devops-jfrog-connect-workspace&family=zurich&ft:locale=en-US)**\n\nGather JFrog evidence seamlessly and create change records automatically using the improved JFrog integration with DevOps Change Velocity.\n\n- **[Bearer authentication in JFrog](https://www.servicenow.com/docs/access?context=devops-jfrog-connect-workspace&family=zurich&ft:locale=en-US)**\n\nConnect to JFrog using the secure bearer token authentication to comply with JFrog’s updated security policies.\n\n- **[HTTP proxy for Docker](https://www.servicenow.com/docs/access?context=servicenow-custom-actions-for-gitlab&family=zurich&ft:locale=en-US)**\n\nConnect to DevOps Change Velocity through HTTP proxy settings using environment variables in your Docker deployment for instances that run a proxy server.\n\n- **[Health scan enhancements](https://www.servicenow.com/docs/access?context=run-health-scan-check&family=zurich&ft:locale=en-US)**\n - Identify any callback processing issues in your instance.\n - Identify any access control rule \\(ACL\\) that is incorrectly associated with a role in your instance.\n - Verify whether all DevOps tables are present in your instance and confirm whether all metadata in sys\\_\\* tables is present.\n - Verify whether all DevOps roles in your instance contain all expected roles, including inherited roles.\n- **[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)**\n\nChange requests can now be auto-closed without requiring you to install the Change Management - State Model \\[Legacy\\] plugin.\n\n\n |
| \n\nAustralia\n\n | \n\n- **[Enhanced JFrog integration with DevOps Change Velocity](https://www.servicenow.com/docs/access?context=devops-jfrog-connect-workspace&family=australia&ft:locale=en-US)**\n\nGather JFrog evidence seamlessly and create change records automatically using the improved JFrog integration with DevOps Change Velocity.\n\n\n- **[Bearer authentication in JFrog](https://www.servicenow.com/docs/access?context=devops-jfrog-connect-workspace&family=australia&ft:locale=en-US)**\n\nConnect to JFrog using the secure bearer token authentication to comply with JFrog’s updated security policies.\n\n\n- **[HTTP proxy for Docker](https://www.servicenow.com/docs/access?context=servicenow-custom-actions-for-gitlab&family=australia&ft:locale=en-US)**\n\nConnect to DevOps Change Velocity through HTTP proxy settings using environment variables in your Docker deployment for instances that run a proxy server.\n\n- **[Health scan enhancements](https://www.servicenow.com/docs/access?context=run-health-scan-check&family=australia&ft:locale=en-US)**\n - Identify any callback processing issues in your instance.\n - Identify any access control rule \\(ACL\\) that is incorrectly associated with a role in your instance.\n - Verify whether all DevOps tables are present in your instance and confirm whether all metadata in sys\\_\\* tables is present.\n - Verify whether all DevOps roles in your instance contain all expected roles, including inherited roles.\n- **[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)**\n\nChange requests can now be auto-closed without requiring you to install the Change Management - State Model \\[Legacy\\] plugin.\n\n\n |
\n