Compare releases

Compare releases

Find out what's new in the latest Octopus Deploy release, or compare the latest release to what you're currently running to see what's changed.


These are the most important features you'll get by upgrading from 2019.3.3 to 2019.5.3

Octopus 2019.3


Octopus Server 2019.3 LTS is a roll-up release of Octopus 2019.1 and Octopus 2019.2 and the headline feature is Spaces which enables teams to group projects, environments, tenants, step templates, and other resources into a Space. It also includes a large number of enhancements and bug fixes along with database performance and cloud dependency updates.

Read our blog post to learn more.

Breaking changes

This release includes numerous break changes from the introduction of Spaces. Refer to the Octopus Deploy 2019.1 release highlights for the full details.

Octopus 2019.4


  • Build information and work item tracking captures work items and build details and surfaces them with links to the appropriate sites.
  • Generate and share release notes automatically enables teams to view and share the work items associated with releases and deployments.
  • Octopus integration with Jira which provides two-way links between your Jira issues and your deployments.

Read our blog post to learn more.

Breaking Changes

There are some very slight changes to the format of the output returned by the Octopus.Server.exe show-configuration command. This is unlikely to affect you, but if you are using this to drive automation, please test the new release before upgrading.

Octopus 2019.5


  • Updated build information and work item tracking to fix bugs and improve release note generation
  • Expanded script module support for C# (and F# and Bash and Python)

Read our blog post to learn more.

Breaking Changes

  • Remove the uniqueness restriction on user email addresses to support some customers who have Active Directory configurations where users share email addresses.

  • Health check properties of machine policies have changed to accommodate Linux Tentacle. TentacleEndpointHealthCheckPolicy has been renamed to PowerShellHealthCheckPolicy and SshEndpointHealthCheckPolicy has been renamed to BashHealthCheckPolicy. Any custom tools that create machine policies should use the new property names.

  • The OnlyConnectivity option that was configured on SSH health check policies is now a policy-wide setting. This setting is commonly used for raw scripting on SSH targets. If you are using this setting a new machine policy will be created during the Octopus Server upgrade. Please refer to this GitHub issue for details, you may need to take action.

  • Permissions are now more strictly enforced for creating and modifying teams and users, to avoid users being able to escalate their own permissions. Please see 5537 for more information.


Changes in Octopus 2019.3.3

  • 5531 - Fixed a bug preventing deployment target triggers from working when any project has more than one deployment target trigger defined

Changes in Octopus 2019.3.4

  • 5553 - Improve Performance of Dashboard by indexing temp table
  • 5565 - Azure Resource Group step fixed to handle the templates correctly when bool and integer types are used
  • 5571 - Fixed bug that caused automatic release creation failures to return 400 and 500 on package push
  • 5576 - Fixed high CPU usage on deployment task page
  • 5580 - Resolved issue where certificates with private keys were being shown as not having a private key

Changes in Octopus 2019.3.5

  • 5615 - More defensive error handling when docker acquisition fails

Changes in Octopus 2019.3.6

  • 5453 - Introduced table caching of user details in server, to address performance issues
  • 5627 - Fix for TypeError on certificate search, when certificate data was in an unexpected state
  • 5633 - Further fixes for boolean handling in the Azure Resource Group template step UI
  • 5670 - Fixed issue where historical feed data in database caused primary key violation when creating a new space
  • 5690 - Fix for Tenant variablesmissing endpoint is slow to load with a project/tenant filter when there are many tenants variables
  • 5700 - Fix for Upgrading from 2018.10 to 2019.3+ fails when package configuration contains forward slashes
  • 5702 - Fix for incorrectly migrated user roles that could not be saved due to validation error

Changes in Octopus 2019.3.7

  • 5737 - Fixed issue where proxy password was in certain circumstances rendered as clear text in deployment log CVE-2019-14268

