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 2024.1.11865 to 2024.2.1310

Octopus 2024.2

No highlights for 2024.2

Octopus 2024.1

The 2024.1 release of Octopus Deploy has updates to make your deployments simpler to manage and more secure and efficient.

This release’s noteworthy updates include:

  • More secure connectivity to AWS using OpenID Connect (OIDC)
  • Artifactory Generic Repositories now supported in Octopus
  • Faster feedback loops with inline execution containers
  • Improved performance with Octopus Server upgraded to .NET 8
  • Building on Resilient Tentacle Communications
  • Improved page layouts for easier navigation

The 2024 Q1 release is already available on Octopus Cloud and now ready for download by our self-hosted customers.

Breaking changes

Workers and Targets Running Windows Server 2003 and unpatched Windows Server 2008 Operating Systems will no longer be functional

Recent updates to our execution engine necessitate the minimal requirement of .NET 4.6.2 on Windows Targets and Workers. Due to the support capabilities of the .NET Framework, this requirement excludes Windows 2003 Servers, and Windows 2008 Servers that do not have the latest service patches installed.

Learn more about this change in the GitHub issue.

Release notes

These are the features and fixes you'll get by upgrading from 2024.1.11865 to 2024.2.1310.

Changes in Octopus Server 2024.2.1310

  • 8664 - Fixed regression that prevented guest users from viewing config as code projects
  • 8659 - Converted RunbookRunHistory document persistence from JSON store to relational model

Changes in Octopus Server 2024.2.855

Breaking Changes
  • 8615 - Breaking change: Internal changes made to Kustomize step resulting in slight UI differences and OCL changes. The only breaking change is the payload to create the Kustomize step via the API is slightly different so any existing external api calls that attempt to create the Kustomize step with the old payload will fail
Other Changes
  • 7461 - Migrated from ADAL to MSAL for Azure service principal accounts. This change applies to fetching authentication tokens, which are consumed by the management clients for storage accounts, resource groups, and web apps

Changes in Octopus Server 2024.2.534

  • 8651 - Allow the configuration of an OIDC Issuer URL. This will override the Server URL and allow reverse proxies and GHA workers that interact with a bound URL
  • 8652 - Display 'Missing resource' text instead of permission error for project variables
  • 8654 - Always keep "edit" button visible in Tenant Variables page
  • 8636 - Show Octopus version for nodes listed on node page
  • 8467 - Fixed an issue preventing the slugs of existing lifecycles from being updated
  • 8650 - AWS accounts with OIDC used on Terraform steps fails to login with error.

Changes in Octopus Server 2024.2.101

  • 8646 - Improve loading of required accounts, certificates and worker pools on project tenant variables
  • 7481 - Fixed runbook or deployment process scoped worker-pool variable resolution
  • 8258 - Fixed runbook or deployment process scoped account variable resolution
  • 8571 - Fixed an issue that prevented users from setting a default channel on a project
  • 8576 - Fixed an issue where SupplementalGroups and RunAsUserId were not populated in the Edit Yaml section for the "Deploy a Kubernetes container" step

Changes in Octopus Server 2024.1.11865

  • 8651 - Allow the configuration of an OIDC Issuer URL. This will override the Server URL and allow reverse proxies and GHA workers that interact with a bound URL
  • 8650 - AWS accounts with OIDC used on Terraform steps fails to login with error.
  • 8646 - Improve loading of required accounts, certificates and worker pools on project tenant variables
  • 7481 - Fixed runbook or deployment process scoped worker-pool variable resolution
  • 8258 - Fixed runbook or deployment process scoped account variable resolution
  • 8571 - Fixed an issue that prevented users from setting a default channel on a project
  • 8576 - Fixed an issue where SupplementalGroups and RunAsUserId were not populated in the Edit Yaml section for the "Deploy a Kubernetes container" step