abra recipe release: support maintainer pull request review workflow #806

New Issue

2026-03-25T15:43:16Z

decentral1se commented

2026-03-25 15:43:16 +00:00

If you run abra recipe release it automatically bumps the labels and commits/pushes the tag. However, for a maintainer recipe pull request review workflow ™️, you want to push your commit from a branch and open a pull request.

What happened in coop-cloud/traefik#98 is that the tag was already pushed and released on the catalogue but the pull request was not reviewed 🙃 As mentioned in coop-cloud/traefik#98 (comment), we need some proposals for how abra recipe release can adapt to the collective use-case and not exclusively work for the lone maintainer.

Proposals welcome!

Follow up of https://git.coopcloud.tech/coop-cloud/traefik/pulls/98. If you run `abra recipe release` it automatically bumps the labels and commits/pushes the tag. However, for a maintainer recipe pull request review workflow ™️, you want to push your commit from a branch and open a pull request. What happened in https://git.coopcloud.tech/coop-cloud/traefik/pulls/98 is that the tag was already pushed and released on the catalogue but the pull request was not reviewed 🙃 As mentioned in https://git.coopcloud.tech/coop-cloud/traefik/pulls/98#issuecomment-32282, we need some proposals for how `abra recipe release` can adapt to the collective use-case and not exclusively work for the lone maintainer. Proposals welcome!

👍 1

decentral1se added the enhancement label 2026-03-25 15:43:16 +00:00

decentral1se referenced this issue from coop-cloud/traefik

2026-03-25 15:43:22 +00:00

chore: publish 5.1.0+v3.6.11 release #98

iexos commented

2026-03-25 17:05:18 +00:00

Merging changes and releasing are two very different things. The new flow requires you to commit your changes before making a release. I don't know how this commit was created but it should not possible with v0.13 abra recipe release. @moritz

Right now you might contribute all your changes via PR. Then someone has to do the release on main branch. But for actually publishing via PR you would need it to create a tag which I guess is only be possible via CI?

Merging changes and releasing are two very different things. The new flow requires you to commit your changes before making a release. I don't know how [this commit](https://git.coopcloud.tech/coop-cloud/traefik/commit/ff138864d4b086e510fc3d0abc5f74a3da1fdb55) was created but it should not possible with v0.13 `abra recipe release`. @moritz Right now you might contribute all your changes via PR. Then someone has to do the release on main branch. But for actually publishing via PR you would need it to create a tag which I guess is only be possible via CI?

decentral1se added this to the Abra "next" project 2026-03-29 16:04:39 +00:00

decentral1se referenced this issue from coop-cloud/mastodon

2026-04-27 19:51:33 +00:00

docs: Maintainers let's goooo #48

benjaminlyng commented

2026-07-11 05:47:13 +00:00

I think there are several solutions to this. I've tried two at work:

Autopub https://github.com/autopub/autopub - where you add a release.md file describing the type and text of the release
Conventional commits https://www.conventionalcommits.org/en/v1.0.0/ - where you write every commit starting with a tag depending on the type of release.

We've switched from Autopub to Conventional commits. I think mainly because we'd always forget to add the release.md file and then have to add it in a new commit later. 😅

Of course both changes the workflow for the maintainers a bit. For conventional commits you can add a commit-lint step in the pipeline which it will help to ensure your commits are correctly formatted before merging.

I'd say its definitely worth it to avoid the risks of pushing directly to the main branch.

I think there are several solutions to this. I've tried two at work: * Autopub https://github.com/autopub/autopub - where you add a release.md file describing the type and text of the release * Conventional commits https://www.conventionalcommits.org/en/v1.0.0/ - where you write every commit starting with a tag depending on the type of release. We've switched from Autopub to Conventional commits. I think mainly because we'd always forget to add the release.md file and then have to add it in a new commit later. 😅 Of course both changes the workflow for the maintainers a bit. For conventional commits you can add a commit-lint step in the pipeline which it will help to ensure your commits are correctly formatted before merging. I'd say its definitely worth it to avoid the risks of pushing directly to the main branch.

Sign in to join this conversation.

3 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: toolshed/abra#806

abra recipe release: support maintainer pull request review workflow #806

`abra recipe release`: support maintainer pull request review workflow #806