From 3915c309681d510dfd0dbee14a40f5ce3be3e919 Mon Sep 17 00:00:00 2001
From: James Wilson <james.wilson@parity.io>
Date: Thu, 24 Oct 2024 16:37:05 +0100
Subject: [PATCH] Update the release notes to work for current releases

---
 RELEASING.md | 21 +++++++++++++++------
 1 file changed, 15 insertions(+), 6 deletions(-)

diff --git a/RELEASING.md b/RELEASING.md
index 37bfc50d2d..6fa609649e 100644
--- a/RELEASING.md
+++ b/RELEASING.md
@@ -76,14 +76,23 @@ We also assume that ongoing work done is being merged directly to the `master` b
 
         ```
         (cd metadata && cargo publish) && \
-            (cd lightclient && cargo publish) && \
-            (cd codegen && cargo publish) && \
-            (cd macro && cargo publish) && \
-            (cd subxt && cargo publish) && \
-            (cd signer && cargo publish) && \
-            (cd cli && cargo publish);
+        (cd lightclient && cargo publish) && \
+        (cd utils/fetch-metadata && cargo publish) && \
+        (cd codegen && cargo publish) && \
+        (cd macro && cargo publish);
         ```
 
+        Now, remove the dev dependencies from `subxt-core` (to avoid circular deps), and then run:
+
+        ```
+        (cd core && cargo publish) && \
+        (cd subxt && cargo publish) && \
+        (cd signer && cargo publish) && \
+        (cd cli && cargo publish);
+        ```
+
+        Finally, put back the dev dependencies in `subxt-core`.
+
 11. If the release was successful, tag the commit that we released in the `master` branch with the
     version that we just released, for example: