feat: revert all changes during failed release process #791
Merged
decentral1se
merged 1 commits from 2026-03-03 00:02:16 +00:00
iexos/abra:push-opmswyqxplqx into main
Labels
Clear labels
bug
build
ci/cd
critical fix
design
documentation
duplicate
easy-first-issue
enhancement
help wanted
i10n
i18n
installer
invalid
question
release
release-candidate
security
tech-debt
test
wontfix
Something is not working
go build related issues
Building things with CI/CD
https://docs.coopcloud.tech/federation/resolutions/passed/010/
UI/UX
Documenting all the things
This issue or pull request already exists
Something for new people to get stuck into. We hope it's easy!
New feature
Need some help
Everything to do with localisation
Everything to do with internationalisation
Everything to do with the install script.
Something is wrong
More information is needed
Release management
Related to the new release candidate
Security related
Unit/integration testing
This won't be fixed
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
3wordchant
aadil (Aadil Ayub)
abra-bot (Abra Bot)
ammaratef45
amras (Sarma)
Apfelwurm
BornDeleuze
Brooke
carla
cas (Cassowary)
coopcloud
cyrnel
decentral1se (d1)
dede
devydave
fauno (fauno)
iexos
jade (Jade Ambrose)
jjsfunhouse
jmakdah2 (Jackie Makdah)
joe-irving (Joe Irving)
kawaiipunk (KawaiiPunk)
knoflook
kolaente
lambdabundesverband
linnealovespie (April)
moosemower
moritz
notplants
oxaliq (sorrel)
p4u1
pharaohgraphy (Andrew 🐦🔥❤️🔥✴️)
renovate-bot (Comrade Renovate Bot)
ripclap
simon
sixsmith (Sixsmith)
stevensting
trav (Trav Fryer)
val (val (he/him))
yksflip
Clear assignees
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: toolshed/abra#791
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
closes #683
Looking good, tysm @iexos! A few minor comments below.
@@ -317,2 +302,2 @@if cleanErr := cleanCommit(recipe, preCommitHead); cleanErr != nil {log.Fatal(cleanErr)if resetErr := resetCommit(recipe, preCommitHead); resetErr != nil {log.Fatal(resetErr)In the case of either
cleanTagorresetCommitfailing while trying to clean up, we'll see a cryptic error without context. Should we adjust thelog.Fatal(cleanErr)/log.Fatal(resetErr)to also include something likeunable to clean up after failed release attempt: %s@@ -393,2 +364,2 @@if tagString == "" {tagString = fmt.Sprintf("%s+%s", tag.String(), mainAppVersion)mainService := "app"label := i18n.G("coop-cloud.${STACK_NAME}.version=%s", tagString)We can remove the
i18n.G(...)wrapper since this string doesn't need to be translated.That was a previous mistake, I think. You can use a standard
fmt.Sprintfinstead.@@ -601,3 +579,3 @@}opts := &git.ResetOptions{Commit: head.Hash(), Mode: git.MixedReset}opts := &git.ResetOptions{Commit: head.Hash(), Mode: git.HardReset}Does this still guarantee that we still won't lose "non release related changes"? Can this be covered with a separate integration test as well? I'd rather we are safe than sorry in the case of potential data loss issues.
abrahas a bit of a bad reptuation in this regard 🙃There are already tests covering staged or unstaged changes in which case
releasewill bail out. Is that what you mean or is there something else you want to test?84a8fa2254to039a29f27c👏