Compare releases

• 9949 - Fixed an issue where waiting for multiple pull requests would only actually wait on the last created pull request
• 9950 - Fixed an issue where Argo CD steps fail to clone the Git repository if project references an OIDC account
• 9942 - Inside the live status object tree, nested resources with the failed health status are not visible by default
• 9947 - Use unique email as default for admin user when not supplied in the docker ENV
• 9948 - Add Project Template information to compliance policies input data
• 9944 - ArgoCD Application verification now covers cases apps which weren't updated by the deployment
• 9943 - Adds Running Tasks Dashboard to Workers page
• 9934 - Fix package acquisition information fetching for SPF steps
• 9940 - Fixed an issue where user Display Name updates applied via the SCIM API could fail if the user did not already have a Display Name

Breaking Changes

• 9936 - Removed the deprecated GET /reporting/deployments-counted-by-week API endpoint

Other Changes

• 9941 - Fix code editor causing the page to error
• 9940 - Fixed an issue where user Display Name updates applied via the SCIM API could fail if the user did not already have a Display Name
• 9938 - Fix incorrect ArgoCD sync status
• 9937 - V2 Executions Pipeline Self-Host Telemetry: Fix Server Task durations and add queue time

Breaking Changes

• 9935 - Removed the deprecated POST /projects/{projectId}/git/branches/ API endpoint

Other Changes

• 9916 - Visting live status page for environment with no deployments displays an error
• 9927 - Improved distribution of background processing across nodes in high-availability Octopus Server deployments, redistributing some work away from nodes with a Task Cap of 0

Breaking Changes

• 9933 - Removed the deprecated GET /projects/{projectId}/runbooks/all API endpoint

Other Changes

• 9929 - Update Argo CD Application Image Tags and Update Argo CD Application Manifests steps will now fail fast if there is no found Argo CD applications in the target deployment environment
• 9920 - Update Octopus Server's Autofac dependency to 9.1.0
• 9925 - Introduce new endpoint to return paginated set of platform hub policy versions
• 9922 - Released Project Templates as an Open Alpha feature for Enterprise customers
• 9921 - Changed bash Calamari installation scripts to better support concurrency
• 9919 - Unable to create a Release with non-semver versioning
• 9888 - Fixed issue with variable expressions when accessing index 0 in a JSON array
• 9918 - Fixed issue with evaluating variable expressions on a target when accessing index 0 in a JSON array
• 9907 - Cloning a step keeps package reference after updating to a different source
• 9917 - Fixed version control onboarding copy and Platform Hub version control settings nav label
• 9912 - Azure Cloud Target steps are no longer recognised as valid Octopus steps.
• 9914 - Fixed an issue where an error could occur when navigating through the Kubernetes Agent/Worker installation dialog
• 9915 - Fixed an issue with the deploy a release step in process templates outside of the default space failing to resolve the release version and failing deployments

• 9906 - Tasks list option for "All" not showing Timed Out tasks correctly
• 9913 - Implement a custom color picker directly within the Tenant Tag color selection dialog
• 9911 - Kubernetes live status tooltips now display the specific reason a resource has an Unknown health or sync status, instead of generic text
• 9909 - Added octopus variable to override NuGet source for dotnet scripts
• 9908 - Fixed an issue where package extraction does not respect build metadata

• 9910 - Add new Modify via Helm dialog to the Kubernetes agent/worker settings overflow menu. This can be used to get a Helm command for modifying the Helm release for the agent/worker
• 9904 - When Manual Intervention is used as the child of a step without target tags, other child steps do not wait for it to be resolved
• 9903 - Always display invalid compliance policies in the Server Task logs

• 9896 - Server restart now required to stop background work on UI nodes. We have updated how work gets done in the background on Octopus Server nodes, and a restart will now be required in order to stop/start background work on UI nodes where the task cap is 0. This change also stops deployment and runbook work being done on UI nodes

• 9901 - Fixes overrun limit not respected in the UI

• 9898 - Added the ability for administrators of self-hosted instances to enable exporting OpenTelemetry traces to disk for diagnostic purposes