diff --git a/CHANGELOG.md b/CHANGELOG.md
index 4220bfebb21d..6903b2b492b8 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -27,9 +27,6 @@
 
 ### Breaking
 
-- [#3007](https://github.com/ChainSafe/forest/pull/3007): Optimize DB
-  parameters. This requires all existing databases to be re-initialized.
-
 ### Added
 
 - [#3026](https://github.com/ChainSafe/forest/pull/3026): Expose
@@ -41,6 +38,15 @@
 
 ### Fixed
 
+## Forest v0.10.0 "Premature"
+
+### Breaking
+
+- [#3007](https://github.com/ChainSafe/forest/pull/3007): Optimize DB
+  parameters. This requires all existing databases to be re-initialized.
+
+### Fixed
+
 - [#3006](https://github.com/ChainSafe/forest/issues/3006): Fix `premature end`
   error when exporting a snapshot.
 
diff --git a/Cargo.toml b/Cargo.toml
index 161423d3463b..2a7b5e0529ed 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -1,6 +1,6 @@
 [package]
 name = "forest-filecoin"
-version = "0.9.0"
+version = "0.10.0"
 authors = ["ChainSafe Systems <info@chainsafe.io>"]
 repository = "https://github.com/ChainSafe/forest"
 edition = "2021"
diff --git a/documentation/src/developer_documentation/release_checklist.md b/documentation/src/developer_documentation/release_checklist.md
index 1b1b05048436..2fb38e80e6fa 100644
--- a/documentation/src/developer_documentation/release_checklist.md
+++ b/documentation/src/developer_documentation/release_checklist.md
@@ -20,7 +20,8 @@ in case of absence, passing the task to a different team member.
 4. Once the changes in step 1 and step 2 have been merged, tag the commit with
    the new version number. The version tag should start with a lowercase 'v'.
    Example: v0.4.1
-5. (NOT YET APPLICABLE) Publish new crates on crates.io.
+5. Publish new crates on crates.io according to the
+   [manual](https://doc.rust-lang.org/cargo/reference/publishing.html).
 6. Go to https://github.com/ChainSafe/forest/releases/new and create a new
    release. Use the tag created in step 4, follow the title convention of the
    previous releases, and write a small summary of the release (similar or
@@ -30,12 +31,7 @@ in case of absence, passing the task to a different team member.
    hour).
 8. Verify that the new release is available in the Github Container Registry.
    Use `docker pull ghcr.io/chainsafe/forest:<version>` and ensure that it is
-   present in the [packages][2]
-9. Update the [Forest Progress][1] wiki with the changes in the new release. If
-   in doubt about what has been accomplished, is in progress, or what's included
-   in the future plans, ask in the #fil-devs slack channel and tag authors of
-   related PRs.
-10. Make sure the `Cargo.lock` change is included in the pull request.
+   present in the [packages][1]
+9. Make sure the `Cargo.lock` change is included in the pull request.
 
-[1]: https://github.com/ChainSafe/forest/wiki/Forest-Progress
-[2]: https://github.com/ChainSafe/forest/pkgs/container/forest
+[1]: https://github.com/ChainSafe/forest/pkgs/container/forest