1.0.0-beta.1
Not 1.0.0 after all, but let’s call it 1.0.0-beta.1 rather than 0.13.0.
This commit is contained in:
parent
fe838bbc35
commit
0316c0faea
|
@ -1,5 +1,10 @@
|
||||||
# 1.0.0 (unreleased)
|
# 1.0.0 (unreleased)
|
||||||
|
|
||||||
|
Planned once the dust of 1.0.0-beta.1 settles, since 1.0.0-beta.1 ended up
|
||||||
|
being bigger than I’d earlier intended.
|
||||||
|
|
||||||
|
# 1.0.0-beta.1 (2022-01-25)
|
||||||
|
|
||||||
- Removed `anymap::any::Any` in favour of just plain `core::any::Any`, since its
|
- Removed `anymap::any::Any` in favour of just plain `core::any::Any`, since its
|
||||||
`Send`/`Sync` story is now long stable.
|
`Send`/`Sync` story is now long stable.
|
||||||
|
|
||||||
|
@ -38,9 +43,6 @@
|
||||||
- Worked around the spurious `where_clauses_object_safety` future-compatibility lint that has been raised since mid-2018.
|
- Worked around the spurious `where_clauses_object_safety` future-compatibility lint that has been raised since mid-2018.
|
||||||
If you put `#![allow(where_clauses_object_safety)]` on your binary crates for this reason, you can remove it.
|
If you put `#![allow(where_clauses_object_safety)]` on your binary crates for this reason, you can remove it.
|
||||||
|
|
||||||
I don’t plan for there to be any real changes from 0.12.1;
|
|
||||||
it should be just a bit of housecleaning and a version bump.
|
|
||||||
|
|
||||||
# 0.12.1 (2017-01-20)
|
# 0.12.1 (2017-01-20)
|
||||||
|
|
||||||
- Remove superfluous Clone bound on Entry methods (#26)
|
- Remove superfluous Clone bound on Entry methods (#26)
|
||||||
|
|
|
@ -1,6 +1,6 @@
|
||||||
[package]
|
[package]
|
||||||
name = "anymap"
|
name = "anymap"
|
||||||
version = "0.12.1"
|
version = "1.0.0-beta.1"
|
||||||
authors = ["Chris Morgan <rust@chrismorgan.info>"]
|
authors = ["Chris Morgan <rust@chrismorgan.info>"]
|
||||||
edition = "2018"
|
edition = "2018"
|
||||||
rust-version = "1.36"
|
rust-version = "1.36"
|
||||||
|
|
Loading…
Reference in a new issue