Merge pull request #25 from DragonBox/release_1.0.0beta5

Preparing release for 1.0.0beta5

CHANGELOG.md

@@ -1,12 +1,29 @@
 # Change Log
 
+## [v1.0.0beta5](https://github.com/DragonBox/uplift/tree/v1.0.0beta5) (2017-11-30)
+[Full Changelog](https://github.com/DragonBox/uplift/compare/v1.0.0beta4...v1.0.0beta5)
+
+**Fixed bugs:**
+
+- Some .unitypackage are not extracted correctly [\#23](https://github.com/DragonBox/uplift/issues/23)
+- Readme version not correctly updated when releasing [\#22](https://github.com/DragonBox/uplift/issues/22)
+- Log not aggregated on Unity 2017+ from the .unitypackage [\#20](https://github.com/DragonBox/uplift/issues/20)
+
+**Merged pull requests:**
+
+- Compiler: use defines to make sure that .unitypackage is built correctly [\#21](https://github.com/DragonBox/uplift/pull/21) ([niezbop](https://github.com/niezbop))
+
 ## [v1.0.0beta4](https://github.com/DragonBox/uplift/tree/v1.0.0beta4) (2017-11-28)
 [Full Changelog](https://github.com/DragonBox/uplift/compare/v1.0.0beta3...v1.0.0beta4)
 
 **Implemented enhancements:**
 
 - Add GitHub repository [\#18](https://github.com/DragonBox/uplift/pull/18) ([niezbop](https://github.com/niezbop))
 
+**Merged pull requests:**
+
+- Preparing release for 1.0.0beta4 [\#19](https://github.com/DragonBox/uplift/pull/19) ([niezbop](https://github.com/niezbop))
+
 ## [v1.0.0beta3](https://github.com/DragonBox/uplift/tree/v1.0.0beta3) (2017-11-16)
 [Full Changelog](https://github.com/DragonBox/uplift/compare/v1.0.0beta2...v1.0.0beta3)
 

README.md

@@ -1,7 +1,7 @@
 # UPLIFT
 
 [![License](https://img.shields.io/badge/license-MIT-green.svg?style=flat)](https://github.com/DragonBox/uplift/blob/master/LICENSE)
-![Version](https://img.shields.io/badge/version-1.0.0beta4-blue.svg)
+![Version](https://img.shields.io/badge/version-1.0.0beta5-blue.svg)
 
 Uplift is a __package manager__ for the [Unity](https://unity3d.com/) game engine, built in __C#__, that provides a standard format for distributing Unity3d assets, and is designed to easily manage the installation of assets into your projects.
 
@@ -83,4 +83,4 @@ Nonetheless, we believe that Uplift has strengths that could motivate one to use
 
 - Finally, __Uplift is not in complete opposition with PackMan__. Using Uplift requires you to do a big paradigm shift towards the use of a package manager. It encourages modularity, versioning and other concepts that are separate from the actual implementation of the package manager. If you start using Uplift right now and modularize some of you projects, your work will not be lost if you decide to shift to Unity's package manager when it is released. Most of it will actually be done, as a big part of using package managers requires you to adopt a specific mindset and switching from one another should not be too much of a hassle, and should remain an implementation detail.
 
-In conclusion to this matter, we believe that Uplift and Unity's Package Manager do not completly overlap. Whether it is in scope or in implementation, we are confident that both of these products can find use without major conflict with the other.
+In conclusion to this matter, we believe that Uplift and Unity's Package Manager do not completly overlap. Whether it is in scope or in implementation, we are confident that both of these products can find use without major conflict with the other.