Prepare 0.22.0 release

Author: tyranron

CHANGELOG.md

@@ -1,6 +1,6 @@
 [package]
 name = "cucumber"
-version = "0.21.1"
+version = "0.22.0"
 edition = "2024"
 rust-version = "1.88"
 description = """\
@@ -82,7 +82,7 @@ smart-default = "0.7.1"
 
 # "macros" feature dependencies.
 anyhow = { version = "1.0.58", optional = true }
-cucumber-codegen = { version = "=0.21.1", path = "./codegen", optional = true }
+cucumber-codegen = { version = "=0.22.0", path = "./codegen", optional = true }
 cucumber-expressions = { version = "0.5", features = ["into-regex"], optional = true }
 inventory = { version = "0.3", optional = true }
 

Cargo.toml

@@ -10,7 +10,7 @@ Cucumber testing framework for Rust
 An implementation of the [Cucumber] testing framework for Rust. Fully native, no external test runners or dependencies.
 
 - Book ([current][1] | [edge][2])
-- [Changelog](https://github.com/cucumber-rs/cucumber/blob/main/CHANGELOG.md)
+- [Changelog](https://github.com/cucumber-rs/cucumber/blob/v0.22.0/CHANGELOG.md)
 
 
 
@@ -113,8 +113,8 @@ The full gamut of Cucumber's [Gherkin] language is implemented by the [`gherkin`
 
 This project is licensed under either of
 
- * Apache License, Version 2.0 ([LICENSE-APACHE](https://github.com/cucumber-rs/cucumber/blob/main/LICENSE-APACHE) or <http://www.apache.org/licenses/LICENSE-2.0>)
- * MIT license ([LICENSE-MIT](https://github.com/cucumber-rs/cucumber/blob/main/LICENSE-MIT) or <http://opensource.org/licenses/MIT>)
+ * Apache License, Version 2.0 ([LICENSE-APACHE](https://github.com/cucumber-rs/cucumber/blob/v0.22.0/LICENSE-APACHE) or <http://www.apache.org/licenses/LICENSE-2.0>)
+ * MIT license ([LICENSE-MIT](https://github.com/cucumber-rs/cucumber/blob/v0.22.0/LICENSE-MIT) or <http://opensource.org/licenses/MIT>)
 
 at your option.
 

README.md

@@ -5,7 +5,7 @@ IntelliJ Rust (`libtest`) integration
 
 Example below is set up to output with the default [`writer::Basic`] if there is no `--format=json` option, or with [`writer::Libtest`] otherwise.
 ```toml
-cucumber = { version = "0.20", features = ["libtest"] }
+cucumber = { version = "0.22", features = ["libtest"] }
 ```
 ```rust
 # extern crate cucumber;

book/src/output/intellij.md

@@ -5,7 +5,7 @@ Cucumber JSON format
 
 This requires `output-json` feature to be enabled in `Cargo.toml`:
 ```toml
-cucumber = { version = "0.20", features = ["output-json"] }
+cucumber = { version = "0.22", features = ["output-json"] }
 ```
 
 And configuring output to [`writer::Json`]:

book/src/output/json.md

@@ -5,7 +5,7 @@ JUnit XML report
 
 This requires `output-junit` feature to be enabled in `Cargo.toml`:
 ```toml
-cucumber = { version = "0.20", features = ["output-junit"] }
+cucumber = { version = "0.22", features = ["output-junit"] }
 ```
 
 And configuring output to [`writer::JUnit`]:

book/src/output/junit.md

@@ -8,7 +8,7 @@ To start, let's create a directory called `tests/` in the root of the project an
 Add this to `Cargo.toml`:
 ```toml
 [dev-dependencies]
-cucumber = "0.20"
+cucumber = "0.22"
 futures = "0.3"
 
 [[test]]
@@ -37,7 +37,7 @@ To enable testing of our `simple.feature`, let's add this code to `example.rs`:
 #
 use cucumber::{World, given};
 
-// These `Cat` definitions would normally be inside your project's code, 
+// These `Cat` definitions would normally be inside your project's code,
 // not test code, but we create them here for the show case.
 #[derive(Debug, Default)]
 struct Cat {
@@ -51,7 +51,7 @@ impl Cat {
 }
 
 // `World` is your shared, likely mutable state.
-// Cucumber constructs it via `Default::default()` for each scenario. 
+// Cucumber constructs it via `Default::default()` for each scenario.
 #[derive(Debug, Default, World)]
 pub struct AnimalWorld {
     cat: Cat,
@@ -88,7 +88,7 @@ fn main() {
 > #
 > #[derive(Debug, World)]
 > // Accepts both sync/async and fallible/infallible functions.
-> #[world(init = Self::new)] 
+> #[world(init = Self::new)]
 > pub struct AnimalWorld {
 >     cat: Cat,
 > }
@@ -103,7 +103,7 @@ fn main() {
 > # fn main() {}
 > ```
 
-If we run this, we should see an output like this:  
+If we run this, we should see an output like this:
 ![record](rec/quickstart_simple_1.gif)
 
 A checkmark `✔` next to the `Given a hungry cat` [step] means that it has been matched, executed and passed.
@@ -161,7 +161,7 @@ fn feed_cat(world: &mut AnimalWorld) {
 # }
 ```
 
-Once we run the tests again, we see that two lines are green now and the next one is marked as not yet implemented:  
+Once we run the tests again, we see that two lines are green now and the next one is marked as not yet implemented:
 ![record](rec/quickstart_simple_2.gif)
 
 Finally, how do we check our result? We expect that this will cause some change in the cat and that the cat will no longer be hungry since it has been fed. The `then` [step] matcher follows to assert this, as our [feature] says:
@@ -211,7 +211,7 @@ fn cat_is_fed(world: &mut AnimalWorld) {
 # }
 ```
 
-Once we run the tests, now we see all steps being accounted for and the whole [scenario] passing:  
+Once we run the tests, now we see all steps being accounted for and the whole [scenario] passing:
 ![record](rec/quickstart_simple_3.gif)
 
 > __TIP__: In addition to assertions, we may also return a `Result<()>` from a [step] matching function. Returning `Err` will cause the [step] to fail. This lets using the `?` operator for more concise step implementations just like in [unit tests](https://doc.rust-lang.org/rust-by-example/testing/unit_testing.html#tests-and-).
@@ -261,7 +261,7 @@ fn cat_is_fed(world: &mut AnimalWorld) {
 # }
 ```
 
-And see the test failing:  
+And see the test failing:
 ![record](rec/quickstart_simple_fail.gif)
 
 > __TIP__: By default, unlike [unit tests](https://doc.rust-lang.org/cargo/commands/cargo-test.html#test-options), failed [step]s don't terminate the execution instantly, and the whole test suite is executed regardless of them. Use `--fail-fast` [CLI] option to stop execution on first failure.
@@ -332,7 +332,7 @@ fn hungry_cat(world: &mut AnimalWorld, state: String) {
 
 > __NOTE__: We surround the regex with `^..$` to ensure an __exact__ match. This is much more useful when adding more and more [step]s, so they won't accidentally interfere with each other.
 
-[Cucumber] will reuse these [step] matchers:  
+[Cucumber] will reuse these [step] matchers:
 ![record](rec/quickstart_concurrent_sync.gif)
 
 > __NOTE__: Captured values are __bold__ to indicate which part of a [step] is actually captured.
@@ -398,7 +398,7 @@ A contrived example, but it demonstrates that [step]s can be reused as long as t
 Let's switch our runtime to `tokio`:
 ```toml
 [dev-dependencies]
-cucumber = "0.20"
+cucumber = "0.22"
 tokio = { version = "1.10", features = ["macros", "rt-multi-thread", "time"] }
 
 [[test]]