diff --git a/Scrapy-release-procedure.md b/Scrapy-release-procedure.md
index 898e4d7..bd67a8f 100644
--- a/Scrapy-release-procedure.md
+++ b/Scrapy-release-procedure.md
@@ -97,13 +97,6 @@ $ git push origin master
 The recipe is located here: https://github.com/conda-forge/scrapy-feedstock/tree/master/recipe
 The procedure is through PRs from a fork against the master branch.
 
-Checklist:
-
-1. Update the ``version`` string.
-2. Update the ``sha256sum`` of the release tarball. This can be done by downloading the tarball from pypi and compute the sha256sum.
-3. Reset the ``build.number`` to ``0``. This number is only increased when we re-build a package with no version change.
-4. Update requirements if needed. This can be done by checking the ``setup.py`` changes between releases.
-5. Do a test build locally to ensure everything is OK.
-6. Create a branch in your fork and submit the PR.
+See the release update checklist: https://github.com/conda-forge/scrapy-feedstock#updating-scrapy-feedstock
 
 The PR will trigger builds in Travis CI, Circle CI and Appveyor. This may take a while depending on the conda-forge build queue. Once builds are OK, the PR is ready to merge and packages will be uploaded to the `conda-forge` channel automatically.
\ No newline at end of file