Compare releases

• Fixed a bug that prevented adding new package steps (details)

• Upgrade to NuGet 2.0 (details)
• Fix package step validation bug (details)
• Fix support for HTML in markdown content (details)
• "Try again..." deployment button will use "force" mode by default (details)
• Allow underscores and @'s in usernames (details)
• Improve dashboard performance (details)

• Improving performance of dashboard and projects pages (details)
• Fixed web link generation for projects REST API (details)
• Remove an Octopus web.config change from last release that broke compatibility with some versions of IIS (details)

• Fixed a bug that caused errors when listing deployments via the API (details)
• Improved error experience when using HTTP API's (full details are now included)
• Added a new special variable to treat warnings as errors (details)
• Automatically trimming whitespace when editing projects/environments (details)
• Improved WCF logging when Tentacle encounters security errors

• Fixed a bug that prevented the dashboard from showing some deployments (details)
• Fixed a JavaScript bug that prevented the create release page from working properly under IE 8 (details)
• A note will now appear to suggest users need to create a new release after editing variables/steps (details)

• Fix a bug that prevented the Create Release page from working when a project uses multiple NuGet feeds (details)
• The auto-registration of Tentacles now requires a -f parameter to be passed to force overwriting of existing machines (details)

• Support for DeployFailed.ps1 scripts, which will be executed if other scripts/conventions fail (details)
• Saving variables no longer triggers request validation (details)
• Create release page should load quicker when there are many packages (details)
• Create release version number generation improvements (details)
• Better NuGet results when searching for packages (details)
• Environment images are fixed when Octopus runs under a virtual directory (details)
• Better error messages when Octopus is unable to communicate with Tentacle (details)

• Auditing and activity logging/history (details)
• A new "select all" option when skipping many steps (details)
• Better time zone support on the environments page (details) Read our blog post demonstrating the new history feature.

This release adds a register-with command to unattended Tentacle installation. See our blog post on automated Tentacle installation for details.

• Fixed case sensitivity bug when validating uploaded packages on the Tentacle (details)
• A small change to how certificates are loaded into memory, to handle this issue (details)
• Fixed a bug that caused new Tentacle installs to crash when package folder doesn't exist (details)
• Implemented support for unattended tentacle configuration (details) I'll do a blog post shortly to describe how that last feature works.

• Fix Tentacle command line parsing (details)
• Fix bug that prevented Octo.exe from being able to find releases (details)
• Fix environment rendering under IE8 and IE9 with compatibility view enabled (details)
• Extend timeouts when downloading NuGet packages

• Better support for dealing with multiple copies of a package being uploaded, and ensuring corrupt packages aren't installed, by checking the hashes on the Tentacle (details)
• SemVer tags like 1.0.0-patch1 are now supported when creating releases via the API (details)
• Fix for a bug whereby deploying a release via the command line would complain that the release cannot be found (details)
• Admins can't remove themselves from the admin group anymore (details)

• Environments in the drop downs on the Edit Variables screen will be sorted (link)
• Fixed path used by Octopus to store downloaded packages (link)
• Prevent deployment when Octopus or Tentacle is close to running out of disk space (link)
• Edit variables screen now supports saving large numbers of variables (link)
• Tentacle no longer crashes when loading .NET Framework 2.0 mixed mode assemblies (link)
• PowerShell files can now be run directly by Tentacle, for testing (link)
• NuGet feeds can be deleted (link)
• Show a hint to make people aware of possible permission problems when no results are found in a NuGet feed (link)

This fixes a null reference bug when downloading or uploading packages.

This release adds a couple of registry settings that allow the RavenDB host name and port number to be overridden.

• When a step is skipped, packages won't be downloaded/uploaded for it anymore (link)
• The Cancel button is now shown for deployments (link)
• A slight delay has been added to Octopus startup to make sure the HTTP server is ready and listening, which will hopefully prevent some crashes on start up

This release adds a new migration tool, which can be used to import data from the SQL-based 0.9.* releases of Octopus.

• Fixed a bug in license checking
• Setup tool now makes it more obvious that IIS needs to be updated (link)
• Installer now uses C:\Program Files (link)

• Bug fix: Error when checking for updates (link)
• Bug fix: Admin account can't be deleted (link)
• Setup tools now check for pre-requisites during installation (link)
• The Octopus MSI's and executables are now signed

• Wrapping/layout of the dashboard and deployment list when you have many projects/environments (details)
• Unlisted packages will no longer appear in the package selection dialog, and they won't be seen by Octo.exe (details)
• Octopus now displays a more useful error message when the Tentacle rejects the Octopus due to an invalid thumbprint

• Projects can now be deleted by Octopus administrators
• Inability to modify .config files has reverted back to being a warning rather than an error, because some customers have .config files that are not XML documents.

• Fix a problem that prevented appSettings being updated with empty strings

• The last release number now appears when creating a new release
• Increased refresh rate for running tasks
• Fixed bug in checking for Octopus updates
• Fixed bug when displaying releases for a project when environments have been deleted

• Failure to save the Tentacle folder path was prevented deployments from working
• An out-of-date Dotless had problems with multiple IIS bindings
• If Tentacle fails to change the PowerShell execution policy it will still continue to run the script