Week 13 (March 24th – March 30th)
- Over the past couple of weeks, we've been working to resolve a potential arbitrary code execution vulnerability related to how Packit processes spec file macros.
help command in PR and issue comments.
(packit-service#2853)rawhide PRs
of ELN packages without dedicated eln branch independently.
(packit-service#3032)pull-from-upstream via dist-git PR comment.
(packit-service#3058)propose_downstream/pull_from_upstream to fail if upstream git repo
contains submodules that are manipulated with in actions.
(packit-service#2768)--base-nvr option when submitting scans to OpenScanHub.
The base NVR is pulled in from Koji to perform a differential scan.
(packit#2569)use_target_repo_for_fmf_url configuration flag to bypass
the default passing of fork URLs for test requests.
(packit-service#2752)The default behaviour of changelog entry generation has been changed to comply with Fedora Packaging Guidelines
(see the relevant Fedora Packaging Committee discussion).
From now on, the default changelog entry is "- Update to version \<version>".
Users can still affect this behaviour using custom commands in the changelog-entry action
or with the copy_upstream_release_description configuration option.
(packit#2253)
"[packit]" prefix has been removed from default dist-git commit message titles in order to prevent
unnecessary noise in autogenerated changelog. Users can override this using the commit-message action.
(packit#2263)
packit validate-config now checks whether upstream_project_url is set if pull_from_upstream job is configured.
(packit#2254)%prep section processing. For instance, if the %patches macro appeared there,
it would have been converted to %patch es, causing failure when executing %prep later.
(specfile#356)packit). (packit-service#2364)