/osh-scans API endpoint. (packit-service#2614)Packit now links the information related to upstream events in PRs opened when syncing a release. (packit#2173)
When accessing tags or macro definitions by name, specfile library now takes validity into account
when looking for the best match. For example if there are two instances of Version tag,
one in the true and one in the false branch of a condition, Specfile.version will always access
the one that is in the true branch.
This also applies to Packit when syncing a release and updating value of Version tag.
(specfile#328)
propose_downstream and pull_from_upstream.
A spec file update might be required, see the documentation for more details.
(packit#2149)Specfile.update_version(), that allows updating spec file
version even if it is a pre-release. (specfile#317)update_version_mask configuration option, that the proposed version of new release
and the current version of the dist-git branch are compatible and sync the dist-git branch only in that case.
(packit#2156)Version tag is not present in the specfile directly,
but e.g. imported from another file. (packit#2157)PACKIT_COPR_PROJECT env var that is exposed to Testing Farm now includes the Copr project of the additional build
specified in comment, if present. (packit-service#2253)~^+ (special characters) in a tag (used for building the version string). (packit#2154)/jobs/downstream-koji-builds on dashboard and are also accessible via /api/koji-builds API endpoint. (packit-service#2244, packit-service#2249, dashboard#354)