DOC Update release checklist regarding SECURITY.md
diff --git a/doc/developers/maintainer.rst b/doc/developers/maintainer.rst
index 1b79fbd3c282c..54b75a96b6360 100644
--- a/doc/developers/maintainer.rst
+++ b/doc/developers/maintainer.rst
@@ -301,7 +301,6 @@ The following GitHub checklist might be helpful in a release PR::
 
     * [ ] update news and what's new date in release branch
     * [ ] update news and what's new date and sklearn dev0 version in main branch
-    * [ ] update SECURITY.md in release and main branch
     * [ ] check that the wheels for the release can be built successfully
     * [ ] merge the PR with `[cd build]` commit message to upload wheels to the staging repo
     * [ ] upload the wheels and source tarball to https://test.pypi.org
@@ -311,6 +310,7 @@ The following GitHub checklist might be helpful in a release PR::
     * [ ] upload the wheels and source tarball to PyPI
     * [ ] https://github.com/scikit-learn/scikit-learn/releases publish (except for RC)
     * [ ] announce on mailing list and on Twitter, and LinkedIn
+    * [ ] update SECURITY.md in main branch (except for RC)
 
 Merging Pull Requests
 ---------------------

Follow-up of https://github.com/scikit-learn/scikit-learn/pull/25047
SECURITY.md is bound to the github repo. There's no need to update it in the release branch (it's not shipped in the wheels anyway). We only need to update it once the final release for a version (minor or major) is online.