ci: release into epel-9-next
Instead of directly releasing to epel-9 we should release into epel-9-next and do manual merges/releases when/if RHEL and/or CentOS catch up with our dependencies. Signed-off-by: Simon de Vlieger <supakeen@redhat.com>
This commit is contained in:
parent
9847b44619
commit
a893c2316e
1 changed files with 3 additions and 3 deletions
|
|
@ -30,19 +30,19 @@ jobs:
|
|||
dist_git_branches:
|
||||
- fedora-branched # rawhide updates are created automatically
|
||||
- epel-10
|
||||
- epel-9
|
||||
- epel-9-next
|
||||
- job: koji_build
|
||||
trigger: commit
|
||||
dist_git_branches:
|
||||
- fedora-all
|
||||
- epel-10
|
||||
- epel-9
|
||||
- epel-9-next
|
||||
- job: propose_downstream
|
||||
trigger: release
|
||||
dist_git_branches:
|
||||
- fedora-all
|
||||
- epel-10
|
||||
- epel-9
|
||||
- epel-9-next
|
||||
- job: copr_build
|
||||
trigger: pull_request
|
||||
targets: &build_targets
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue