From 91cc10b69b7a0770f0df5f6f72bd98120f6e71f4 Mon Sep 17 00:00:00 2001
From: Sarah Alnegheimish <40212131+sarahmish@users.noreply.github.com>
Date: Mon, 16 Feb 2026 13:48:37 +0000
Subject: [PATCH] Update release guides to include conda-forge step

---
 RELEASE.md | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/RELEASE.md b/RELEASE.md
index e475b93c1..8d19ec2ab 100644
--- a/RELEASE.md
+++ b/RELEASE.md
@@ -22,6 +22,8 @@ The process of releasing a new version involves several steps:
 
 10. [Close milestone and create new milestone](#close-milestone-and-create-new-milestone)
 
+11. [Release on Conda-Forge](#release-on-conda-forge)
+
 ## Install RDT from source
 
 Clone the project and install the development requirements before start the release process. Alternatively, with your virtualenv activated.
@@ -173,3 +175,7 @@ Click `Publish release`, which will kickoff the release workflow and automatical
 
 Finaly, **close the milestone** and, if it does not exist, **create the next milestone**.
 
+## Release on conda-forge
+
+After the release is published on [public PyPI](https://pypi.org/project/rdt/), Anacanoda will automatically open a [PR on conda-forge](https://github.com/conda-forge/rdt-feedstock/pulls). Make sure the dependencies match and then merge the PR for the anaconda release to be published.
+