2.1.24 - May 29th, 2018

Fixes

• Fixed a problem on TFS 2015 related to task names that could cause releases to fail.

2.1.23 - May 21st, 2018

Compatibility with VSTS Build addon

2.1.22 - May 8th, 2018

Fixes

• Fixed a bug that could cause releases to fail with the error "...A parameter cannot be found that matches parameter name 'MaximumVersion'..." when run on private agents that don't have PowerShell 5 available

• Fixed a bug introduced in 2.1.20 that could cause releases to fail with the error "...The term 'Get-PSRepository' is not recognized..." when run on private agents that don't have PowerShellGet available

2.1.20 - May 8th, 2018

Fixes

• The latest version of DLM Automation from the PowerShell gallery will now be used in preference to an installed version unless a specific version is specified in the task definition.

This fixes a problem introduced in the previous version where having an incompatible version of DLM Automation installed on a private build agent would cause builds to fail with the error "A parameter cannot be found that matches parameter name 'AbortOnWarningLevel'"

2.1.19 - May 2nd, 2018

Features

• The VSTS DLM Automation Release plugin now gets the latest version of DLM Automation from the PowerShell Gallery. For more details see the DLM Automation 2.1.0 release notes.
  
  If you wish to use a specific version of DLM Automation there are two options:
  - A new option in the task definition where you can specify a specific version to be downloaded from the PowerShell Gallery.
  - Install DLM Automation on your release agent. An installed version of DLM Automation will be used instead of downloading the latest version from PowerShell Gallery.

2.1.18 - April 12th, 2018

Features

• Revert the release artifacts change from 2.1.17 because it was causing issues.

2.1.17 - April 11th, 2018

Features

• Release artifacts are now included in the VSTS log files as part of the "Create release" operation.
  
• Updated to v2.0.35 of DLM Automation (see main Release notes for details)

2.1.16 - March 27th, 2018

Features

• Updated to v2.0.34 of DLM Automation (see main Release notes for details)

2.1.15 - February 14th, 2018

Features

• Updated to v2.0.29 of DLM Automation (see main Release notes for details)

2.1.14 - January 31st, 2018

Features

• Updated to v2.0.28 of DLM Automation (see main Release notes for details)

2.1.13 - January 12th, 2018

Features

• Updated to v2.0.27 of DLM Automation (see main Release notes for details)

2.1.12 - January 4th, 2018

Features

• Updated to v2.0.26 of DLM Automation (see main Release notes for details)

2.1.11 - December 7th, 2017

Features

• Updated to v2.0.25 of DLM Automation (see main Release notes for details)

2.1.10 - November 22nd, 2017

Features

• Allow Abort on warning level to be set
• Updated to v2.0.24 of DLM Automation (see main Release notes for details)

2.1.9 - November 3rd, 2017

Features

• DeployFromPackage skips PreUpdateSchemaCheck

2.1.8 - October 25th, 2017

Features

• Updated to v2.0.23 of DLM Automation (see main Release notes for details)

2.1.7 - October 12th, 2017

Fixes

• Allowing the task to run without AGENT_JOBNAME being set.

2.1.6 - July 3rd, 2017

Features

• Updated to v2.0.14 of DLM Automation (see main Release notes for details)

2.1.5 - June 22nd, 2017

Features

• Updated to v2.0.13 of DLM Automation (see main Release notes for details)

2.1.4 - January 26th, 2017

Fixes

• Updated internal versioning so that build agents would be properly updated

2.1.3 - January 23rd, 2017

Features

• Updated to v2.0.7 of DLM Automation (see main Release notes for details)

2.1.2 - December 19th, 2016

Features

• Updated to v2.0.5 of DLM Automation (see main Release notes for details)
• Transaction isolation level can now be set for releases (e.g. to enable use of linked servers).

2.1.1 - November 24th, 2016

Features

• Query Batch Timeout is now an option in the "Deploy from package" task.

2.1.0 - November 16th, 2016

Features

• Updated to v2.0.3 of DLM Automation (see main Release notes for details)

Fixes

• Append release name to path so that release resources no longer overwrite each other

  • There is an option to turn off this behaviour if you would rather only the current copy of release resources is kept