The finalisePath option has been deprecated in favour of the new finaliseDirectory option, which dictates the root directory of the finalise repository. This can be configured in an environment variable called "FinaliseDirectory".

Any git repositories under the root FinaliseDirectory will be purged, in theory as a one-off operation.

Zip Backups are no longer performed, using the finaliseDirectory option is the preferred alternative.

New function: TagVersion - adds a tag to the finalise repository with the specified version number

NGit library removed in preference of LibGit2Sharp which is more performant on large repositories.
Namespace tidyup, fixing git Signature
finalisePath option only marked as obsolete, for backwards compatibility reasons.

Can be used in conjunction with finaliseDirectory, with the finaliseDirectory overriding any subdirectory attempt at finalising done as part of the finalisePath operation.
Exit after -i|stdin operation completed: other operations are not allowed in this mode
Only finalise when files are known to have changed
Manually staging known files rather on relying on the slower RetrieveStatus function, which can add considerable time to deployments.

The down side is that doing it this way may result in null commits as we're staging files irrespective of if there were changes to those files.
Reducing severity of finalisePath usage to an informational message, so as not to break deploys that treat Error output as warnings and breaking deploys when the variable OctopusTreatWarningsAsErrors is true
finalisePath is now automatic and runs during every ensconce operation
Merge remote-tracking branch '15below/development' into development
TagVersion command will finalise all uncommitted changes in the finaliseDirectory path
Merge pull request #23 from richard-green/development

The finalisePath option has been deprecated in favour of finaliseDirectory (+others)