diff --git a/CHANGELOG.md b/CHANGELOG.md
index 8d13cec..5d8eea1 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -7,13 +7,15 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 
 ## [Unreleased]
 
-<-- The latest version contains all changes.-->
+The latest version contains all changes.
+
+## [1.0.2] - 2021-10-29
 
 ### Changed
 
 - Misc package bumps
 
-## [1.0.1] - 2020-10-21
+## [1.0.1] - 2021-10-21
 
 ### Changed
 
diff --git a/Cargo.lock b/Cargo.lock
index 8ed1279..1ebc803 100644
--- a/Cargo.lock
+++ b/Cargo.lock
@@ -80,7 +80,7 @@ dependencies = [
 
 [[package]]
 name = "bovine"
-version = "1.0.1"
+version = "1.0.2"
 dependencies = [
  "anyhow",
  "bollard",
diff --git a/Cargo.toml b/Cargo.toml
index f111480..76cf38f 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -1,6 +1,6 @@
 [package]
 name = "bovine"
-version = "1.0.1"
+version = "1.0.2"
 edition = "2021"
 
 authors = ["Nick Gerace <nickagerace@gmail.com>"]
diff --git a/DEVELOPING.md b/DEVELOPING.md
index 2861bdd..f18ce46 100644
--- a/DEVELOPING.md
+++ b/DEVELOPING.md
@@ -16,8 +16,7 @@ Users dependencies are specified in the [README](../README.md).
 ## Building
 
 Building `bovine` should be possible on every tier one platform that Rust supports with no restriction on multi-platform development.
-We use `cargo xtask` for automation, which only requires `cargo` to be installed to work.
-For ease of use, you can alias `cargo xtask` to `cx` or something similar.
+We use GNU/BSD `make` for automation, but it's entirely optional as nearly all commands ran are `cargo` commands.
 
 ## Design Considerations
 
diff --git a/RELEASE.md b/RELEASE.md
index ac50cc2..c7ff909 100644
--- a/RELEASE.md
+++ b/RELEASE.md
@@ -10,7 +10,7 @@ This checklist details the `bovine` release process.
 
 - [ ] Checkout (or create a branch of) `main` at its latest commit.
 - [ ] Change the `version` field in `Cargo.toml` to the new tag.
-- [ ] Run `cargo xtask ci` and verify that everything looks/works as expected.
+- [ ] Run `make ci` and verify that everything looks/works as expected.
 - [ ] (Skip for release candidates) change the version in `CHANGELOG.md` and uncomment the line, `<!--The latest version contains all changes.-->`.
 - [ ] Create a commit with the following message `Update to <new-tag>`. Do not push (or merge) the commit.
 - [ ] Test and verify the publishing workflow: `cargo publish --dry-run`.