ci release: automate updates of Fedora packages

[bkmgit]

No description provided.

[packit-as-a-service]

Failed to load packit config file:

Please correct data and retry.

For more info, please check out the documentation or contact the Packit team. You can also use our CLI command config validate or our pre-commit hooks for validation of the configuration.

[packit-as-a-service]

Failed to load packit config file:

Cannot parse package config. ValidationError({'jobs': {0: {'job': ['Must be one of: propose_downstream, pull_from_upstream, sync_from_downstream, copr_build, upstream_koji_build, koji_build, tests, bodhi_update, vm_image_build, koji_build_tag.']}}})

For more info, please check out the documentation or contact the Packit team. You can also use our CLI command config validate or our pre-commit hooks for validation of the configuration.

[packit-as-a-service]

Congratulations! One of the builds has completed. 🍾

You can install the built RPMs by following these steps:

• sudo yum install -y dnf-plugins-core on RHEL 8
• sudo dnf install -y dnf-plugins-core on Fedora
• dnf copr enable packit/enactic-openarm_can-56
• And now you can install the packages.

Please note that the RPMs should be used only in a testing environment.

[kou]

We can't test this without pushing a new tag such as 1.1.1, right?

[kou]

Could you use the same order in job: copr_build?

Suggested change

	- fedora-all
	- epel-all
	- epel-all
	- fedora-all