*: bump 0.4 (#53)

Signed-off-by: Jay Lee <[email protected]>

Author: BusyJay

CHANGELOG.md

@@ -1,3 +1,9 @@
+# 0.4.0 - 2020-04-13
+
+- re-arrange macros to avoid leaking
+- support callback action
+- update rand to 0.7
+
 # 0.3.0 - 2019-07-15
 
 - fail-rs is now 2018-edition compatible!

Cargo.toml

@@ -1,14 +1,14 @@
 [package]
 name = "fail"
-version = "0.3.0"
+version = "0.4.0"
 authors = ["The TiKV Project Developers"]
 license = "Apache-2.0"
 keywords = ["failpoints", "fail"]
-repository = "https://github.com/pingcap/fail-rs"
+repository = "https://github.com/tikv/fail-rs"
 readme = "README.md"
-homepage = "https://github.com/pingcap/fail-rs"
+homepage = "https://github.com/tikv/fail-rs"
 documentation = "https://docs.rs/fail"
-description = "Failpoints for rust."
+description = "Fail points for rust."
 categories = ["development-tools::testing"]
 edition = "2018"
 exclude = ["/.github/*", "/.travis.yml", "/appveyor.yml"]
@@ -22,7 +22,7 @@ rand = "0.7"
 failpoints = []
 
 [badges]
-travis-ci = { repository = "pingcap/fail-rs" }
+travis-ci = { repository = "tikv/fail-rs" }
 appveyor = { repository = "busyjay/fail-rs" }
 
 [package.metadata.docs.rs]

README.md

@@ -1,6 +1,6 @@
 # fail-rs
 
-[![Build Status](https://travis-ci.org/pingcap/fail-rs.svg?branch=master)](https://travis-ci.org/pingcap/fail-rs)
+[![Build Status](https://travis-ci.org/tikv/fail-rs.svg?branch=master)](https://travis-ci.org/tikv/fail-rs)
 [![Crates.io](https://img.shields.io/crates/v/fail.svg?maxAge=2592000)](https://crates.io/crates/fail)
 
 [Documentation](https://docs.rs/fail).
@@ -17,7 +17,7 @@ First, add this to your `Cargo.toml`:
 
 ```toml
 [dependencies]
-fail = "0.3"
+fail = "0.4"
 ```
 
 Now you can import the `fail_point!` macro from the `fail` crate and use it to inject dynamic failures.

src/lib.rs

@@ -18,7 +18,7 @@
 //!
 //! ```toml
 //! [dependencies]
-//! fail = "0.3"
+//! fail = "0.4"
 //! ```
 //!
 //! Now you can import the `fail_point!` macro from the `fail` crate and use it
@@ -191,7 +191,7 @@
 //!
 //! ```sh
 //! $ FAILPOINTS=read-dir=return cargo run --features fail/failpoints
-//!    Compiling failpointtest v0.1.0 (/home/brian/pingcap/failpointtest)
+//!    Compiling failpointtest v0.1.0
 //!     Finished dev [unoptimized + debuginfo] target(s) in 2.38s
 //!      Running `target/debug/failpointtest`
 //! Error: Custom { kind: PermissionDenied, error: StringError("error") }
@@ -205,15 +205,16 @@
 //! That's the basics of fail points: defining them with `fail_point!`,
 //! configuring them with `FAILPOINTS` and `fail::cfg`, and configuring them to
 //! panic and return early. But that's not all they can do. To learn more see
-//! the documentation for [`cfg`](fn.cfg.html) and
+//! the documentation for [`cfg`](fn.cfg.html),
+//! [`cfg_callback`](fn.cfg_callback.html) and
 //! [`fail_point!`](macro.fail_point.html).
 //!
 //!
 //! ## Usage considerations
 //!
 //! For most effective fail point usage, keep in mind the following:
 //!
-//!  - Failpoints are disabled by default and can be enabled via the `failpoints`
+//!  - Fail points are disabled by default and can be enabled via the `failpoints`
 //!    feature. When failpoints are disabled, no code is generated by the macro.
 //!  - Carefully consider complex, concurrent, non-deterministic combinations of
 //!    fail points. Put test cases exercising fail points into their own test