Compare releases
Compare releases and check for compatibility between your existing Octopus Server and new releases.
What's new
These are the most important features you'll get by upgrading from 2026.1.11242 to 2026.2.3409
Octopus 2026.2 3 breaking changes
Release notes
These are the features and fixes you'll get by upgrading from 2026.1.11242 to 2026.2.3409.
Changes in Octopus Server 2026.2.3409
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
Changes in Octopus Server 2026.2.3060
Breaking Changes
- 9935 - Removed the deprecated POST /projects/{projectId}/git/branches/ API endpoint
Other Changes
Changes in Octopus Server 2026.2.2825
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
- 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
Changes in Octopus Server 2026.2.999
- 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
Changes in Octopus Server 2026.2.742
- 9910 - Add new
Modify via Helmdialog 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
Changes in Octopus Server 2026.2.223
- 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
Changes in Octopus Server 2026.2.111
- 9901 - Fixes overrun limit not respected in the UI
Changes in Octopus Server 2026.2.61
- 9898 - Added the ability for administrators of self-hosted instances to enable exporting OpenTelemetry traces to disk for diagnostic purposes