| \n\nYokohama\n\n | \n\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 - **[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\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\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\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\n |
| \n\nZurich\n\n | \n\n- **[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)**\n\nAuthenticate a Jira tool connection using OAuth 2.0 with three-legged OAuth \\(3LO\\) to enable secure, delegated access to your Jira account.\n\n- **[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)**\n\nConnect 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.\n\n\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 - **[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\n - **Coral theme**\n\nCoral 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.\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\n |
| \n\nAustralia\n\n | \n\n- **[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)**\n\nAuthenticate a Jira tool connection using OAuth 2.0 with three-legged OAuth \\(3LO\\) to enable secure, delegated access to your Jira account.\n\n- **[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)**\n\nConnect 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.\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- **[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- **[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