diff --git a/.release-notes/0.6.4.md b/.release-notes/0.6.4.md
new file mode 100644
index 0000000..59076a4
--- /dev/null
+++ b/.release-notes/0.6.4.md
@@ -0,0 +1,8 @@
+## Handle release already existing when uploading release notes
+
+Previously, the uploading of release notes assumed that the release didn't exist yet. If the release already existed, the release notes upload would fail.
+
+Only working when a release didn't exist made sense for all our ponylang usage. However, for other projects that create assets as part of the build process and store them in GitHub releases rather than Cloudsmith, the release might already exist.
+
+Now, we will check to see if the release exists. If it does, we update it with our release notes. If it doesn't, we will create the release like we previously did.
+
diff --git a/.release-notes/next-release.md b/.release-notes/next-release.md
index 59076a4..e69de29 100644
--- a/.release-notes/next-release.md
+++ b/.release-notes/next-release.md
@@ -1,8 +0,0 @@
-## Handle release already existing when uploading release notes
-
-Previously, the uploading of release notes assumed that the release didn't exist yet. If the release already existed, the release notes upload would fail.
-
-Only working when a release didn't exist made sense for all our ponylang usage. However, for other projects that create assets as part of the build process and store them in GitHub releases rather than Cloudsmith, the release might already exist.
-
-Now, we will check to see if the release exists. If it does, we update it with our release notes. If it doesn't, we will create the release like we previously did.
-