Repository: mitsuhiko/insta (language: rust)

Issue:
1.42.0 changelog suggests incorrect command to recreate snaoshots
### What happened?

The [changelog entry for 1.42.0](https://github.com/mitsuhiko/insta/releases/tag/1.42.0) mentions `cargo test --force-update-snapshots` as the command to recreate snapshots. However, this is a `cargo insta test` subcommand argument, not a `cargo test` one.

### Reproduction steps

1. Run `cargo test --force-update-snapshots`


### Insta Version

1.42.0

### rustc Version

rustc 1.79.0 (129f3b996 2024-06-10)

### What did you expect?

Changelog should mention `cargo insta test --force-update-snapshots` instead.


Discussion / hints:

Fix patch:
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 80ba30ec..88b25c83 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -8,7 +8,7 @@ All notable changes to insta and cargo-insta are documented here.
   context, we originally added this in the prior release (1.41.0) to support
   binary snapshots, but some folks disliked the diff noise on any snapshot
   changes, and the maintainers' weighted votes favored reverting.  I apologize
-  that this will cause some additional churn for those who used `cargo test
+  that this will cause some additional churn for those who used `cargo insta test
   --force-update-snapshots` to update their snapshots to the 1.41 format;
   running this again with 1.42 will remove those metadata entries.  To confirm:
   this doesn't affect whether snapshot tests pass or fail — the worst impact is


Test patch: