diff --git a/.bumpy/recover-bump-files-past-version-commit.md b/.bumpy/recover-bump-files-past-version-commit.md
deleted file mode 100644
index ec191df..0000000
--- a/.bumpy/recover-bump-files-past-version-commit.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'@varlock/bumpy': patch
----
-
-Fixed GitHub release notes coming up empty (`No changelog entries.`) when the publish ran several commits after the version commit — e.g. a retry after the first publish was blocked and unrelated fixes landed on main. Bump-file recovery assumed the version commit was always `HEAD~1..HEAD`; it now locates the most recent commit that actually deleted bump files and recovers their content from that commit's parent, so release notes are populated regardless of how far HEAD has moved past versioning.
diff --git a/packages/bumpy/CHANGELOG.md b/packages/bumpy/CHANGELOG.md
index d2c5e29..165cae4 100644
--- a/packages/bumpy/CHANGELOG.md
+++ b/packages/bumpy/CHANGELOG.md
@@ -1,5 +1,12 @@
 # Changelog
 
+## 1.16.1
+
+<sub>2026-06-25</sub>
+
+- [#136](https://github.com/dmno-dev/bumpy/pull/136) _(patch)_
+  Fixed GitHub release notes coming up empty (`No changelog entries.`) when the publish ran several commits after the version commit — e.g. a retry after the first publish was blocked and unrelated fixes landed on main. Bump-file recovery assumed the version commit was always `HEAD~1..HEAD`; it now locates the most recent commit that actually deleted bump files and recovers their content from that commit's parent, so release notes are populated regardless of how far HEAD has moved past versioning.
+
 ## 1.16.0
 
 <sub>2026-06-23</sub>
diff --git a/packages/bumpy/package.json b/packages/bumpy/package.json
index 6c06f39..e5922cd 100644
--- a/packages/bumpy/package.json
+++ b/packages/bumpy/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@varlock/bumpy",
-  "version": "1.16.0",
+  "version": "1.16.1",
   "description": "Modern monorepo versioning and changelog tool",
   "keywords": [
     "bump",