sync_release in API allows specifying a suffix for the newly created branch in a dist-git repo fork,
so that there can be more open update PRs for the same dist-git branch at the same time.
The behaviour of running tests triggered by /packit test comment was improved.
If there is no existing Copr build when the tests are triggered,
Packit service should now react and create a new build.
Also when the last Copr build status is failed,
tests are not submitted and users are informed about this.
You can use oraclelinux-7/oraclelinux-8 chroots for build and test of your package on Oracle Linux.
Packit by default locally merges checked out pull requests into target branch.
Logging for checking out pull requests was improved to contain hashes and
summaries of last commit on both source and target branches.
Packit Service now runs Copr and Koji builds and following tests on Testing Farm
for pull requests on the code that would be a result of merging into the target branch.
In case merge conflicts occur during preparation of SRPM,
you can find more info in the SRPM logs.
Packit’s CLI source-git update-dist-git now supports using Git trailers to define patch metadata,
which will control how patches are generated and added to the spec-file.
source-git init uses this format to capture patch metadata when setting up
a source-git repo, instead of the YAML one.
To maintain backwards compatibility, the YAML format is still parsed,
but only if none of the patches defines metadata using Git trailers.
These changes will be applied next week (not this week as usual).