From: Chris Morgan <me@chrismorgan.info>
Date: Tue, 22 Feb 2022 02:54:20 +0000 (+1100)
Subject: 1.0.0-beta.2
X-Git-Tag: 1.0.0-beta.2
X-Git-Url: https://git.chrismorgan.info/anymap/commitdiff_plain/2e9a570491664eea18ad61d98aa1c557d5e23e67

1.0.0-beta.2
---

diff --git a/Cargo.toml b/Cargo.toml
index aca1a64..43e7dec 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -1,6 +1,6 @@
 [package]
 name = "anymap"
-version = "1.0.0-beta.1"
+version = "1.0.0-beta.2"
 authors = ["Chris Morgan <rust@chrismorgan.info>"]
 edition = "2018"
 rust-version = "1.36"
diff --git a/README.md b/README.md
index d0af879..e53b1e8 100644
--- a/README.md
+++ b/README.md
@@ -45,14 +45,14 @@ Typical Cargo.toml usage, providing `anymap::AnyMap` *et al.* backed by `std::co
 
 ```toml
 [dependencies]
-anymap = "1.0.0-beta.1"
+anymap = "1.0.0-beta.2"
 ```
 
 No-std usage, providing `anymap::hashbrown::AnyMap` *et al.* (note the different path, required because Cargo features are additive) backed by `alloc` and the [hashbrown](https://rust-lang.github.io/hashbrown) crate:
 
 ```toml
 [dependencies]
-anymap = { version = "1.0.0-beta.1", default-features = false, features = ["hashbrown"] }
+anymap = { version = "1.0.0-beta.2", default-features = false, features = ["hashbrown"] }
 ```
 
 **On stability:** hashbrown is still pre-1.0.0 and experiencing breaking changes. Because it’s useful for a small fraction of users, I am retaining it, but with *different compatibility guarantees to the typical SemVer ones*. Where possible, I will just widen the range for new releases of hashbrown, but if an incompatible change occurs, I may drop support for older versions of hashbrown with a bump to the *minor* part of the anymap version number (e.g. 1.1.0, 1.2.0). Iff you’re using this feature, this is cause to *consider* using a tilde requirement like `"~1.0"` (or spell it out as `>=1, <1.1`).