Compare releases

Compare releases and check for compatibility between your existing Octopus Server and new releases.

→

Release notes

These are the features and fixes you'll get by upgrading from 2019.8.6 to 2019.9.15.

6229 - Fixed bug where Octopus was ignoring proxy config when configuring Azure targets

6053 - Added retries running the Tentacle MSI to the Tentacle upgrader if msiexec failed to run successfully
6078 - Enhanced logging of timezone conversion failures during scheduled health checks
6082 - Fixed a bug where deleting a parent step might delete the wrong step

6028 - Fixed a bug where connections may have been opened unnecessarily when querying the /api/projects/all endpoint

6009 - Fix issue where project switcher would open a new tab when clicking away
6018 - Fixed a bug with GitHub feed tags not getting more than the first 100 tags
6022 - UI rendering performance improvements to the projects list screen for customers operating at scale

5997 - CSRF cookie sometimes missing secure attribute - CVE: CVE-2019-19375
6001 - Fixed an error calling octo create-release when package version supplied for a deploy a release step does not exist
6004 - Invalid request submitted to Team API can cause denial of service - CVE: CVE-2019-19376

5983 - Fixed an information disclosure vulnerability during error handling of maliciously crafted packages on Octopus Cloud - CVE: CVE-2019-19084
5984 - Changed machine license check to sql column for better performance

5957 - Fixed an information disclosure vulnerability during error handling of maliciously crafted packages - CVE: CVE-2019-19084
5960 - Fixed a stored cross-site-scripting (XSS) vulnerability - CVE: CVE-2019-19085

5921 - UI performance boost for Octopus instances with lots of projects doing lots of deployments
5922 - Fix for duplicate key exception when cleaning up build information/package metadata
5929 - Fix for StackOverflowException causing Octopus Server to crash
5930 - Fix for recursive variable loop when there isn't one

5905 - Fixed an issue where a project was not able to be cloned when the logo file was missing, the cloned project will now use the default logo

5901 - Fix for upgrade error unable to find id in Script0206 - affecting case sensitive SQL server instllations

5894 - Create User action can now add external logins, due to a bug was only available in editing existing users
5896 - Fixes rare crash in editing a package deployment step if a large amount of feeds are present

5755 - Added informational message on how to work around PowerShell terminating processes on Win2019 and .NET 4.7.2 when an error is output
5824 - Project logos are now copied when a project is cloned
5880 - helm init in the Helm Upgrade step no longer refreshes the local repository cache
5883 - Fix for Kubernetes node affinity not being set during deployment
5889 - Project overview screen is no longer dependant on LibraryVariableSetView permission for Tenanted projects

5797 - Fixed how manual interventions are handled when they occur during a deploy release step
5835 - Account parameters used in Step Templates are now expanded, making them easier to use
5851 - Shows cleaner exception message when executable is not found in steps with script logic
5866 - Fixed an issue that caused certain steps to now show in the channel version rule selector
5868 - Fixed comparison of package ids between build information and steps to be case insensitive
5872 - Improved validation and error messsages for Automatic Release Creation package steps
5874 - Improve reliability of temp file handling on Linux targets and avoid silent failure of "Deploy to NGINX" steps
5878 - Removed duplicate email validation when modifying or registering users