Changes in Octopus 2019.3.8

  • 5747 - Tentacle TentacleProxyPassword logged in clear text when OctopusPrintVariables is set
  • 5759 - TentacleProxyPassword logged in clear text if $env:HTTP_PROXY is printed and password contains special characters

Changes in Octopus 2019.4.1

  • 4236 - Auto Release Creation and Scheduled Triggers now evaluate variables in package names
  • 5412 - Auto Release Creation and Scheduled Triggers can now create releases for projects using Step Templates that reference packages other than the one uploaded
  • 5421 - Improved the speed of the Machine status triggered AutoDeploy
  • 5424 - UI trimming roles on data-entry to avoid white-space issues during machine scoping
  • 5445 - Package push with overwrite now updates metadata
  • 5447 - Swagger file should use string for enums
  • 5449 - Integrate Octopus with Jira to get deployment feedback on your Jira work items
  • 5450 - Projects can now specify a release notes template, complete with variable binding, that gets applied during release creation
  • 5465 - Fixed bug in release creation when steps are scoped to channels

Changes in Octopus 2019.4.2

  • 5159 - Add Octo.exe argument --noDeployAfter to set QueueTimeExpiry
  • 5419 - An event is now logged to the audit log when a task is cancelled due to the server shutting down unexpectedly
  • 5426 - Certificate with private-key being displayed as not having private-key
  • 5427 - UI adding default role chips to the variable editor when no target roles exist yet
  • 5429 - Adding project group filtering for events/subscriptions
  • 5430 - Fixed an issue where an excessive amount of requests were being made for tenant tag sets when on the deployment target settings page
  • 5435 - UI show the step type while editing a step
  • 5436 - Tenant tag selection now shows an appropriate message when all tag sets are empty
  • 5440 - Prevented duplicate validation messages
  • 5452 - Improve Performance of Dashboard by indexing temp table
  • 5455 - Improved the performance the Projects API when many projects use features that are based on step names
  • 5461 - UI adding form expander animations

Changes in Octopus 2019.4.3

  • 5223 - Fixed an issue where redeploying a SF application of the same app/type/version would fail regardless of override behavior
  • 5386 - UI adding categories to make step template selection more intuitive
  • 5402 - Related to 5468, Azure Resource Group template parser updated to handle non-string types
  • 5415 - Added warning when user is creating/editing an Email Step or a Subscription and SMTP hasn't been configured yet
  • 5431 - Prevented disabled steps from being used for release versioning and automatic release creation
  • 5437 - Updated health check messages to better reflect plural and singular
  • 5444 - Octopus Server can no longer be started against a database with a newer schema
  • 5468 - Azure Resource Group step fixed to handle the templates correctly when bool and integer types are used
  • 5472 - Corrected read-only summary label for container volume mount in k8s deploy containers step
  • 5473 - Ensure only distinct package versions are included when running package metadata retention
  • 5475 - Button styling has been updated to improve accessibility
  • 5478 - Resolved spurious validation failure related to secret volume on deploy k8s containers step
  • 5480 - Add certificate variable validation for HTTPS binding on the Deploy to IIS step
  • 5481 - Bug: Unable to pull docker image on some ssh targets
  • 5485 - Kubernetes step resource validation is over-eager and not allowing variables

Changes in Octopus 2019.4.4

  • 5483 - Changed all popover components to use the new MUI component which is reported to fix the positioning delay
  • 5487 - Return a more helpful error message on the release page if a package / version combination cannot be found in the built-in repository
  • 5490 - Make package published date format in UI consistent and include tooltip with timezone info
  • 5491 - Fixed exception on Project settings page if auto release creation is enabled and a package step is configured to use a versioning template instead of package step
  • 5493 - BugFix: DockerHub feeds fail to authenticate during acquisition

