docs: use up-to-date example commits in the Release guide

We are using the Python's ".dev" versioning convention now (see fb231b1).
miyuchina · Jan 21, 2024 · acde7c2 · acde7c2
1 parent aa624e0
commit acde7c2
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/cutting-a-release.md b/cutting-a-release.md
@@ -2,7 +2,7 @@
 
 For maintainers, here are the basic steps when creating a new release of mistletoe.
 
-* set a release version & commit [chore: version <x.y.z>](https://github.com/miyuchina/mistletoe/commit/72e35ff22e823083915ed0327c5f479afec539fa)
+* set a release version & commit [chore: version <x.y.z>](https://github.com/miyuchina/mistletoe/commit/35dfaa0a95e8abb1cdceb8e449f9590905dca439)
 * publish artifacts of the release
     * official documentation: [Packaging Python Projects](https://packaging.python.org/en/latest/tutorials/packaging-projects/)
     * install / upgrade the build tool: `$ python -m pip install --upgrade build`
@@ -17,4 +17,4 @@ For maintainers, here are the basic steps when creating a new release of mistlet
 * [create the release in GitHub](https://github.com/miyuchina/mistletoe/releases/new)
     * attach the "dist/*.whl" from the previous step to the release (drag & drop) (source code archives are attached automatically)
     * publish the release, let GitHub create a new Git tag automatically
-* commit [chore: next dev version](https://github.com/miyuchina/mistletoe/commit/d91f21a487b72529a584b8958bffaed864dd67d7)
+* commit [chore: next dev version](https://github.com/miyuchina/mistletoe/commit/aa624e0e7015fa9993056bb4016bdec6079122d7)