Improvements in 1.7.3

• Quicker symlinks creation in shared folders, it could take second before, thanks @mblaschke
• Tests for Ansible 1.8 which is our minimum supported

Improvements in 1.7.2

If you are using the git strategy, the result is now available under ansistrano_git_result. You can use this to notify your monitoring tools in a hook. Thanks @Lumbendil

The example playbook is working again, inside the example folder as it used to be

Bug fixes in 1.7.1

Bug reported at #128 by @michaelBenin

Ansistrano was crashing when ansistrano_s3_object had a "folder" structure path. We added a basename filter to prevent this issue

Changes in 1.7.0

Add a flag to force overwrite in the git pull strategy. This can be useful to prevent deployments failing after doing local changes in the remote machine's git repository

This is due to a BC change in Ansible 1.9 where they changed the default value from yes to no for this option in the git module. Thanks @fonsecas72

Changes in 1.6.0

Lots of improvements to the rsync current folder strategy (as opposed to the default symlink option)

Thanks a lot @mblaschke

Changes in 1.4.1

Bug Fixes

• Fixed a problem with shared_paths relative symlinks with a many folders structure
• Removed some Ansible2 deprecation warnings in the shared_paths task

Changes in 1.4.0

New features

• New download + unarchive strategy

Internal changes

• Symlinks are now relative instead of absolute

Changes in 1.3.0

Fixes

• Improving compatibility with Ansible 2.x

Changes in 1.2.0

New features

• Added an extra step to collect anonymous stats
• Some clarifications in the README file about the ansistrano_git_branch variable

Changes in 1.1.0

New features

• Allow ansistrano to work with .ssh config files by Andrei Simion
• New S3+unarchive strategy by Dani Codina

Bug fixes

• Some fixes in the S3 strategy by Dani Codina & @ricardclau
• Quote variable ansistrano_rsync_extra_params by @mvbeek-oefenweb

BC Breaks

• Stopped creating the redundant ansistrano_timestamp variable by @cbrunnkvist. Please note this can lead to potential BC breaks in case someone was using it. In that case, please use ansistrano_release_version instead
• In order to introduce omit-able variables in the S3 strategy the Ansible minimum version was bumped to 1.8. Ansible 1.7 should still be fine for the rest of deployment strategies