Changes in Octopus 2019.4.5

  • 4567 - Automatic Release Creation now creates releases after a step rename
  • 5394 - K8S deploy step supports external secrets to be used for ingress TLS
  • 5458 - Improved the speed of the automatic release creation after a package upload
  • 5488 - Release note accumulation honors the Discrete Channel release setting on the project
  • 5494 - Raw commit details as an Octopus variable for release notes
  • 5495 - Work item release notes from GitHub / Jira
  • 5498 - Improved error message when attempting to acquire helm charts but helm is missing
  • 5501 - Fixed an issue preventing the cloning of a step into the current project
  • 5506 - Fixed issue with creating releases when multiple packages exist on the versioning step

Changes in Octopus 2019.4.7

  • 5482 - Fixed a bug preventing deployment target triggers from working when any project has more than one deployment target trigger defined
  • 5511 - Releases and deployments now have access to a distinct list of work items, as well as the original hierarchical data structures
  • 5515 - Fix up some UserRoles that were not set up correctly in 2019.1 and could not be saved
  • 5518 - Added support for Azure accounts in Terraform steps
  • 5521 - Work items with an alphanumeric project identifier in issue ID can now be parsed
  • 5528 - Fixed an access control bug where project scoping was not being applied for VariableViewUnscoped and VariableEditUnscoped permissions (CVE-2019-11632)
  • 5532 - Fixed single quotes arguments passed to Terraform

Changes in Octopus 2019.5.0

  • 3590 - Choosing a certificate no longer shows the binding expression toggle in the UI
  • 5462 - Added variables for trigger which caused a deployment
  • 5486 - UI improving delta highlighting on the audit screen
  • 5499 - Script modules are now supported for Bash, C#, F# and Python
  • 5502 - Fixed an issue where the file picker window would not trigger from the replace certificate dialog
  • 5507 - UI improving onboarding for new users and team membership and including a list of teams on the users page
  • 5508 - Can now step into script modules while debugging PowerShell script steps
  • 5520 - UI Dashboard screen search bar will no longer render if there are no Environments in the instance
  • 5522 - Release notes evaluation now also happens for automatic release creation and scheduled release triggers
  • 5523 - Fixed an issue where Deploy CloudFormation template step would fail when using the change sets feature and no changes need to be applied
  • 5524 - Fixed bug where retrieving release notes from GitHub would throw an exception if the VcsRoot ended with .git
  • 5526 - Improved how the Portal retries connecting when the Octopus Server is not contactable
  • 5533 - Health check may fail on windows machines with failure to load TimeZoneInfo type
  • 5534 - The Test button on the Create Feed screen no longer crashes when invalid data entered
  • 5536 - Fixed error when attempting to delete an Octopus Server node
  • 5537 - Modifying teams and roles enforces all permissions and scoping in elevation checks
  • 5540 - Added confirmation dialog before deleting an API Key
  • 5542 - Fixed an issue preventing the selection of the Specific Version radio button when using variables for the package feed
  • 5544 - Breaking change Some machine policy properties have been renamed to better accommodate Linux Tentacle
  • 5546 - Fixed TypeError on Kubernetes step when adding a volume
  • 5549 - Octopus no longer enforces email uniqueness across users, in order to support Active Directory scenarios where users can share an email address

Changes in Octopus 2019.5.1

  • 5550 - Fixed an issue where multi-select and auto completion fields would render popovers partially offscreen when close to the edge
  • 5551 - Deployment retention no longer requires exclusive access to the tentacle (this bug was introduced in 2019.4.5)
  • 5555 - Fixed "Sequence contains no elements" error when viewing releases that don't match the current project release versioning settings
  • 5556 - Fix terraform steps unable to asume AWS service roles
  • 5557 - Only load script module usage on demand
  • 5559 - Include monthly active user count in usage statistics

Changes in Octopus 2019.5.2

  • 5539 - Fixed missing navigation menus when creating a new Deployment Target or Worker

Changes in Octopus 2019.5.3

  • 5567 - Rolled back the logging changes in 2019.4.3 that are likely causing deployments, tasks and server shutdown to hang