Our latest feature release, 2.1.0, is now publicly available for use!
What's New!
At over a year in progress, there were a lot of changes introduced:
v 2.1.0 (release):
- Test Framework Redesign - better test coverage means more reliable software
- Updated documentation to facilitate security review and additional development efforts.
- Added new functionality surrounding file validation, either on-demand or at runtime.
- add Build-Time File Validation: True to your config file to activate.
- demand-validate specific block files with --validate (requires decryption)
- Fixed an unreported bug introduced in v2.0.0 that caused an error message at runtime.
- If no -c config file path is provided, tapestry will look for tapestry.cfg in the current working directory.
- If that file is also not found, Tapestry will generate a config file with sane defaults and save it in that
location.
- Deprecates all former network functionality; this is being replaced with new SFTP functionality.
- Deemed acceptable as FTP/S is a rare arrangement by comparison to SFTP.
- This requires new fields be added to your configuration file.
- Stashing on network shared drives still possible.
- Adds SFTP functionality
- Restores the logger functionality. Future logging improvements likely, but the original functionality of logging
skipped files should be restored.
- Issue 19: Tapestry will crash upon encountering a file it cannot operate against, such as a broken symlink.
EricaPomme supplied a new function that will address this.
Other Changes
You might have noted that for the first time, a secondary contributor was included in the changenotes! @EricaPomme contributed a very useful function which closed out a major technical issue.
The 2.1.0 will be the last feature release for the foreseeable future. From now on, development around tapestry will focus on bug fixes only, and minor improvements where possible. Of course, we'll continue to review and accept new PRs, including those which add functionality.