# Ansible 2.0.1.0 has been released

**URL:** <https://forum.ansible.com/t/ansible-2-0-1-0-has-been-released/20674>\
**Category:** Ansible Project\
**Created:** [February 25, 2016, 3:42am UTC](https://forum.ansible.com/t/ansible-2-0-1-0-has-been-released/20674 "2016-02-25T03:42:51Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![James\_Cammarata](https://avatars.discourse-cdn.com/v4/letter/j/7c8e57/32.png) [@James\_Cammarata](https://forum.ansible.com/u/James_Cammarata)\
**Post date:** [February 25, 2016, 3:42am UTC](https://forum.ansible.com/t/ansible-2-0-1-0-has-been-released/20674/1 "2016-02-25T03:42:51Z")

</div>

Hi all, 2.0.1.0 has been released, and is now available.

This release addresses several bugs present in 2.0, such as:

- Improvements to the way no\_log filters some output, which may have lead to  
some disclosure of secret variables when using the --diff option.
- Lots of improvements to the synchronize module to bring it back in line  
with 1.9’s handling of become/sudo options, among other things.
- Re-implemented retry file support, which was overlooked in the 2.0 release.  
Additionally, retry files are now stored in the same directory as the  
playbook, rather than the home directory (assuming the retry\_files\_save\_path  
configuration option is not set in your ansible.cfg file).
- Fixes bugs in the implementation of any\_errors\_fatal. Additionally, we’ve  
added the ability to set this option on blocks.
- Many unicode fixes.
- Temporary files created by ansible-vault are now “shredded” as an extra  
layer of security.

And many other minor fixes.

As always, this update is available via PyPi and [releases.ansible.com](http://releases.ansible.com) now, and packages for distros will be available as soon as possible.

Thanks, and enjoy!