Installability check is now being run as part of CI on dist-git pull requests. For more information, please refer to our documentation. (packit-service#2782)
Support for Forgejo pull requests has been added. (ogr#925)
--resultdir argument in build_in_mock now defaults to the current directory ("."), preventing loss of build artifacts when not explicitly set. (packit#2567)tf_extra_params should now be included when submitting the automatic upstream installability check to the Testing Farm. (packit-service#2779)osh_options config option that allows you to customize OpenScanHub scans. (packit#2570)fast_forward_merge_into, version_update_mask is now correctly being taken into consideration. (packit#2551)config command group for configuration-related commands and moved the validate-config command under it, resulting in the new command being packit config validate. (packit#2559)/packit scratch-build. (packit-service#2770)
PACKIT_PROJECT_VERSION environment variable.
(packit#2297)status_name_template option that allows you to configure
status name for a Packit job. For further details have a look at our
docs.
This feature is still experimental and at the moment it is not possible
to retry such jobs via GitHub Checks' re-run.
(packit-service#2402)
koji_build job has a new sidetag_group option that allows to perform a downstream Koji build in a sidetag.
A new sidetag will be created for each configured dist_git_branch if it doesn't already exist.
This represents the first step towards multi-package Bodhi updates. Stay tuned for further advancements!
(packit-service#2409)copr_build job status checks were sometimes wrongly updated with a misleading
message after a SRPM build failure. (packit-service#2406)
packit dist-git init now allows specifying --version-update-mask option and also any arbitrary top-level configuration options. (packit#2288)/packit test comment command: in case there is a missing build for some target, the build will not be triggered anymore, it will just be reported to the user. We needed to make this change as with the increased complexity of the configuration (multiple test jobs), the previous implementation was prone to race conditions leading to wasting of resources of Copr and Testing Farm. (packit-service#2399)copr_build jobs sharing a Copr project but having different targets were running at the same time. (packit#2274)manual_trigger: True. (packit-service#2389)