Cut 0.1.0 (woo!) (#237)

Let's do this!

Cargo.toml

@@ -18,4 +18,4 @@ keywords = ["deltalake", "delta", "datalake"]
 license = "Apache-2.0"
 repository = "https://github.com/delta-incubator/delta-kernel-rs"
 readme = "README.md"
-version = "0.0.1"
+version = "0.1.0"

README.md

@@ -35,9 +35,14 @@ As it is a library, in general you will want to depend on `delta-kernel-rs` by a
 dependency to your `Cargo.toml`. For example:
 
 ```toml
-delta_kernel = "0.0.1"
+delta_kernel = "0.1"
 ```
 
+### Versions and Api Stability
+We intend to follow [Semantic Versioning](https://semver.org/). However, in the `0.x` line, the APIs
+are still unstable. We therefore may break APIs within minor releases (that is, `0.1` -> `0.2`), but
+we will not break APIs in patch releases (`0.1.0` -> `0.1.1`).
+
 ## Documentation
 
 - [API Docs](https://docs.rs/delta_kernel/latest/delta_kernel/)

ffi/Cargo.toml

@@ -18,7 +18,7 @@ url = "2"
 delta_kernel = { path = "../kernel", default-features = false, features = [
   "developer-visibility",
 ] }
-delta_kernel_ffi_macros = { path = "../ffi-proc-macros", version = "0.0.1" }
+delta_kernel_ffi_macros = { path = "../ffi-proc-macros", version = "0.1.0" }
 
 # used if we use the default engine to be able to move arrow data into the c-ffi format
 arrow-schema = { version = "^51.0", default-features = false, features = [
@@ -46,4 +46,4 @@ default-engine = [
   "arrow-schema",
 ]
 sync-engine = ["delta_kernel/sync-engine"]
-developer-visibility = []
+developer-visibility = []

kernel/Cargo.toml

@@ -31,7 +31,7 @@ uuid = "1.3.0"
 z85 = "3.0.5"
 
 # bring in our derive macros
-delta_kernel_derive = { path = "../derive-macros", version = "0.0.1" }
+delta_kernel_derive = { path = "../derive-macros", version = "0.1.0" }
 
 # used for developer-visibility
 visibility = "0.1.0"