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 3.16.6 to 3.16.7

Octopus 3.16

Changes in 3.16

See our release blog post for more details.

New Features

Octopus 3.16 removes the requirement to install Mono when deploying to Linux and MacOS targets. It does this by using a self-contained .NET Core build of Calamari.

Improvements

  • Support for Okta as an authentication provider
  • ScriptCS has been upgraded to version 0.17.1
  • Resolved issue introduced by Let's Encrypt API change

Breaking Changes

The latest version of ScriptCS has introduced some breaking changes so it's important to review their release notes before upgrading. This only affects projects with script steps written using C#, which are powered by ScriptCS under the hood.

Upgrading

This release contains a post-install data fix that may take a few minutes, depending on the size of your Events table, so please ensure you allow time for this to complete. In our testing with 180,000 records in the EventsTable took ~3 seconds to upgrade.

If you are running the watchdog service, please ensure this is stopped during the upgrade.

All of the usual steps for upgrading Octopus Deploy apply.

Release notes

These are the features and fixes you'll get by upgrading from 3.16.6 to 3.16.7.

Changes in Octopus Server 3.16.7

  • 3759 - Fixed an issue causing too much verbose output in the task log

Changes in Octopus Server 3.16.6

  • 3734 - Fixed a problem preventing the Octopus Server from starting successfully which affected customers where their SQL Server Collation is case-sensitive (CS) even if the Database Collation is case-insensitive (CI)
  • 3736 - Adhere to PowerShell common preferences when writing verbose and warning output
  • 3749 - Log warning for duplicate variables between step template and project for steps that run on the server