Compare releases

• 9946 - Add feed details to compliance policy input schema
• 10020 - Prevent AutoComplete/MultiSelect popover from blocking the input
• 10021 - Support automatic post-deployment state transitions for Normal ServiceNow CRs
• 10016 - Fixed an issue where the "Configure the Octopus Deploy GitHub App" button on the GitHub Connection onboarding page did not redirect to GitHub
• 10017 - Improve performance of loading large variable sets
• 5489 - Fixed an issue where enabling strict mode in Powershell caused azure steps to fail
• 9981 - Extend compliance policy input schema with potentially required approval for the deployment or runbook run
• 10011 - Improve throughput of ArgoCD application updates

• 10007 - Audience field for OIDC accounts now supports variable substitution
• 10024 - Updated variable description tooltip text so that it is now selectable or clickable
• 9999 - Prevent Projects Page from becoming unresponsive with large numbers of environments

• 10006 - Fixed the JSON Column loading 5 times for EF TPH-mapped properties
• 10004 - Error when saving kubernetes steps when feed id/ feed name uses a variable
• 9962 - Excluded process steps no longer contribute build information in deployment changes
• 9990 - Spaces filter on /scopeduserroles/ API endpoint is ignored
• 9997 - Extend compliance policy input data schema with 'IsConditional' value for every step. This value is se to true when step's run condition is not a default value

• 10002 - Fixed an issue where certain Runbook pages failed to load as a raw variable expression couldn't be parsed as a Git URL

• 10003 - It is now possible to allow Script Console Tasks to run concurrently with other Script Console Tasks and concurrently with scripts on Tentacle Targets
• 9992 - "Fixed batch target/deployment upgrade ignoring filters causing all to be upgraded"
• 9993 - Fix: CSharp script steps now work when using the Octopus Server linux container's built-in worker

Breaking Changes

• 9965 - Update the data model for Feed in preparation for Platform Hub support. This includes a breaking change to the Feed JSON in the audit logs. See the GitHub issue for the changes to the JSON structure if this affects you

Other Changes

• 9989 - Removed support for connecting Octopus Server directly to Azure OpenAI; the OCTOPUSAIClient* environment variables are no longer used. AI-backed features now connect through the Octopus AI proxy for all instances, including self-hosted
• 9996 - Improves handling of deleted branches when deprovisioning ephemeral environments
• 9905 - Upgraded NuGet.Client libraries from 6.14 to 7.3 - includes upstream security fixes and protocol improvements. Breaking changes from NuGet 7.0: package ID validation is now enforced across feed operations (search, download, metadata), and NuGet V3 feeds with mixed HTTP/HTTPS service indices will now raise an error; public feeds are unaffected
• 9994 - Fix issue where Argo CD live status can show an error when sync status is "GitDrift"
• 9985 - Enable Deployment History report by default
• 9986 - Fixed null reference exception for CloudFormation stack deployment with zero changes
• 9987 - Fix: Running Python scripts on the built-in worker in a container based install did not work
• 9839 - Add warning for existing Octopus Server configuration in the installer
• 9970 - Provide possibility to download Deployment History report in CSV format
• 9980 - Fixed incorrect deployment information shown on the Live Status page when paused for manual intervention
• 9979 - Fix process template parameter default value not being fully contributed into variables
• 9974 - Fixed an issue where machine variables were not resolved during git package acquisition
• 9968 - Introduce Deployment History report available in Platform Hub area
• 9972 - Fix subscriptions filtering hiding the search input when there are no results
• 9973 - Polling Tentacles are no longer slower to process work
• 7434 - Azure Container Registry as External Feed - Add support for ACR authentication via Token
• 9969 - Added a filter by scoped sources when determining the status for applications. Now the card shows the correct success status if one of the sources is unscoped
• 9971 - Previous deployment link from deployment page not filtering tasks by tenants or environments correctly
• 9952 - Fix a bug with opening the logs directory from Octopus Manager

• 9966 - Implemented a clickable application status card, and clicking on it opens a drawer with expanded matching "erroneous" applications
• 9964 - Fixed project group filter getting stuck when using breadcrumb

• 9963 - Include runbooks in compatibility checks when converting a project to use version control
• 9934 - Fix package acquisition information fetching for SPF steps
• 9803 - Fixed project variables losing Open Editor option in the UI
• 9951 - Fix aws-iam-authenticator warning for AWS regions

• 9961 - Argo Steps cannot clone git repositories from self-hosted Azure Devops (ADO)
• 9954 - Fix issue where prompted variable values are ignored when scoped to parent ephemeral environment
• 9952 - Fix a bug with opening the logs directory from Octopus Manager
• 9930 - GitHub Connections now available in Platform Hub

• 9955 - A region is required when creating or updating AWS accounts
• 9928 - Added additional telemetry about the underlying hardware running the Octopus Server to better understand performance characteristics

• 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