Try using 0.1.1 instead of 0.2.0

ghagl · Mar 8, 2022 · f6afa30 · f6afa30
1 parent a637aad
commit f6afa30
Show file tree

Hide file tree

Showing 3 changed files with 5 additions and 3 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -6,9 +6,11 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
-## [0.2.0] - 2022-03-08
+## [0.1.1] - 2022-03-08
 - rename project to `solo1-cli`
 - rename CLI to `solo1`
+- keep `solo` name for library
+- have old `solo-python` on PyPI depend on `solo1`
 
 ## [0.1.0] - 2022-03-08
 - fix build @innir

diff --git a/README.md b/README.md
@@ -4,7 +4,7 @@
 
 This CLI is for Solo 1, for the Solo 2 device use [solo2-cli](https://github.com/solokeys/solo2-cli).
 
-v0.1.0 was the last to be named `solo-python`, since v0.2.0 this project is named `solo1-cli` for clarity, and available from PyPI as `solo1`.
+v0.1.0 was the last to be named `solo-python`, since v0.1.1 this project is named `solo1-cli` for clarity, and available from PyPI as `solo1`.
 
 The CLI is now called `solo1`, for the time being `solo` will also be removed, but this is deprecated.
 

diff --git a/solo/VERSION b/solo/VERSION
@@ -1 +1 @@
-0.1.0
+0.1.1