RFE: propose_downstream trigger on new tag

[prestist]

Description

While working to configure our repository with packit to handle the downstream bits in our release checklist for fcos we noticed that the trigger for the propose_downstream would not work for our current release checklist/workflow.

Our current workflow is as follows

1. Update release notes
2. Land release notes in main
3. Tag merge commit
4. Update spec file
5. land the changes into rawhide/fcos-stable
6. build each branch
7. Submit builds to bodhi.
8. Wait for bodhi to sign builds
9. Then create a https://pagure.io/releng/new_issue to have our builds signed.
10. Then finally we can release our new version with our signed builds.

So for packit to trigger and update our spec file and merge it into the correct repos really we need to have the ability to trigger proposed_downstream on a new tag created.

For context:
Repository
Packit config
Spec file

Benefit

This would provide us a way to use packit.

Currently packit does not fit in the workflow as we are faced with a chicken and egg issue for our release upstream.

Importance

This is currently blocking me and my team from using packit in a number of repositories. Its so close to being exactly what we need.

What is the impacted category (job)?

Fedora release automation

Workaround

• There is an existing workaround that can be used until this feature is implemented.

Participation

• I am willing to submit a pull request for this issue. (Packit team is happy to help!)

[nforro]

Related issue: #1284

[lbarcziova]

This is also related to #1785

[lachmanfrantisek]

Hi @prestist !

Since you are mentioning other projects interested in this -- do you have a list of such projects? (We prioritise tasks where the benefit is the biggest => if we know we will unblock a new group of people to use Packit, there is a high chance we will get to it very soon..;)

Thanks!

[prestist]

@lachmanfrantisek 100% makes sense. While I thought it was more impactful to our repos, I might have over-estimated the number of them which require this change. There are two repo's coreos/ignition and coreos/butane.

[lsm5]

Podman would also be interested in this. We're looking to revise the podman release process like so:

1. Create tag
2. Build podman rpm
3. Build machine images (qcow2, applehv, hyperv) with the podman rpm included
4. Create github release with these machine images attached as release artifacts.