diff --git a/RELEASING.md b/RELEASING.md
index 4f1d16294..5199fb97d 100644
--- a/RELEASING.md
+++ b/RELEASING.md
@@ -34,10 +34,10 @@ git push upstream vX.Y.Z-rc.R
 
 Draft the release notes in our [GitHub releases](https://github.com/OpenZeppelin/openzeppelin-solidity/releases). Make sure to mark it as a pre-release! Try to be consistent with our previous release notes in the title and format of the text. Release candidates don't need a detailed changelog, but make sure to include a link to GitHub's compare page.
 
-Once the CI run for the new tag is green, publish on npm.
+Once the CI run for the new tag is green, publish on npm under the `next` tag.
 
 ```
-npm publish
+npm publish --tag next
 ```
 
 Publish the release notes on GitHub and ask our community manager to announce the release candidate on at least Slack and Twitter.
@@ -67,6 +67,12 @@ npm publish
 
 Publish the release notes on GitHub and ask our community manager to announce the release!
 
+Delete the `next` tag in the npm package as there is no longer a release candidate.
+
+```
+npm dist-tag rm --otp $2FA_CODE openzeppelin-solidity next
+```
+
 ## Merging the release branch
 
 After the final release, the release branch should be merged back into `master`. This merge must not be squashed, because it would lose the tagged release commit, so it should be merged locally and pushed.