hanzoai/deploy
2
0
Fork 0
mirror of https://github.com/hanzoai/deploy.git synced 2026-10-07 08:44:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: Update releasing.md with handling a failed release (#26049)

Browse Source 
Signed-off-by: Regina Voloshin <[email protected]>
Co-authored-by: Nitish Kumar <[email protected]>
This commit is contained in:
Regina Voloshin
2026-04-06 16:16:14 +05:30
committed by GitHub
co-authored by Nitish Kumar
parent 47f846f03b
commit 893f6fa5c0
1 changed files with 8 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/developer-guide/releasing.md
+8 -4
View File
@@ -98,11 +98,15 @@ checks to see if the release came out correctly:
### If something went wrong
If something went wrong, damage should be limited. Depending on the steps that
have been performed, you will need to manually clean up.
A new Argo CD release results in:
- A new GitHub release created
- Stable Git tag pointing to the release (if the release is the latest release)
- The release Go packages are published for using Argo CD code as dependency
- Docker images and SBOM artifacts are published
* If the container image has been pushed to Quay.io, delete it
* Delete the release (if created) from the `Releases` page on GitHub
Because of all the above dependencies, in a case of a release that failed, it is not safe to delete and recreate it.
Instead, create the next patch release (for example, if `3.2.4` failed, create `3.2.5` after fixing the problem, but don't recreate `3.2.4`).
Upon successful publishing of the fixed release (3.2.5 in our example), copy the full release notes manually from the failed release (3.2.4 in our example) and then update the failed release (3.2.4 in our example) release notes to state this release is invalid and should not be used.
### Manual releasing