abra recipe release pushes all branches #959

New Issue

2026-10-30T14:10:26Z

fauno commented

2026-10-30 14:10:26 +00:00

i've been finding my own private working branches pushed after i release a new recipe version and sometimes the release process fails because it can't push some branches. i think it should only push the current branch.

fauno commented

2026-10-30 14:10:50 +00:00

error example

? ¿Usar la nota de la versión en release/next? Yes
FATA 🛑 error al publicar la nueva versión: command error on refs/heads/renovate: refname conflict

error example ``` ? ¿Usar la nota de la versión en release/next? Yes FATA 🛑 error al publicar la nueva versión: command error on refs/heads/renovate: refname conflict ```

fauno commented

2026-10-30 14:12:32 +00:00

actually the push worked for main but since it failed to push the renovate branch, abra decided to soft reset the commit that was already pushed:

main monitoring-ng >_ git push --all
Enumerando objetos: 4, listo.
Contando objetos: 100% (4/4), listo.
Compresión delta usando hasta 4 hilos
Comprimiendo objetos: 100% (3/3), listo.
Escribiendo objetos: 100% (3/3), 587 byte | 587.00 KiB/s, listo.
Total 3 (delta 1), reused 0 (delta 0), pack-reused 0 (from 0)
remote: error: 'refs/heads/renovate/docker-29.x' exists; cannot create 'refs/heads/renovate'
To https://git.coopcloud.tech/coop-cloud/monitoring-ng.git
 ! [rejected]        main -> main (non-fast-forward)
 ! [remote rejected] renovate -> renovate (refname conflict)
error: falló el empuje de algunas referencias a 'https://git.coopcloud.tech/coop-cloud/monitoring-ng.git'
hint: Updates were rejected because the tip of your current branch is behind
hint: its remote counterpart. If you want to integrate the remote changes,
hint: use 'git pull' before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.
main monitoring-ng >_ git pull
Actualizando 7d7060c..f130a61
Fast-forward
 compose.yml                     | 2 +-
 release/{next => 2.3.0+v1.21.3} | 0
 2 files changed, 1 insertion(+), 1 deletion(-)
 rename release/{next => 2.3.0+v1.21.3} (100%)

actually the push worked for main but since it failed to push the renovate branch, abra decided to soft reset the commit that was already pushed: ``` main monitoring-ng >_ git push --all Enumerando objetos: 4, listo. Contando objetos: 100% (4/4), listo. Compresión delta usando hasta 4 hilos Comprimiendo objetos: 100% (3/3), listo. Escribiendo objetos: 100% (3/3), 587 byte | 587.00 KiB/s, listo. Total 3 (delta 1), reused 0 (delta 0), pack-reused 0 (from 0) remote: error: 'refs/heads/renovate/docker-29.x' exists; cannot create 'refs/heads/renovate' To https://git.coopcloud.tech/coop-cloud/monitoring-ng.git ! [rejected] main -> main (non-fast-forward) ! [remote rejected] renovate -> renovate (refname conflict) error: falló el empuje de algunas referencias a 'https://git.coopcloud.tech/coop-cloud/monitoring-ng.git' hint: Updates were rejected because the tip of your current branch is behind hint: its remote counterpart. If you want to integrate the remote changes, hint: use 'git pull' before pushing again. hint: See the 'Note about fast-forwards' in 'git push --help' for details. main monitoring-ng >_ git pull Actualizando 7d7060c..f130a61 Fast-forward compose.yml | 2 +- release/{next => 2.3.0+v1.21.3} | 0 2 files changed, 1 insertion(+), 1 deletion(-) rename release/{next => 2.3.0+v1.21.3} (100%) ```

decentral1se added the bug label 2026-10-31 21:33:52 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: toolshed/abra#959

abra recipe release pushes all branches #959

`abra recipe release` pushes all branches #959