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 2023.4.8082 to 2024.1.2059

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.

Octopus 2023.4

The 2023.4 release of Octopus Deploy has a number of updates to make your deployments simpler to manage and more resilient.

This release’s noteworthy updates include:

  • More secure connectivity to GitHub and Azure using OpenID Connect (OIDC)
  • Source scripts from Git to maintain them like other assets
  • Resilient Tentacle communications to reduce deployment failures
  • Elevate critical tasks to the top of the task queue
  • Connect tenants to multiple projects in one step
  • Space ID now available on Terraform resources to simplify configuration

The 2023 Q4 release is available on Octopus Cloud and ready for download by our self-hosted customers.

Release notes

These are the features and fixes you'll get by upgrading from 2023.4.8082 to 2024.1.2059.

Changes in Octopus Server 2024.1.2059

  • 8558 - Added support for authenticating to the Octopus API using OpenID Connect
  • 8469 - Fixed a broken link from the Audit screen to a Scoped User Role

Changes in Octopus Server 2024.1.1743

  • 7996 - Fix incorrect task duration when using manual intervention steps
  • 7468 - Deployment task page shows incorrect "ran for" time for process with Manual Intervention step
  • 8475 - Fix publish button UI for runbook snapshots
  • 8476 - The upload to S3 step now only allows package selection from compatible feeds
  • 8473 - Fixed an error when interacting with a version controlled deployment process with a system level team as the responsible team on a Manual intervention step
  • 8465 - Fix saving step templates that reference a script in a git repository
  • 8461 - Update all Tasks pages to show Running/Waiting/Completed tabs
  • 8470 - Support OCI feed sub-paths in Harbor
  • 8466 - Added a performance feedback survey to the navigation bar
  • 8455 - Fixed an issue where the project versioning strategy could be put in an invalid state
  • 8458 - Running and waiting task counts should now display the correct number of tasks when filters are applied
  • 8457 - Allow user to cancel server task from the Tasks list
  • 8532 - Reduced default concurrent message pumps to alleviate thread pool pressure
  • 8464 - Fixed Add/Modify ProjectGroup returning 500 when it should return 409
  • 8429 - Increased the default number of Thread Pool threads and Database Connections

Changes in Octopus Server 2024.1.746

  • 8459 - Fixed issue with the Deploy Raw Kubernetes Yaml step where you couldn’t save when sourcing yaml from a Git Repository
  • 8448 - Waiting tasks are now displayed in the expected execution order on the Tasks page. Each queued task displays its respective placement in the queue
  • 8450 - Make server task prioritization part of the public API
  • 8441 - Add container options to k8s targets
  • 8447 - Reduced the amount of data loaded to display teams in the UI

Changes in Octopus Server 2024.1.437

  • 8452 - Fixed a bug on the Tasks page which caused paging to not work
  • 8453 - Deployment Target and Worker lists now display the target type
  • 8449 - ReferenceIds on StepFramework steps are incorrectly updated when updating step versions, this leads to a mismatch between the referenceId and StepPackageInputsReferenceId causing deployment failures
  • 8446 - Add support for sub paths on an OCI registry feed URI
  • 8635 - Converted ProjectGroup document persistence from JSON store to relational model
  • 8445 - "Move to Top" option is missing for queued server tasks
  • 8329 - Added support for Inline Execution Containers
  • 8402 - Added tooltips to accommodate for long project names in the project-switcher
  • 8436 - Separate the table on the Tasks page into three tabs - Running, Waiting and Completed
  • 8442 - Scripts can now be sourced from Git repositories
  • 8406 - Changed Netfx Calamari filesystem recursive operations to use the .NetFramework provided methods instead of AlphaFS due to performance issues

Changes in Octopus Server 2023.4.8082

  • 8558 - Added support for authenticating to the Octopus API using OpenID Connect
  • 8465 - Fix saving step templates that reference a script in a git repository
  • 8470 - Support OCI feed sub-paths in Harbor
  • 8532 - Reduced default concurrent message pumps to alleviate thread pool pressure
  • 8429 - Increased the default number of Thread Pool threads and Database Connections
  • 8447 - Reduced the amount of data loaded to display teams in the UI
  • 8449 - ReferenceIds on StepFramework steps are incorrectly updated when updating step versions, this leads to a mismatch between the referenceId and StepPackageInputsReferenceId causing deployment failures
  • 8446 - Add support for sub paths on an OCI registry feed URI
  • 8442 - Scripts can now be sourced from Git repositories
  • 8406 - Changed Netfx Calamari filesystem recursive operations to use the .NetFramework provided methods instead of AlphaFS due to performance issues