From 5d3bc00fd5aa91845378917b5fec0bb182eeb7f9 Mon Sep 17 00:00:00 2001
From: link2xt <link2xt@testrun.org>
Date: Fri, 23 Jan 2026 13:52:24 +0000
Subject: [PATCH] docs(RELEASE.md): add section about dealing with failed
 releases

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

diff --git a/RELEASE.md b/RELEASE.md
index 033213dba..58f7c8be1 100644
--- a/RELEASE.md
+++ b/RELEASE.md
@@ -21,3 +21,10 @@ For example, to release version 1.116.0 of the core, do the following steps.
 8. Push the release tag: `git push origin v1.116.0`.
 
 9. Create a GitHub release: `gh release create v1.116.0 --notes ''`.
+
+## Dealing with failed releases
+
+Once you make a GitHub release,
+CI will try to build and publish [PyPI](https://pypi.org/) and [npm](https://www.npmjs.com/) packages.
+If this fails for some reason, do not modify the failed tag, do not delete it and do not force-push to the `main` branch.
+Fix the build process and tag a new release instead.